aws-cf-templates VS aws-cloudformation-templates

I think any of the common proxy platforms would work, the example code just happens to be for HAProxy. Managing ECS isn't that hard once you get it stood up. https://github.com/widdix/aws-cf-templates widdix provides a ton of reference cloud formation templates that cover most aspects of running aws infrastructure. We run everything through cloud formation and it is self-scaling and self-healing. System manager can automate patch management as well.

https://www.stackery.io/registry/?repo=https://github.com/wi...

Finally, if you’re feeling nostalgic for winter, this example from Symphonia is a lab for benchmarking Lambda cold starts for Java runtimes so that you can better understand how they behave and plan configurations accordingly.

Still, have a look at the CFN example repo for what you're trying to do. You'll see that even AWS chose to not bother with userdata

If you don't like using CLI tools and just prefer to start using the CloudFormation templates directly by yourself then this repo has some examples configurations for load balanced services in various networking configurations: https://github.com/awslabs/aws-cloudformation-templates/tree/master/aws/services/ECS

ECS has it's own format, which is not a direct 1:1 mapping from Docker Compose to ECS service / task definitions. You have to either use a prebuilt tool that does that mapping for your (like the Docker Compose context) or write your own service and task definitions from scratch. If you want to write them in the YAML format then CloudFormation would be the best bet. There are some sample YAML definitions for ECS here: https://github.com/awslabs/aws-cloudformation-templates/tree/master/aws/services/ECS

Example can be found here: https://github.com/awslabs/aws-cloudformation-templates/blob/master/community/services/EC2/ec2_with_waitcondition_template.json *Note it doesn’t haven’t to be as long at that example. Just needs to show a basic functionality with obvious misconfigurations.

If you have special networking needs, or already know AWS pretty well and want it integrated into your environment then you can just build it in EC2. You can either use an AMI from the marketplace to get started or just install it yourself. If going this route and you want to "scale" I'd recommend also setting up an RDS database. You can add a load balancer for SSL termination and have AWS automatically rotate the certificates for you and make sure you enable scheduled AMI and/or RDS snapshots for backups. For OS patching you can use either unattended-upgrades or AWS patch manager. A benefit of this method is that it can be pretty well automated with CloudFormation. Such as with this AWS Labs template:\ https://github.com/awslabs/aws-cloudformation-templates/blob/master/aws/solutions/WordPress_Single_Instance.yaml

A is correct = https://github.com/awslabs/aws-cloudformation-templates/blob/master/aws/services/DynamoDB/DynamoDB_Secondary_Indexes.yaml

Yea, the documentation is a mess, I would recommend checking out the github with samples instead. https://github.com/awslabs/aws-cloudformation-templates

🔗 https://github.com/awslabs/aws-cloudformation-templates