amazon-ecs

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 6 months ago . Improve this question I have 2 dockerfile and I want to link them using Aws-ECS service. I want to link them using Ecs Ec2. What steps I should keep in mind to link the container and what network mode should I used. Lets say I want to expose the container on localhost:5000. I

问题 I'm starting a task in ECS using Fargate and after being in PENDING for a little bit it ends up in STOPPED with the following error: STOPPED (CannotPullContainerError: "Error response from daem When I expand out the details I see STOPPED (CannotPullContainerError: "Error response from daemon: Get https://id.dkr.ecr.ap-southeast-2.amazonaws.com/v2/: net/http: request canceled while waiting for connection" with the reason (Client.Timeout exceeded while awaiting headers) So the task can't access

问题 I currently have an ECS task that fails from time to time, with different error codes. I would like to create a CloudWatch event rule that is triggered on such failures. I currently have the following cloud watch event rule, which is triggered only on exit code 1. I would like to be notified of all non-zero errors exit code. { "source": [ "aws.ecs" ], "detail-type": [ "ECS Task State Change" ], "detail": { "lastStatus": [ "STOPPED" ], "stoppedReason": [ "Essential container in task exited" ],

问题 I currently have an ECS task that fails from time to time, with different error codes. I would like to create a CloudWatch event rule that is triggered on such failures. I currently have the following cloud watch event rule, which is triggered only on exit code 1. I would like to be notified of all non-zero errors exit code. { "source": [ "aws.ecs" ], "detail-type": [ "ECS Task State Change" ], "detail": { "lastStatus": [ "STOPPED" ], "stoppedReason": [ "Essential container in task exited" ],

问题 I'm currently having an issue with ECS Service Discovery and Route53 Auto Naming. I have added the Service Registry to the service and all the Hosted Zones records are being populated automatically. But I cannot seem to work out how to resolve the DNS SRV records with NGINX + ngx_upstream_resolveMK. # DNS RESOLVER resolver ns-x.awsdns-xx.com valid=10s; # UPSTREAMS upstream kibana { resolveMK servicediscovery.ecs service=kibana; } # HOST - kibana.example.com server { server_name kibana.example

问题 I'm currently having an issue with ECS Service Discovery and Route53 Auto Naming. I have added the Service Registry to the service and all the Hosted Zones records are being populated automatically. But I cannot seem to work out how to resolve the DNS SRV records with NGINX + ngx_upstream_resolveMK. # DNS RESOLVER resolver ns-x.awsdns-xx.com valid=10s; # UPSTREAMS upstream kibana { resolveMK servicediscovery.ecs service=kibana; } # HOST - kibana.example.com server { server_name kibana.example

问题 I have a task definition in ECS running in awsvpc mode, containing 2 docker containers. My question is how can I communicate between containers in a task definition. Do they act similar to docker-compose? 回答1: Yes, we can communicate between the containers running task. Here is the system architecture And we will use Service discovery for register to Service task (Fargate/EC2 task) This is an example how to launch one service to ECS with CloudFormation ... Resources: DiscoveryService: Type:

问题 I have a task definition in ECS running in awsvpc mode, containing 2 docker containers. My question is how can I communicate between containers in a task definition. Do they act similar to docker-compose? 回答1: Yes, we can communicate between the containers running task. Here is the system architecture And we will use Service discovery for register to Service task (Fargate/EC2 task) This is an example how to launch one service to ECS with CloudFormation ... Resources: DiscoveryService: Type:

问题 I can't find a way to specify a user-data after creating ECS instance definition. Document says You can pass this user data into the Amazon EC2 launch wizard in Step 6.g of Launching an Amazon ECS Container Instance. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/bootstrap_container_instance.html#multi-part_user_data ECS is launched automatically, how do you specify the user data? I want to send /var/log/syslog to cloudwatch and I need to add user data (https://docs.aws.amazon

问题 Context: I am using Circle CI's aws-ecs/deploy-service-update orb to deploy my docker container by pulling the latest image in AWS ECR and deploy it in AWS ECS with AWS EC2 instance. This container is a Machine Learning model that accepts API requests at TCP port 3000(I am using fastAPI for this) and returns the predictions. After I deployed it I couldn't send requests to the public IP of the container instance of the task that deploys the container at port 3000 (This IP is not my EC2