Skip to content

Conversation

@cloud456
Copy link
Collaborator

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

linnjia-aws and others added 30 commits July 11, 2025 11:26
This patch adds AWS ECR (Elastic Container Registry) support to the docker-reverse-proxy, allowing it to work with both GCP Artifact Registry and AWS ECR. Key changes include:

- Add cloud provider detection based on CLOUD_PROVIDER environment variable
- Implement AWS ECR authentication using AWS SDK
- Add support for dynamic AWS account ID discovery via STS
- Make AWS credentials optional to support EC2 instance roles
- Centralize AWS configuration in shared/pkg/consts/aws.go
- Add proper path handling for AWS ECR repositories
- Update proxy logic to handle both GCP and AWS specific paths

With this change, users can configure the docker-reverse-proxy to work with AWS ECR by setting CLOUD_PROVIDER=aws and providing the required AWS configuration (AWS_ECR_REPOSITORY_NAME is req
uired, while AWS_REGION, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_ACCOUNT_ID are optional when running on EC2 with instance roles).
crazyoyo and others added 30 commits July 21, 2025 17:11
- Relocated AWS constants from shared/pkg/consts to docker-reverse-proxy/internal/constants
- Updated proxy path mapping for better repository name handling
- Added detailed debug logging in proxy handler for better troubleshooting
- Improved token handling and authentication flow tracing
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.

5 participants