-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CDK Pipelines] Changes are deployed and published using global STS endpoints #9223
Comments
I don't think this is a bug, since switching to regional endpoints is more of an optimization than a necessity. https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_enable-regions.html |
It means we have created a single point of failure that is outside of the region a pipeline is configured to use as the “global” endpoint is dependent on us-east-1. If CDK is supposed to have best practices as a default then this is a bug. |
I agree. Thanks for the report. |
Make CLI and `cdk-assets` use regional endpoints by setting `AWS_STS_REGIONAL_ENDPOINTS=regional`. While we are configuring the SDK by setting global environment variables anyway (*shudder*), might as well improve performance a bit by enabling keepalive on the connections (by setting `AWS_NODEJS_CONNECTION_REUSE_ENABLED=1`). Fixes #9223.
Make CLI and `cdk-assets` use regional endpoints by setting `AWS_STS_REGIONAL_ENDPOINTS=regional`. While we are configuring the SDK by setting global environment variables anyway (*shudder*), might as well improve performance a bit by enabling keepalive on the connections (by setting `AWS_NODEJS_CONNECTION_REUSE_ENABLED=1`). Fixes #9223. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
CDK Pipelines currently uses global STS endpoints to publish artifacts and also to deploy the self-mutating pipeline changes instead of the correct regional endpoints
Reproduction Steps
Create a CDK pipeline, using the demo example in the docs is fine. Check your CloudTrail logs and you can see v1 API calls to the us-east-1 endpoint for STS (auth tokens that start with an
F
) are going to be visible.Error Log
Environment
Other
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: