I&#39;m just getting started on AWS EC2. I understand that EC2 is like a remote computer where I can do pretty much everything I want. Then I found out about ECS. I know it uses Docker, but I&#39;m confused about the relationship between these two.

Is ECS just a Docker install in EC2?
If I already have an EC2 and I start an ECS, does it mean I have two instances?


What is the difference between Amazon ECS and Amazon EC2?

It appears that one can either run a Task or a Service based on a Task Definition. What are the differences and similarities between Task and Service? Is there a clue in the fact that one can specify &quot;Task Group&quot; when creating Task but not Service? Are Task and Service hierarchically equal instantiations of Task Definition, or is Service composed of Tasks?

What is the difference between a task and a service in AWS ECS?

What is the right approach to make my [Amazon ECS](http://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html) tasks update their Docker images, once said images have been updated in the corresponding registry?

How do I deploy updated Docker images to Amazon ECS tasks?

Im trying to deploy a `docker` container image to `AWS` using `ECS`, but the EC2 instance is not being created. I have scoured the internet looking for an explanation as to why I&#39;m receiving the following error: 

&gt;&quot;A client error (InvalidParameterException) occurred when calling the RunTask operation: No Container Instances were found in your cluster.&quot;

**Here are my steps:** 

1\. Pushed a docker image FROM Ubuntu to my Amazon ECS repo.
   
2\. Registered an ECS Task Definition:

    aws ecs register-task-definition --cli-input-json file://path/to/my-task.json 

3\. Ran the task: 

    aws ecs run-task --task-definition my-task

Yet, it fails.

**Here is my task:**

    {
      &quot;family&quot;: &quot;my-task&quot;,
      &quot;containerDefinitions&quot;: [
        {
            &quot;environment&quot;: [],
            &quot;name&quot;: &quot;my-container&quot;,
            &quot;image&quot;: &quot;my-namespace/my-image&quot;,
            &quot;cpu&quot;: 10,
            &quot;memory&quot;: 500,
            &quot;portMappings&quot;: [
                {
                    &quot;containerPort&quot;: 8080,
                    &quot;hostPort&quot;: 80
                }
            ],
            &quot;entryPoint&quot;: [
                &quot;java&quot;,
                &quot;-jar&quot;,
                &quot;my-jar.jar&quot;
            ],
            &quot;essential&quot;: true
        }
      ]
    }

I have also tried using the management console to configure a cluster and services, yet I get the same error. 
How do I configure the cluster to have ec2 instances, and what kind of container instances do I need to use? *I thought this whole process was to create the EC2 instances to begin with!!*





    

AWS ECS Error when running task: No Container Instances were found in your cluster

I&#39;m using AWS&#39;s CloudFormation, and I recently spent quite a bit of time trying to figure out why the role I had created and attached policies to was not enabling my ECS task to send a message to a Simple Queue Service (SQS) queue. 

I realized that I was incorrectly attaching the SQS permissions policy to the `Execution Role` when I should have been attaching the policy to the `Task Role`. I cannot find good documentation that explains the difference between the two roles. CloudFormation documentation for the two of them are here: [ExecutionRole](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-taskdefinition.html#cfn-ecs-taskdefinition-executionrolearn) and [TaskRole](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-taskdefinition.html#cfn-ecs-taskdefinition-taskrolearn)

Difference between AWS Elastic Container Service&#39;s (ECS) ExecutionRole and TaskRole

I am trying to run a private repository on aws-ecs-fargate-1.4.0 platform.

For private repository authentication, I have followed the [docs][1] and it was working well.

Somehow after updating existing service many times it goes fail to run the task and complain the error like 

    ResourceInitializationError: unable to pull secrets or registry auth: execution resource retrieval failed: unable to get registry auth from asm: service call has been retried 1 time(s): asm fetching secret from the service for &lt;secretname&gt;: RequestError: ...

I haven&#39;t change the `ecsTaskExecutionRole` and it contains all required policies to fetch secret value.

 1. AmazonECSTaskExecutionRolePolicy
 2. CloudWatchFullAccess
 3. AmazonECSTaskExecutionRolePolicy
 4. GetSecretValue
 5. GetSSMParamters



  [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/private-auth.html

Aws ecs fargate ResourceInitializationError: unable to pull secrets or registry auth

I&#39;m building a system consisting of an Angular2 single page app and a REST API running on ECS. The API runs on .Net/[Nancy](http://nancyfx.org/), but that might well change.

I would like to give Cognito a try and this is how I imagined the authentication workflow:

 1. SPA signs in user and receives a JWT
 2. SPA sends JWT to REST API with every request
 3. REST API verfies that the JWT is authentic

My question is about step 3. **How can my server (or rather: my stateless, auto-scaled, load-balanced Docker containers) verify that the token is authentic?** Since the &quot;server&quot; hasn&#39;t issued the JWT itself, it can&#39;t use its own secret (as described in the basic JWT example [here](https://jwt.io/introduction/)).

I have read through the Cognito docs and googled a lot, but I can&#39;t find any good guideline about what to do with the JWT on the server side.

How to verify JWT from AWS Cognito in the API backend?

I&#39;ve developed a Docker based application comprised of multiple microservices. It has to consume Amazon SQS messages and processes them. At first I wanted to use AWS Elastic Beanstalk, but then I fell over the EC2 Container Service. Now I don&#39;t know which one to choose.

As of now, Elastic Beanstalk supports Multi-Container-Environments. That&#39;s great because every microservice has its own application server inside a docker container. The next problem is scaling:

I don&#39;t know how the scaling mechanism works. For example: I have 5 docker containers in my Elastic Beanstalk Environment. Now only the fifth docker container is under heavy load, because it has a huge amount of SQS messages to process, the other four are nearly idle, because they don&#39;t need much CPU or maybe don&#39;t have a lot of SQS messages. Let&#39;s assume the 5th container runs a JBoss application server. As far as i know, the server only can consume a limited amount of parallel requests even if there is enough CPU/memory available.

If the JBoss Docker container isn&#39;t able to handle the amount of requests, but there is enough CPU/memory available, of course I want to automatically start a second Docker/JBoss container on the same instance. But what happens, if I don&#39;t have enough CPU/memory? Of course I want to spin on a second instance, which is configurable through a auto-scaling group in EB. Now a second instance spins up, but every container except of the 5th is nearly idle, of course I don&#39;t want them to spawn 4 unnecessary at the second instance too, which would be a waste of resources. Only the 5th should spawn and the others should scale like the 5th scale based on configurable parameters like e.g.: CPU/memory/SQS. 

I don&#39;t exactly know if Amazon ECS is doing that, or if it&#39;s possible at all, but I really can&#39;t find any source on the internet about this topic, which is in general said, scaling based on instances/containers.

Should I use AWS Elastic Beanstalk or the Amazon EC2 Container Service (ECS) to scale Docker containers?

When I deploy using cloudformation ```aws cloudformation deploy --region $region --stack-name ABC```

Got error: 

&gt; An error occurred (ValidationError) when calling the CreateChangeSet
&gt; operation:
&gt; Stack:arn:aws:cloudformation:stack/service/7e1d8c70-d60f-11e9-9728-0a4501e4ce4c
&gt; is in ROLLBACK_COMPLETE state and can not be updated.

Please help me !

ValidationError Stack:arn aws cloudformation stack is in ROLLBACK_COMPLETE state and can not be updated

Once you&#39;ve created a task definition in Amazon&#39;s EC2 Container Service, how do you delete or remove it? 

How do you delete an AWS ECS Task Definition?

I&#39;m trying to setup a basic web application, which has an associated database, in AWS ECS. Locally I have these setup in different containers, and on ECS, I&#39;d like to have separate task definitions so that I may scale the two separately.

1. I registered my first task definition as `david_mongodb` successfully in ECS. It has a container named `david_mongodb` in it.
2. Then I attempted to register my second task definition as `david_web`, which has a container named `david_web` that links the database via `david_mongodb:db`.
3. When I click &#39;Create&#39;, it returns an error:

        Unable to create Task Definition
        Linked container &#39;david_mongodb:db&#39; doesn&#39;t exist.

It seems like task definitions can&#39;t see container names in other task definitions? I&#39;m thinking putting both `david_web` and `david_mongodb` containers in the same task definition would work, but I don&#39;t want to do that: it would prevent me from scaling either web app or database separately. [This overview](http://docs.aws.amazon.com/AmazonECS/latest/developerguide/application_architecture.html) seems to confirm that my architecture is recommended...

So how do I link containers that live in different task definitions? Or is there another clever way of handling this?

Linking containers between task definitions in AWS ECS?

I am running docker-nginx on ECS server. My nginx service is suddenly stopped because the `proxy_pass` of one of the servers got unreachable. The error is as follows:

    [emerg] 1#1: host not found in upstream &quot;dev-example.io&quot; in /etc/nginx/conf.d/default.conf:988

My config file is as below:

     server {
           listen      80;
           server_name     test.com;
           location / {
              proxy_pass         http://dev-exapmle.io:5016/;
              proxy_redirect     off;

              ##proxy_set_header   Host             $host;
              proxy_set_header   X-Real-IP        $remote_addr;
              proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;

              client_max_body_size       10m;
              client_body_buffer_size    128k;

              proxy_connect_timeout      90;
              proxy_send_timeout         90;
              proxy_read_timeout         90;

              proxy_buffer_size          4k;
              proxy_buffers              4 32k;
              proxy_busy_buffers_size    64k;
              proxy_temp_file_write_size 64k;
           }
    }

    server {
       listen       80 default_server;
       server_name  localhost;

       #charset koi8-r;
       #access_log  /var/log/nginx/log/host.access.log  main;

       location / {
          root   /usr/share/nginx/html;
          index  index.html index.htm;
       }

       #error_page  404              /404.html;

       # redirect server error pages to the static page /50x.html
       #
       error_page   500 502 503 504  /50x.html;
       location = /50x.html {
          root   /usr/share/nginx/html;
       }
    }

I have many servers in the config file, even if one server was down, I need to have running nginx. Is there any way to fix it?

Any suggestion to fix this issue would be appreciated.

Docker Nginx stopped: [emerg] 1#1: host not found in upstream

So I&#39;m new to ecs/ecr, but it seems like I have to name (with a tag) the image after the repository name in order to push that image to the repository.

So my question is: Is it intended that the user (me) would ONLY be pushing a single image and any associated versions of that image to a single repository in ecr, thus creating ANOTHER repository if i need to push a completely different image?

basically, one repo for nginx, one repo for postgressql, etc.

ECS/ECR: is common practice to have one repository per image (and associated versions)?

How can I create an AWS ECR repository if it doesn&#39;t already exist?

All Amazon Ecs Solutions on Gang of Coders

Total of 14 Amazon Ecs Solutions