aws-fargate

问题 We are using ECS Farget container service for our ruby on rails containers. We have implemented NLB with HTTP health checks in the target group but as we know that "NLB Target Group health checks are out of control". This is consuming our CPU of each container up to 8% so we are thinking of to migrate HTTP HealthChecks to TCP HealthChecks. Can anyone comment on how TCP HealthCheck works??? Does it only connects to port for a health check or it's actually hit the API? Ref: NLB Target Group

问题 An AutoScalingGroup needs a LaunchConfiguration The problem is that the LaunchConfiguration requires things like ImageId and other parameters which I do not have since I am using containers. How should the LaunchConfiguration be configured when using ECS Fargate? AWS::AutoScaling::AutoScalingGroup https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-as-group.html AWS::AutoScaling::LaunchConfiguration https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws

问题 I'm using AWS ECS to host my services. When I try to define task with fargate, I'm getting this below problem. CannotPullContainerError: API error (500): Get https://xxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Further I gave full permissions to access ECR in the IAM user as well. Please help me to sort out this problem. 回答1: Have a look here: https://github.com/aws/amazon-ecs-agent

问题 During migration on AWS, I created a new cluster on AWS and deployed several docker application with Fargate approach. During each update of task definition, new task is launched inside service and new public IP is assigned from AWS public IP pool Is there any solution or instruction on how I can attach static IP adderes to the service tasks? I saw similar question here How do I associate an Elastic IP with a Fargate container? but still can't find any solution 回答1: see this answer add

问题 I have an API running on ECS Fargate that accepts GET method requests. I put an API Gateway endpoint in front of it with a VPC_LINK integration with an NLB in a private subnet. When I send a GET request using the invoke url, I get a 404 page not found error. I am confused why I am getting this. I set up every component - the NLB listener, the target group, and my host and container ports in my task definition - on 8000/tcp . So, I am not sure why this error is happening. My Fargate task is

问题 I would like to open a Rails console in a Fargate container to interact with my production installation However after searching the web and posting in the AWS forum I could not find an answer to this question Does anyone know how I can do this? This seems like a mandatory thing to have in any production environment and having no easy way to do it is kind of surprising coming from such a respected cloud provider as AWS Thanks 回答1: After trying lots of things, I found a way to open a Rails

问题 If I am running container in AWS ECS using EC2, then I can access running container and execute any command. ie. docker exec -it <containerid> <command> How can I run commands in the running container or access container in AWS ECS using Fargate? 回答1: With Fargate you don't get access to the underlying infrastructure so docker exec doesn't seem possible. The documentation doesn't mention this explicitly but it's mentioned in this Deep Dive into AWS Fargate presentation by Amazon where this is

问题 After migrating from EC2 cluster instances to AWS Fargate, I realized that deployments take a lot longer. Before they would take 1-2 minutes, now some deplyoments take up to 5 minutes. This post claims that their deployments on Fargate even take up to 10 minutes. Does anybody know of a way to speed them up? I can't find any documentation on this topic. 回答1: Through further googling I found this Reddit thread. An AWS employee wrote: With regard to time to provision and start a container it is

问题 I was trying to get answers on my question here and here, but I understood that I need to know specifically Fargate implementation of vCPUs. So my question is: If I allocate 4 vCPUs to my task does that mean that my single-threaded app running on a container in this task will be able to fully use all this vCPUs as they are essentially only a portion of time of the processor's core that I can use? Let's say, I assigned 4vCPUs to my task, but on a technical level I assigned 4vCPUs to a physical

问题 I use to connect to EC2 container instances following this steps, https://docs.aws.amazon.com/AmazonECS/latest/developerguide/instance-connect.html wondering how I can connect to FARGATE-managed container instances instead. 回答1: Looking on that issue on github https://github.com/aws/amazon-ecs-cli/issues/143 I think it's not possible to make docker exec from remote host into container on ECS Fargate. You can try to run ssh daemon and your main process in one container using e.g. systemd