Describe the bug

I have a service sitting on CDK 2.140.0, works fine, when using service principal to allow our StateMachine to assume a role we created, ServicePrincipal properly uses the URI that is correct for Gov Cloud: "states.us-gov-west-1.amazonaws.com". After upgrading CDK, it stops translating "states.amazonaws.com" to the correct URI. Is this intentional? Do we need to update our code? This was a handy feature, getting the correct URI from service principal for our region, wanted to make sure it wasn't remove unintentionally.

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Version

2.140.0

Expected Behavior

ServicePrincipal translates input to the correct URI for states in gov cloud.

Current Behavior

ServicePrincipal uses the commercial cloud URI for states.

Reproduction Steps

Create a role

new Role(this, 'StepFunctionRole', {
  roleName: `some-test`,
  description: `Execution role for step function`,
  assumedBy: new ServicePrincipal('states.amazonaws.com')
})

This previously resulted in:

{
       Action: 'sts:AssumeRole',
       Effect: 'Allow',
       Principal: { Service: 'states.us-gov-west-1.amazonaws.com' }
}

Now it results in:

{
      Action: 'sts:AssumeRole',
      Effect: 'Allow',
      Principal: { Service: 'states.amazonaws.com' }
}

Possible Solution

I admittedly haven't cracked the code, so not sure on this one.

Additional Information/Context

No response

CDK CLI Version

2.140.0

Framework Version

No response

Node.js Version

18.20.4

OS

Same regardless of OS

Language

TypeScript

Language Version

4.8.3

Other information

No response