aws-cloudformation-templates VS troposphere

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

Seems like an interesting generalized mix of something like https://github.com/cloudtools/troposphere and Ansible from a glance.

The value add would be unifying provisioning and configuration management in a Python-y experience? The lifecycle of each is distinct and that's traditionally where the headaches of using a single tool for both has come in

Under the IaC category, in July 2023, AWS added loops to CloudFormation, finally ticking a box the community has been asking for since troposphere. I suspect that, in combination with the Terraform licensing changes, it may keep people using CloudFormation for a while longer.

Because ECS Compose-X uses Troposphere, I was able to create a very light and simple python library(https://github.com/JohnPreston/troposphere-awscommunity-applicationautoscaling-scheduledaction) to distribute the resource for other Troposphere users to re-use.

Written in house, but the library troposphere is the primary component of how it is built. Example stacks are here.

I am kind of going off topic here, but isn't the point of being an SA to be created with code services to deliver solutions at scale that are cost-effective? How in the hell can you do that when you can't write a simple Python template that generates code at 50 times the rate you can manually? How can you ever be expected to deploy a serverless solution if you can't write any code yourself? There has to be some level of proficiency there.

Wouldn't using troposphere[1] be easier?

[1] https://github.com/cloudtools/troposphere

You might have seen some tutorials on how to set up S3 buckets using the AWS Console. This works fine, but I'm a firm believer of managing your resources with code. I've chosen the native solution of AWS, called AWS CloudFormation. This makes it easier to reproduce the setup if I ever need to tear it down of move it to another account or region. Below is the full CloudFormation template, I've used a framework called Troposphere, a Python library that creates CloudFormation.

For CF for example I no longer write template in yaml or shudders json, and instead I use troposphere.

refer : https://github.com/cloudtools/troposphere