fargate-cloudformation-example

I have been using a modified version of this for 8 years. I didn’t write it https://github.com/1Strategy/fargate-cloudformation-example/... It’s never taken 30 minutes to pass in a new parameter value for the Docker container. Also as far as rollbacks just use —disable-rollbacks. The only time I’ve had CFT get stuck is using custom resources when I didn’t have proper error handling and I didn’t send the failure signal back to CFT. This is with raw CFT using SAM.

Fair point, I’m working on a project now that doesn’t require responsiveness - it’s not user facing. We were burned so bad by Lambda cold starts for user facing lambdas that were backing websites we said forget it and just used ECS/fargate. This is my go to template - I didn’t write it. I found it 7 years ago. https://github.com/1Strategy/fargate-cloudformation-example/... You just update the parameter for your container image and redeploy. Of course you have provisioned concurrency that can help. But the easiest way to test Python lambdas locally is just to run it like any other Python script and call your event handler with the event you want to test

I’ve used a modified version of this for 8 years - I didn’t write it. Updating your ECS Docker image is just passing in the parameter of your new image and updating the cloudformation stack. https://github.com/1Strategy/fargate-cloudformation-example/...

That’s actually a good point. It’s been 6 years since I have deployed to EC2. I have been doing Lambda or ECS/Fargate. But when I did it was either: 1. Azure DevOps with agents on EC2 2. Octopus Deploy with agents (not my choice) 3. CodeDeploy with agents All of those are horrible choices. On the other hand, my Fargate deployments have all been: 1. Create Docker container 2. Push to ECR 3. Deploy a parameterized CloudFormation template to update an ECS cluster. I’ve used a modified version of this template for 7 years. I’m not the author. https://github.com/1Strategy/fargate-cloudformation-example/...

You can’t edit Lambda code in the console when you deploy a Docker image to Lambda. As far as flexibility, while there have been third party libraries that let you deploy your standard Node/Express, .Net/ASP, Python/Flask app to Lambda, now there is an official first party solution https://github.com/awslabs/aws-lambda-web-adapter And as far as ECS, it is stupid simple I’ve used this for years https://github.com/1Strategy/fargate-cloudformation-example/...

I went from not knowing Docker to having a production capable ECS/Fargate microservice spun up within less than a week. I based it on this CFT https://github.com/1Strategy/fargate-cloudformation-example/... And this walk through for C#. I had a similar walkthrough for building a container for a Node service. https://aws.amazon.com/blogs/compute/hosting-asp-net-core-ap...

I agree. I didn’t know anything about Docker - and I am still no expert. I put our entire CI/CD pipeline based on two or three easy to follow articles. After you run dotnet publish https://aws.amazon.com/blogs/compute/hosting-asp-net-core-ap... I never bothered to go through the manually steps. I used the CF template above. Here is the complete Docker file for containerizing an ASP.Net Core API. FROM microsoft/aspnetcore:2.0 WORKDIR /mymvcweb COPY bin/Release/netcoreapp2.0/publish . ENV ASPNETCORE_URLS http://+:5000 EXPOSE 5000 ENTRYPOINT ["dotnet", "mymvcweb.dll"] When you create your registry in ECR. It gives you the Docker commands Here is the CF Template: https://github.com/1Strategy/fargate-cloudformation-example

My experience with Fargate: I had a Node/Express microservice running in lambda using the lambda proxy integration to send and receive files from/to S3. I knew in advance that the 6MB request limit for lambda was going to hit us, but it was good enough for what we needed right then. When it came time, I knew I was going to have to convert to Fargate but I didn’t know anything about Docker or Fargate. It took less than a day for me to get the API up and running in Fargate following this tutorial. https://medium.com/@ariklevliber/aws-fargate-from-start-to-f... And automating it with Cloud Formation https://github.com/1Strategy/fargate-cloudformation-example To be fair, I did have experience with the other fiddly bits of AWS and CloudFormation so I knew how to modify the template to work in our own environment.