copilot-cli VS aws-cloudformation-templates

AWS Copilot CLI is an open source command line interface for running containers on AWS App Runner, Amazon Elastic Container Service (ECS), and AWS Fargate.

sudo curl -Lo /usr/local/bin/copilot https://github.com/aws/copilot-cli/releases/latest/download/copilot-linux && sudo chmod +x /usr/local/bin/copilot

Check out AWS Copilot CLI: https://aws.github.io/copilot-cli/

This is by far the best way to deploy compute into AWS in containerized workloads.

The abstraction you want is Jobs: ttps://aws.github.io/copilot-cli/docs/concepts/jobs/

Building this any other way on AWS would require provisioning multiple artifacts. The Copilot Jobs abstraction basically encapsulates the provisioning of those artifacts into one repeatable pattern.

AWS Copilot CLI is a tool that lets you deploy production-ready, scalable services on AWS from a Dockerfile in one command.

and here is the copilot page if you are interested https://aws.github.io/copilot-cli/

For larger high availability required things, AWS ECS with RDS, ElastiCache, CloudFront, S3, etc.. Really like Copilot for deployment/env/secret/sidecar management (probably needs a rename now): https://aws.github.io/copilot-cli/

We are spending about 60% less. Workload has actually lessened since AWS is so much more stable. Getting to a similar DX as Heroku was quite the lift, but once it's done, it's done. These days we generally only have outages when we screw something up ourselves. I recommend https://github.com/aws/copilot-cli for starting out on ECS.

I'd recommend checking out AWS Copilot (https://aws.github.io/copilot-cli/)

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