localstack / localstack/aws-cdk-local
Cannot Set AWS_ENDPOINT_URL_S3 Without DNS Mapping
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 305
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
For the use case where the localstack instance is on a remote server, the environment variables AWS_ENDPOINT_URL and AWS_ENDPOINT_URL_S3 must be set. It should be noted that this requirement appears to have been added when LOCALSTACK_HOSTNAME was deprecated. The problem with setting the AWS_ENDPOINT_URL_S3 variable is the additional requirement that the "server" be in the format of s3.servername.domain which will never resolve correctly without a DNS mapping.
aws-cdk-local version: 3.0.1
Error messages when trying to bootstrap the localstack environment (S3 upload errors):
XXXXXXStack: fail: getaddrinfo ENOTFOUND cdk-hnb659fds-assets-000000000000-us-east-1.s3.servername.domain
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 AWS_ENDPOINT_URL and AWS_ENDPOINT_URL_S3 are handled during CDK bootstrapping, then reproduce the S3 upload failure against a remote LocalStack instance. Done means remote S3 uploads work without requiring a DNS mapping for the s3.servername.domain hostname.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100