Unable Connect do STS if using a VPC

[SolYs02]

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().

[tim-finnigan]

Thanks for reaching out. Can you please share a complete code snippet for reproducing the issue? Also, could you share debug logs (with any sensitive info redacted)? You can get the logs by adding boto3.set_stream_logger('') to your script after importing boto3.

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

[SolYs02]

I already found the root cause, it is similar to issue like #3311.
The endpoint that SQS tries to access lacks the region (e.g. https://sts.amazonaws.com) and that doesn't work inside a VPC since the private DNS of a VPCe includes the region.