ecs-service | CLI tool for deploying services | AWS library

I am working with Terraform to deploy an ECS Service with some containers. Code is so long so I was trying to move all logic to locals.tf.

Right now, my code at container definition is like this:

I have the following cloudformation stack which defines an ECS Service:

I have a minimal stack for creating a simple service with a listener. The listener gets created first and succeeds. The service gets initiated next but gets stuck on "CREATE_IN_PROGRESS". Now I have seen this issue on SO but that has a clear reason for it failing. In my occasion the Cloudtrail logs simple show the initiation and 10 minutes later (custom timeout) the delete but nothing in between. The Cloudformation dashboard events also just show initiation and delete thereafter.

The service does not get created during this time either. This I visually checked by going over to the services and having other services there but not my own.

I have trimmed down the cloudformation template to the bare (i.e. only listener and service with reference to existing resources) but it still gets stuck.

Apart from the usual cloudtrail and cloudformation logs, what could I do to identify the problem?

[EDIT] Here is the template I use. The parameters are based on my current setup.

What's the way to overcome the circular dependency problem in AWS CDK: Let's imagine I have a stack for ECS cluster and a stack for ECS Service (several of them):

I am using Circle CI to build and push the image to AWS ECR, then use this image to deploy a container(with FARGATE as instance) in a service inside a cluster in AWS ECS. The problem is, the tasks are being run outside of this service, but in the same cluster.

Here's task sitting along the task that was started automatically by AWS: The one that has group called service:adp-ecs-service is the one running inside service and the one with group adp-ecs-service is the one that is running outside of service. The one that has group called service:adp-ecs-service will be restarted automatically with the image in ECR tagged 'latest_ci', if i stop it, but other one won't start. And this service can only have one service at a time.

By looking at group in this image, I tried to specify the name of the service in group tag in 'config.yml' file in multiple ways, but to no avail. Here's all I have tried(you can see these in my commits here):

1. 'service:adp-ecs-service'
2. service:adp-ecs-service Both of them(with and without quotes) genereted following error:

I am using Terraform to deploy my ECS cluster with Load Balancer. My Terraform code is as follows:

on bitbucket, the config is required to use both 'service' and 'task definition', I think this is redundant because the service already assigned with task definition, or we have an explanation?

Hi I am trying to create a cluster with service and task. I have a python app in Ecr that connects to redis container. The issue is I am unable to create ec2 instance with autoscaling. Myservice in Cluster and Autoscaling doesn't builds.

Cluster:

I am trying to create following infrastructure using terraform. LoadBalancer -> ECS-Service -> Fargate (nginx images, count=2)

After applying terraform plan, I can see that a target groups shows two healthy targets. But when i try to access loadbalancer dns name from browser, I am getting request-timeout. Ping is also not working for lb dns name.

Loadbalancer is an non-internal application loadbalancer with security-group allowing all traffic on 80 port to all IPv4.

Need help.