Browse through the questions and answers listed below or filter and sort to narrow down your results.
How to deploy Amazon Linux on a Lightsail Container Service?
Hi, I'm trying to deploy Amazon Linux from this public repo public.ecr.aws/amazonlinux/amazonlinux:2018.03 on my Lightsail Container Service. I don't specify any specific launch command. I'm using a Micro instance: Micro (1 GB RAM, 0.25 vCPUs) ×1 node The deployment starts and the fails and this is the log output: ``` [26/Aug/2022:10:09:32] [deployment:1] Creating your deployment [26/Aug/2022:10:10:22] [deployment:1] Started 1 new node [26/Aug/2022:10:11:42] [deployment:1] Started 1 new node [26/Aug/2022:10:12:51] [deployment:1] Started 1 new node [26/Aug/2022:10:13:33] [deployment:1] Canceled ``` Do I need to specify some command or what is the problem here? I want to use this image as a foundation to locally deploy my own written application in it and make it available on the net using the Lightsail Container Service. Best Regards, Frank
Deployment of Amazon Linux 2 on Lightsail ECS is canceled
wanted to deploy the "Amazon Linux 2"-image (public.ecr.aws/amazonlinux/amazonlinux:2022) on a Lightsail Container. It takes a while and then the deployment is cancelled. This is the log output: `[19/Aug/2022:12:07:25] [deployment:1] Creating your deployment [19/Aug/2022:12:08:48] [deployment:1] Started 1 new node [19/Aug/2022:12:09:57] [deployment:1] Started 1 new node [19/Aug/2022:12:10:56] [deployment:1] Started 1 new node [19/Aug/2022:12:11:23] [deployment:1] Canceled Why is her starting three nodes? I have only one node. This happens with other Linux-Distributions too, for e.g. Ubuntu-20.4. I have no idea why this is happening. Any help is greatly appreciated. Best Regards Frank
JSON not working as a command in ECS
I have a json command which I use to setup some configuration settings in my containers and it works fine when used with docker compose and also when I use ecs-cli to deploy it on ecs. When I try to create new revision of the task definition by changing some port values in the command it gives JSON error as it adds and addition " to the command which leads to the failure. Now the task definition created from the cli for fine if I don't touch the command. Is there a fix for it.
ECS Fargate task fails with InvalidDhcpOptionID.NotFound
Trying to launch an ECS Fargate task in a VPC that **does not have a DHCP option set**. The task fails with: Unexpected EC2 error while getting DHCP options for VPC vpc-NNNN: InvalidDhcpOptionID.NotFound. Is DHCP option set required? How is it being used? Is there a workaround other than setting a DHCP option set? Thanks.
Running NextJS on ECS + Fargate
Hi! Would like to know if it is possible to deploy a NextJS app with SSR on AWS ECS + Fargate? After deploying I face a 500 server error, and googling returns a similar issue here: https://github.com/aws-amplify/amplify-js/issues/8049 Would love to know if anyone has experience with this. Thanks!
Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized ERROR
Hi, I have this error when I am creating EKS 1.21 cluster via console: Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized ERROR
Will ECS terminate a task if health check fail during service update termination phase?
If I have health check defined for 30 second interval and 3 failures allowed and termination grace period for task set to 3 minute. Assuming that on SIGTERM due to service update, I stop receiving new requests and task takes 150 seconds to gracefully stop, will ecs terminate my container after 90 seconds since its health checks will fail due to webserver not responding to new requests. This is a concern because I had similar issue with k8s https://github.com/kubernetes/kubernetes/issues/107473
CI/CD on AWS extremely slow
Hi, So I've configured CodePipeline: connection to GitHub, CodeBuild (builds a Docker image and pushes it to ECR), and deployment using Amazon ECS on a Fargate cluster via service with task number = 1, minimum healthy=50%, maximum healthy=140%. It takes astonishing 8 minutes(!) to build and push a simple container, also from the logs it is obvious the Docker layer cache is not used. And then the deployment stage takes ~10 minutes. This is unreal. Is it supposed to be that slow? Are there any ways to make it faster? Thank you.
Connect to the database in an EC2 instance from the ECS cluster
I have Superset deployed on AWS using the guide https://aws.amazon.com/quickstart/architecture/apache-superset/ where I chose to deploy it in an existing VPC. The Superset deployment worked out alright and I can access Superset at the provided link. When I try to connect to a database which is hosted in an EC2 instance, within the same VPC, I get the error, port 5432 is closed message on my Superset. The DB is up and running in the EC2 instance, which has been verified locally and remotely through my laptop. I was previously able to connect to a database on RDS by adding the security group of the ECS Superset to the security group of the RDS instance. The same technique did not work for the ECS (Superset) -> EC2 (DB) connection. I also tried adding the IPv4 subnet range like 172.**.**.0/20 to the EC2 security group without success. These subnet ranges were obtained from the ECS deployment. Any help to debug this issue would be greatly appreciated.
Is it possible to create a QueueProcessingFargateService with read-only root filesystem with cdk?
AWS Foundational Security Best Practices v1.0.0 has a high risk check [ECS.5] ECS containers should be limited to read-only access to root filesystems. The remediation explains how to change this in the console. However, I haven't found a way to do this for a QueueProcessingFargateService using CDK. If a QueueProcessingFargateService could be created without an image, this could have been solved by calling add_container on the task definition, but image is mandatory so that doesn't work. Does anyone know if it is possible to create a QueueProcessingFargateService with read-only root filesystem and if so, how?
Looking for an ecs/eks fargate + cloudwatch + sqs example
Hello all, I'm looking for a complete working example for ecs/eks fargate + cloudwatch + sqs architecture (see Fig 5) that is described in this article - https://aws.amazon.com/blogs/architecture/rate-limiting-strategies-for-serverless-applications/ Any pointers is very much appreciated.
CI/CD on ECS Fargate
Hi AWS, I am following this blog post https://aws.amazon.com/blogs/containers/ci-cd-pipeline-for-testing-containers-on-aws-fargate-with-scaling-to-zero/ to learn about building CI/CD pipelines for containers on ECS Fargate but while accessing the CloudFormation Template and Dockerfile stored in the zipped format I am getting the following error. Here is the URL for the files stored: https://d268s23yov0ww.cloudfront.net/aws-autostart-pipeline.zip and here is the error screenshot: ![Enter image description here](/media/postImages/original/IMx8RvGVrxRcWF4QLdlmXCJw) Please acknowledge this as I am stucked because of the same. Thank you