amazon-ecs

Why can't my ECS service register available EC2 instances with my ELB?

我只是一个虾纸丫 提交于 2019-11-27 17:39:06
问题 I've got an EC2 launch configuration that builds the ECS optimized AMI. I've got an auto scaling group that ensures that I've got at least two available instances at all times. Finally, I've got a load balancer. I'm trying to create an ECS service that distributes my tasks across the instances in the load balancer. After reading the documentation for ECS load balancing, it's my understanding that my ASG should not automatically register my EC2 instances with the ELB, because ECS takes care of

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

若如初见. 提交于 2019-11-27 10:59:23
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'm receiving the following error: "A client error (InvalidParameterException) occurred when calling the RunTask operation: No Container Instances were found in your cluster." 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

terraform-ecs. Registered container instance is showing 0

删除回忆录丶 提交于 2019-11-27 07:20:55
问题 On running terraform apply it is creating a cluster, service, ec2 instance. But Registered container instances is 0, running tasks count is 0. I tried changing ecs.amazonaws.com to ec2.amazonaws.com but it is throwing an error: aws_ecs_service.nginx: InvalidParameterException: Unable to assume role and validate the listeners configured on your load balancer. Please verify that the ECS service role being passed has the proper permissions. provider "aws" { region = "us-east-1" } resource "aws

Linking containers between task definitions in AWS ECS?

元气小坏坏 提交于 2019-11-27 01:00:19
问题 I'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'd like to have separate task definitions so that I may scale the two separately. I registered my first task definition as david_mongodb successfully in ECS. It has a container named david_mongodb in it. Then I attempted to register my second task definition as david_web , which has a container named david_web that links the database via

docker login unknown shorthand flag: 'e'

亡梦爱人 提交于 2019-11-27 00:55:24
问题 I just updated my docker version and found out that command aws ecr get-login is not working anymore. Got error: unknown shorthand flag: 'e' in -e`. Seems that docker doesn't support -e flag anymore. Is there a way to fix this? Installed versions: aws-cli/1.11.111 Python/2.7.10 Darwin/16.6.0 botocore/1.5.74 Docker version 17.06.0-ce-rc5, build b7e4173 回答1: add this to your call --no-include-email here is the new valid syntax : aws ecr get-login ${normal_params_here} --no-include-email aws ecr