Skip to content
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

Unable Connect to STS if using a VPC #4333

Closed
SolYs02 opened this issue Nov 6, 2024 · 1 comment
Closed

Unable Connect to STS if using a VPC #4333

SolYs02 opened this issue Nov 6, 2024 · 1 comment
Assignees
Labels
bug This issue is a confirmed bug. closed-for-staleness p2 This is a standard priority issue sts

Comments

@SolYs02
Copy link

SolYs02 commented Nov 6, 2024

Describe the bug

Same as #4301

Describe the bug
When I attempt to send an STS message from a Lambda function in a VPC, I encounter a timeout issue. I tried using the VPC Link, but it didn’t work.

This solution resolved the problem:

assumed_role = boto3.client( "sts", endpoint_url=f"https://sts.{os.environ['AWS_REGION']}.amazonaws.com", )

Expected Behavior
Successfully executed boto3's sts.get_caller_identity().

Current Behavior
Received a timeout error.

Reproduction Steps
Create a VPC without internet access, add an STS interface endpoint, and then attempt to call boto3's sts.get_caller_identity().

@SolYs02 SolYs02 added bug This issue is a confirmed bug. needs-triage This issue or PR still needs to be triaged. labels Nov 6, 2024
@tim-finnigan tim-finnigan self-assigned this Nov 6, 2024
@tim-finnigan
Copy link
Contributor

Thanks for reaching out. Please refer to this documentation: https://docs.aws.amazon.com/sdkref/latest/guide/feature-sts-regionalized-endpoints.html. Setting the AWS_STS_REGIONAL_ENDPOINTS environment variable or sts_regional_endpoints configuration to regional will force the boto3 to use regional rather than global endpoints when calling STS.

@tim-finnigan tim-finnigan added response-requested Waiting on additional information or feedback. p2 This is a standard priority issue sts closing-soon This issue will automatically close in 4 days unless further comments are made. and removed response-requested Waiting on additional information or feedback. needs-triage This issue or PR still needs to be triaged. labels Nov 6, 2024
@SolYs02 SolYs02 changed the title Unable Connect to STS if using a VPC #4301 Unable Connect to STS if using a VPC Nov 7, 2024
@github-actions github-actions bot added closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a confirmed bug. closed-for-staleness p2 This is a standard priority issue sts
Projects
None yet
Development

No branches or pull requests

2 participants