I have an image in a private Docker Hub repository, which I'm trying to deploy on Amazon's Elastic Container Service. There seems to be nice web console to run a container from a public repository, but nothing for private. I've read and tried to understand the documentation for this, but I don't understand what that has to do with deploying my container, as it states 'The Amazon ECS container agent allows container instances to connect to your cluster'.

1. Aws Fargate
2. Aws Docker Service

Amazon Elastic Container Service Agent. This image is meant to be run on Amazon EC2. Running this image outside of Amazon. Sep 6, 2018 - Deploying the Winds API to AWS ECS with Docker Compose. Get out chinese subtitles season. Provider if you like; however, I highly recommend sticking with Docker Hub).

How to run HuBot in Docker on AWS EC2 Container Services - Part 1. By Philipp Garbe. With each commit a build should be triggered and when the tests are green it should automatically deployed to AWS EC2 Container Service (ECS). GitHub - CircleCI - Docker Hub - AWS ECS Sources are available on my GitHub repository.

Aws Fargate

As an alternative to using the web console, I see mentions of setting up a task definition. It sounds like that's the manual version of what the web console does. I suspect my best bet is with this method, possibly with the help of the script here.

What is the simplest way for me to run an existing image on ECS that's hosted in a private repository?

1 Answer

Right, so a container instance is just the EC2 machine that happens to run the services defined in the cluster. The cluster can then connect to the EC2 machine as a container instance, but unless the EC2 machine is appropriately configured, it can't run your private repository.

Aws Docker Service

Not the answer you're looking for? Browse other questions tagged amazon-ec2dockerdockerhub or ask your own question.