load_balancer | simple load balancer based on a presentation by Rob Pike | Load Balancing library

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

Looks like a solid use-case for locals + dynamic blocks.

It will help if you already know the task placement strategies that should be supported in the module. You can expose an input variable to the end-users and use that to create the service accordingly.

For example: Let's say, we want to support two kind of services:

• simple
• complex

I would first define an input variable with validation like this, to avoid the unknowns:

You should be using default_action.target_group rather than default_action.target_group_arn. The default_action.target_group block then has arn and weight as parameters:

We just need to call addRedirect method on loadbalancer.

Default parameters for method already has

Here is the way to get the dns_name from above json output:

Alb for Ecs fargate is for routing to another avaliablity zones? or routing to containers

Not really. It is to provide a single, fixed endpoint (url) to your ECS service. The ALB will automatically distribute incoming connection from the internet across your ECS services. They can be in one or multiple AZs. In your case it is only 1 AZ since you are using desired_count = 1. This means that you will have only 1 ECS service in a single AZ.

If I create a subnet based on the availability zone number (us-east-2a, 2b, 2c, so number is 3 and create 3 subnets) and map it to an ecs cluster with alb, does the availability zone apply?

Yes, because your ALB is enabled for the same subnets as your ECS service through aws_subnet.cluster[*].id. But as explained in the first question, you will have only 1 service in one AZ.

my intent is to build infra which has three availability zone and also deploy aws fargate on three availablity zone.

As explained before, your desired_count = 1 so you will not have ECS services across 3 AZs.

Also you are creating only public subnets, while your schematic diagram shows that ECS services should be in private ones.

I have solved this problem by adding request parameters to the add method.

Got hint from here -> Hint

Just create a map keyed by project and variable name and apply a bunch of resources for each combination:

You can use the splat operator: aws_subnet.rSubnetMGMT.*.id which will resolve to be the list of IDs of the subnets that were created.