serverless / serverless/serverless
STS:GetCallerIdentity does not use STS VPC Endpoint
Open
Nobody has claimed this yet.
bug
cat/deployment
- Dominant language
- JavaScript
- Stars
- 46.9k
- Forks
- 5.7k
- Avg merge
- 10h 7m
- Merged PRs (30d)
- 57
Description
This is a Bug Report
Description
-
What went wrong?
Deployment of serverless framework does not use the STS VPC endpoint but instead defaults to the default sts url. -
What did you expect should have happened?
it should use the sts vpc endpoint. -
What was the config you used?
-
What stacktrace or error message from your provider did you see?
Timed out
Similar or dependent issues:
- #12345
Additional Data
- Serverless Framework Version you're using:
- Operating System:
- Stack Trace:
- Provider Error messages:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how deployment obtains AWS STS credentials and selects the endpoint for GetCallerIdentity, then reproduce the timeout with an STS VPC endpoint configured. Done means GetCallerIdentity uses the STS VPC endpoint instead of the default STS URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100