Skip to content

Add S3-specific endpoint to generated AWS profile - #473

Draft
anisaoshafi wants to merge 1 commit into
mainfrom
support-s3-to-aws-profile
Draft

Add S3-specific endpoint to generated AWS profile#473
anisaoshafi wants to merge 1 commit into
mainfrom
support-s3-to-aws-profile

Conversation

@anisaoshafi

Copy link
Copy Markdown
Collaborator

Motivation

aws --profile localstack used directly (not through lstk's own proxies) sent S3 requests to the profile's general endpoint, breaking S3's virtual-host-style bucket addressing.

Solution

lstk setup aws now writes an S3 endpoint override in a [services localstack] block, referenced via services = localstack in the profile. It reuses the existing endpoint.S3Addressing helper already used by the Terraform/CDK proxies. Idempotency checks and the existing --force overwrite behavior extend to cover it.

Review

Small, self-contained, covered by unit and integration tests. Self-merge candidate.

Closes DEVX-755

@anisaoshafi anisaoshafi added semver: patch docs: skip Pull request does not require documentation changes labels Aug 27, 2026
@anisaoshafi
anisaoshafi force-pushed the support-s3-to-aws-profile branch 2 times, most recently from 15292ec to a55a980 Compare August 31, 2026 14:11
@anisaoshafi
anisaoshafi force-pushed the support-s3-to-aws-profile branch from a55a980 to 295b8ed Compare August 31, 2026 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs: skip Pull request does not require documentation changes semver: patch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant