3 ms·

AWS ECS is pretty easy to use

• smackeyacky 4y ago
  It's not the most obvious thing to set up, but once it's set up it's basically set and forget. I prefer to use the AWS CLI, so you'll have to install that. Then it's a matter of setting up an aws-ecs-tools-defaults.json file so that the AWS CLI knows what to do with your container. Docker documentation: https://docs.docker.com/cloud/ecs-integration/ https://docs.docker.com/cloud/ecs-integration/ AWS documentation: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...
• thiht 4y ago
  How is it easy? I'm trying to deploy my container and so far I needed to create: - a task definition - a cluster - a service and it hasn't even asked me for environment variables yet. The cluster definition asks me for network configurations, instance selection (I chose a t4g nano but the default was an expensive one, without any pricing on sight). It's NOT easy. I abandoned because I have no idea how much it’ll cost me. I’ll try some of the other suggestions.
  • tedmiston 4y ago
    This is classic AWS in terms of having many abstractions and small components. To be fair, all of the other PaaSes are doing something similar, they're just abstracting it away from the end user. There are abundant configuration options across ECR + ECS Fargate, but for a basic container with a few environment variables you can use the defaults for almost all of them. Also, after the initial setup, things like deploying a new version, adding / updating configuration, scaling up, etc are pretty easy to maintain.