Questions tagged with AWS Fargate

Hi everyone I have 3 microservices running on an **ECS cluster**. Each microservice is launched by a **Fargate task**. Each microservice runs in its own Docker container. * *Microservice A* responds on port 8083. * *Microservice B* responds on port 8084. * *Microservice C* responds on port 8085. My configuration consists of two public subnets, two private, an internet gateway and a NAT, as well as two security groups, one for fargate services and one for ALB. On the security groups I have enabled inbound traffic on all ports. I have defined a listner for the ALB that responds on port 80 and wrote some path-based rules to route requests to the appropriate target group (*every target group is a Target type*) : Only the health check of the target group that responds to the default rule responds ( but I suspect it all happens randomly) , and consequently only the service reachable on port 8083 works  The remaining target groups are **unreachable**. What you notice is that in the "*Registered Target"* section the assigned IP addresses change continuously. For example:  Enter image description here](/media/postImages/original/IMCm7LLgy1QJKk0JsLC3XlGg) But every time IP assigned it generates a timeout. It can happen quite randomly that a certain IP address is registered correctly. These are the ECS configurations of one of the unresponsive services:  What is the problem and how can I solve it? Thank you. **UPDATE1** I tried to add a new instance for microservice A. For the new IP (10.0.0.137) the health check is not responding. After a few minutes, the provisioning of a new IP (10.0.0.151) appears and it is registered correctly:  **UPDATE2** It is really strange behavior. **All services are now connected correctly**, after several hours of failed attempts. It looks like an IP address assignment problem. Before finding the correct address, AWS makes several attempts with different IP addresses until it randomly finds the correct one. These are the CIDRs of my PRIVATE subnets * private_subnets = ["10.0.0.128/28", "10.0.0.144/28"] * public_subnets = ["10.0.0.0/28", "10.0.0.16/28"] While these are the IPs that connected successfully: 1. 10.0.0.136 (micorservice A istance1) 2. 10.0.0.151 (micorservice A istance2) 3. 10.0.0.153 (micorservice A istance3) 4. 10.0.0.152 (micorservice B) 5. 10.0.0.142 (Microservice C)lg...

Context: Workload will be periodic and predictable Don't want to go with on-demand EC2 since most of the time it won't be active. Questions: How we can only spawn an ec2 when we need and close it after it's done with a task? Would fargate be a better choice for this situation?lg...

ECS Task ├Apache Container └Gogs Container We are considering autoscaling with the above Fargate configuration. In terms of autoscaling ・CPU utilization ・Memory usage ・Client concurrent connections We think that these should be monitored, but is there anything else we should consider? Also, is there a good way to monitor the number of concurrent client connections?lg...

In our docker file we specify a user using the USER directive as we'd like to run the task as a non-root user. As we understand this is common good practise. However, the enironmental variables set by Fargate are not visible to this user. How to resolve this?lg...

Hello I have created a private clodmap namespace in a VPC and deployed 3 ECS services in to the VPC. My VPC has DNS resolution enabled. On the ECS dashboard I can see the corresponding service discovery names for my services and they all match the records on CloudMap and route 53 hosted zone. My problem is, from service A, I can not reach to service B using service discovery names even though the resources are inside the same fargate cluster. Interestingly, I can reach from A to B if I use the internal IP address. I believe there is a problem in the resolution of the dns, since there is no response to the dig command. I am attaching the logs when I execute a dig command from service A to B. I really appreciate any help, thanks!  lg...

Running a task using `aws ecs run-task` works well for one-off tasks, except for they always lose internet connectivity within about 5 minutes from starting. Here is the script I'm using to start the task: ```bash export AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID} export AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY} cmd=$(cat <<EOF { "containerOverrides": [ { "name": "${CONTAINER}", "command": ${COMMAND} } ] } EOF ) taskDefinition=$( \ aws ecs list-task-definitions --region us-east-1 \ --family-prefix ${TASK_DEFINITION} \ --output text \ | grep ${TASK_DEFINITION} | tail -n1 | awk -F '/' '{print $NF}' \ ) echo "Running '${SCRIPT_NAME}' using '$taskDefinition' task definition" aws ecs run-task --region us-east-1 \ --cluster ${ECS_CLUSTER} \ --launch-type FARGATE \ --started-by "ManualScript" \ --task-definition $taskDefinition \ --network-configuration "awsvpcConfiguration={subnets=[${TASK_SUBNET}],securityGroups=[${TASK_SECURITY_GROUP}],assignPublicIp=ENABLED}" \ --overrides "$cmd" ``` The container name and task definition family do not have auto-scaling rules, which was my first thought, so I'm not sure how to identify the fix here.lg...

Hi Team, I have created a ECS TaskDefinition then I am creating a ecs cluster. Inside cluster I want to create a service through .net awssdk 2.3.55.2 classes. But I am not able to set vpcid under NetworkConfiguration or AwsVpcConfiguration class. Our code is automatically assigning very first vpcid while creating ecs service. Can you please suggest how can I assign/set vpcid which we require instead of selecting first entry from vpc list? Due to this issue my websites are not launching on containers as containers/service doesn't have correct vpcid assigned. Thankslg...

I have a microservice. What would be the most appropriate and economical infrastructure. The idea is to always keep the same public ip to associate it to the DNS. And that it does not change when we make new deployments. - Use Fargate with Balancer. - Use Api Gateway. - Use Beanstalk with Elastic Ip in an EC2 and without Balancer.lg...

Hello, We are investigating AWS Fargate using Amazon EKS. When reading this document: https://docs.aws.amazon.com/eks/latest/userguide/fargate-getting-started.html It is stated `AWS Fargate with Amazon EKS is available in all Amazon EKS Regions except AWS GovCloud (US-East) and AWS GovCloud (US-West). ` However, when looking at this document: https://aws.amazon.com/compliance/services-in-scope/DoD_CC_SRG/ The table indicates that the feature is available in the Gov cloud regions. Could we please have clarification on whether or not the feature is available in the GovCloud regions? When attempting to create a Fargate profile with in our GovCloud subscription we get the following error; ``` Error: error creating EKS Fargate Profile (fargate-test:default): AccessDeniedException: Account <aws-gov-acct-number> is not authorized to use this service ``` Thank you, Robert Batsonlg...

The type initializer for 'Gdip' threw an exception in ECS service. ECS service is Fargate Linux Server. Could any one help how we can resolve the issue. I have added the below lines in my dockerfile. # install System.Drawing native dependencies RUN apt-get update \ && apt-get install -y --allow-unauthenticated \ libc6-dev \ libgdiplus \ libx11-dev \ && rm -rf /var/lib/apt/lists/*lg...

I would like to operate the currently operating fargate as a private network. So I want to set assignPublicIp to disable, but I wonder if there is a way to do it with console or cli. You can re-edit and redistribute it, but please inquire if there is an easier way.lg...

Hi team, I'm trying to deploy an FIS Experimentation Template (admittedly with terraform) but it doesn't seem to work for fargate. Can AWS FIS execute stop task on fargate, and if so, is there an example configuration (even with AWS Console or json)? * action: ecs:stop-task * target: Clusters (?) Since target seems to only allow clusters, dbinstances, (ec2) instances, (eks) nodegroups, and (iam) roles....wasn't sure if clusters is accurate or if there is a needed enhancement for FIS to support fargate? This was further questioned as I got some valuable feedback on a different thread that FIS's ECS drain containers ONLY works on EC2 launch types, not fargate https://docs.aws.amazon.com/fis/latest/userguide/fis-actions-reference.html#ecs-actions-reference so wanted to explicitly ask about fargate support. Thanks!lg...