cloudformation-templates | An assortment of CloudFormation templates

I was being silly and doing this

Important point to note to get the syntax right is to use Json with Yaml when using multiple Intrinsic functions. Updated syntax below. For Environment value DEV, this creates a bucket of name content-input-dev

This is a syntax error. One example how it should be for the Replace operation is given in the repository. Here is a template that I was able to deploy, it uses Transform inside FindInMap and creates an S3 bucket with a test-key:test-value tag:

I guess you are referring this sudo java -jar /tmp/app.jar &? I think you should kill it in your Init after your test finishes.

One way to do this could be as follows:

As suggested by @Cyrus, going over to shellcheck.net and making the suggested changes worked.

The solution that solved it - The following piece of the script:

Not really sure what the difference between !Sub 'LoadBalancerRule${!Explode Prefix}' & - LoadBalancerRule!Explode Prefix is, but this worked out

Because Count is a macro, not a custom resource. A macro is a preprocessor for the Cloudformation template. It takes the template, changes it and outputs a new template. Cloudformation then carries on creating the stack using the updated template.

When you delete the stack, it deletes all resources defined in the stack so there is no need to call the macro again.

In contrast a custom resource is executed at deployment and is used to control resources that Cloudformation doesn't support or to implement other custom logic. The custom resource will be invoked when the stack is deleted to give it a chance to clear up the resources it created.

Timeout is often a network Issue. Have you checked security groups used by both the ECS task and Dynamo DB. Need to make sure you have rules setup to egress out of ECS and ingress into DynamoDB on the correct ports.

You said you setup an endpoint for Dynamo in the VPC. Not clear from your OP if you are trying to connect to private endpoint in a private VPC or if you are trying to go through the public internet. If you are trying to go through public internet you need to also check that your ECS task is in a VPC that has a NAT gateway out to the public internet. It looks like you are trying to connect through 127.0.0.1 or an ELB DNS to connect to the DynamoDB service which doesn't make sense to me.

Instead of