For the last four months I’ve been developing a custom container image builder, collaborating with Outerbounds1. The technical details of the builder itself might be the topic of a future article, but there’s something surprising I wanted to share already: you can use S3 as a container registry! You heard it right. All it takes is to expose an S3 bucket through HTTP and to upload the image’s files to specific paths.

Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

Using S3 as a container registry is feasible by exposing an S3 bucket through HTTP and uploading image files to specific paths. This approach can yield substantial performance improvements, particularly in upload speed, compared to traditional container registries like ECR. While the method is experimental and lacks the advanced features of dedicated registries, it opens up new possibilities for optimizing container image hosting.

Using S3 as a container registry

<p>i not agree with this, the registry give you more services related to the container. it’s not just “upload speed”</p>
