4 ms·
The fun thing about the docker rate limit is that the layer tarballs are stored on S3 in us-east-1. If you do a docker pull inside us-east-1, you’ll get a dire
by glenjamin 5y ago
The fun thing about the docker rate limit is that the layer tarballs are stored on S3 in us-east-1.
If you do a docker pull inside us-east-1, you’ll get a direct S3 link instead of a proxied download, and thus neither you nor docker need to pay AWS anything for bandwidth!
- yjftsjthsd-h 5y ago> If you do a docker pull inside us-east-1, you’ll get a direct S3 link instead of a proxied download, and thus neither you nor docker need to pay AWS anything for bandwidth! I thought cross-account data still cost something; is that not the case?
- dantiberian 5y ago> You pay for all bandwidth into and out of Amazon S3, except for the following: > Data transferred from an Amazon S3 bucket to any AWS service(s) within the same AWS Region as the S3 bucket (including to a different account in the same AWS Region). https://aws.amazon.com/s3/pricing/ https://aws.amazon.com/s3/pricing/
- yjftsjthsd-h 5y agoOoooh very neat thanks for sharing:) That has... interesting potential...
- acdha 5y agoAlso consider enabling S3 gateway endpoints: https://docs.aws.amazon.com/vpc/latest/privatelink/vpce-gateway.html https://docs.aws.amazon.com/vpc/latest/privatelink/vpce-gate... That avoids paying NAT Gateway charges for traffic to S3 and in my testing also made a bit of a latency reduction, which came in handy once when I had a one-off data small file migration.
- yjftsjthsd-h 5y agoThank you:)