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

Switch to the recommended regional S3 domain #1334

Merged
merged 1 commit into from
Jun 13, 2022
Merged

Conversation

edmorley
Copy link
Member

Whilst the global S3 endpoint (s3.amazonaws.com) still works, AWS now recommends using the appropriate regional endpoint to access the bucket:
https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html#s3-legacy-endpoints

Our buildpack buckets are in us-east-1, whose regional domain is *.s3.us-east-1.amazonaws.com:
https://docs.aws.amazon.com/general/latest/gr/s3.html#s3_region

GUS-W-11283397.

Whilst the global S3 endpoint (`s3.amazonaws.com`) still works,
AWS now recommends using the appropriate regional endpoint
to access the bucket:
https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html#s3-legacy-endpoints

Our buildpack buckets are in `us-east-1`, whose regional domain
is `*.s3.us-east-1.amazonaws.com`:
https://docs.aws.amazon.com/general/latest/gr/s3.html#s3_region

GUS-W-11283397.
@edmorley edmorley self-assigned this Jun 13, 2022
@edmorley edmorley marked this pull request as ready for review June 13, 2022 08:05
@edmorley edmorley requested a review from a team as a code owner June 13, 2022 08:05
@edmorley edmorley merged commit 2b0805e into main Jun 13, 2022
@edmorley edmorley deleted the s3-regional-domain branch June 13, 2022 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants