When comparing Amazon EC2 Container Registry vs JFrog Bintray, the Slant community recommends Amazon EC2 Container Registry for most people. In the question“What are the best docker image private registries?” Amazon EC2 Container Registry is ranked 17th while JFrog Bintray is ranked 19th.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Amazon ECR is integrated with Amazon EC2 Container Service (ECS), simplifying your development to production workflow.
Pro Free tier
Amazon ECR, like other AWS tools has a free tier for beginners of 500MB-month storage for one year.
Pro 100% Automated via REST API
Open for automation, JFrog Bintray easily integrates with your existing DevOps ecosystem, such as your continuous integration pipeline and your internal repositories. A rich REST API allows you to control every aspect of your software distribution, manage who has access to your content, collect logs and analytics, and much more - all with the full automation expected of a modern software distribution platform.
Pro Statistics and dashboards
Great statistics on downloads of your Docker images according to tags, geo-location and more..
Pro Universal solution
One distribution platform that supports all technologies. JFrog Bintray natively supports all major package formats, which allows you to work seamlessly with industry standard development, build and deployment tools. With support for massive scalability and worldwide coverage, this gives you the best native repository distribution available.
Pro Full control and security
Exercise fine-grained access control over who can view, upload to or download from your private repositories. Maintain any degree of control through a variety of means, such as IP and geographical restrictions, EULA acceptance and more. Automatically provision your organization users via API, or have them silently sign in with SAML authentication to your existing identity provider.
Cons
Con The access token expires after 12 hours
You have to build a more complex deployment script in order to compensate for the AWS token expiring after 12 hours.