Load_Balancer | Load balancer using C | Load Balancing library

aws_lb_listener is part of AWS ELBv2, which is only for Application Load Balancers and Network Load Balancers. You stated you are creating a classic load balancer. I don't think you can update the certificate of a CLB through Terraform if Terraform itself is not managing the load balancer.

Is there any reason you are using a CLB instead of the newer ALB? Either way, the correct method to do this is by passing the ARN of the SSL certificate directly to the Elastic Beanstalk resource, as a setting:

In your resource "aws_ecs_task_definition" "app" you have specified an execution_role_arn, but you have not specified a task_role_arn. That's really what the error is saying, that you need to provide a task role ARN.

The execution role gives the ECS service permission to do things like read an image from an ECR repository, and lookup secrets in SecretsManager that it needs to inject into the containers it creates.

The task role gives the software running inside the ECS task/container permission to access AWS resources. The command execution permissions need to be assigned to the task role, not the execution role.

At a minimum you could try adding:

Clusters are Region-specific. that could be the reason.

Network Load Balancers now support connections from clients to IP-based targets in peered VPCs across different AWS Regions.

Make sure your VPC has peered connection to target resource

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html

All your apt commands do not have -y flag. Which means that your script will hang for manual confirmation to perform any updates and installations.

There could be other issues, but this one is the most apparent one.

I took a look at that module. The problem is that the version 3.17.0 of the module simply does not have the output of security_group_id. You are using a really old version.

The latest version from the site is 4.7.0, you would want to upgrade to this one. In fact, any version above 4.0.0 has the security_group_id, so you need to at least 4.0.0.

Both roles must have a trust policy that allows ecs-tasks.amazonaws.com.

See this document for the task role, and this document for the execution role.

From the ELB2 API documentation [1]:

I had a related problem because the directory has not yet been created, there is a property in root_directory that allows creating the directory with proper permissions.

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/efs_access_point#creation_info

In the example I use root, but you can set another gid.

Remove the .terraform folder and try terraform init again

OR

error is because there's no S3 bucket created to sync with.

• remove json object of s3 in .terraform/terraform.tfstate
• remove the object generating remote backend run
• terraform init