8000 feat: Use regional endpoint for us-east-1 AWS region by maksim-paskal · Pull Request #4662 · distribution/distribution · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: Use regional endpoint for us-east-1 AWS region #4662

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

maksim-paskal
Copy link

Use regional S3 endpoint, instead global for buckets in us-east-1 AWS region, this change reduce cloud costs:

To test this changes - start registry with S3 bucket in us-east-1 region:

export REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io
export REGISTRY_STORAGE=s3
export REGISTRY_STORAGE_S3_BUCKET=test-bucket-for-test-distribution
export REGISTRY_STORAGE_S3_REGION=us-east-1
export REGISTRY_STORAGE_S3_LOGLEVEL=debug

go run ./cmd/registry serve ./cmd/registry/config-dev.yml

All requests to S3 use regional endpoint:

GET /?list-type=2&max-keys=1&prefix= HTTP/1.1
Host: test-bucket-for-test-distribution.s3.us-east-1.amazonaws.com

Closes: #4661

Signed-off-by: Maksim Paskal <paskal.maksim@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Distribution don't use regional us-east-1 endpoint
1 participant
0