Source: lambda.grofers.com
Reducing data transfer costs with a Docker registry cacheCategory: AWS, Kubernetes, Docker, nginx
Reducing costs has been a focus area for us ever since the COVID pandemic started. One of the prominent contributors to our AWS costs was the data transfer of our internal Docker registry. We use the Oregon region for our development environment & Singapore region for the production environment because of the cost difference between different AWS regions.
We were still getting charged for data transfer between S3 & Oregon region because the S3 bucket storing Docker images bucket was in the Singapore region and VPC Endpoints for services work for VPCs and AWS services within the same region.
This approach seemed great but had two issues: We had some workflows which were building images in the Oregon region and pushing them to our private registry.
We were still getting charged for data transfer between S3 & Oregon region because the S3 bucket storing Docker images bucket was in the Singapore region and VPC Endpoints for services work for VPCs and AWS services within the same region.
This approach seemed great but had two issues: We had some workflows which were building images in the Oregon region and pushing them to our private registry.
Related Articles
Community Partners
DevOps Careers