4 ms·

I gave up on AWS when I realised you can’t deploy a container straight to ec2 like you can on GCP. For bigger things, yeah the support’s better, for anything sm

I gave up on AWS when I realised you can’t deploy a container straight to ec2 like you can on GCP. For bigger things, yeah the support’s better, for anything small to mid GCP all day. Primitives that actually make sense to how we use containers and such these days. And Bigquery

PaulRobinson 2y ago
For containers, you don't want EC2, you want ECS, possibly even Fargate depending on your use case. They're different compute primitives based on your needs. There isn't a boxed product like Bigquery, but the pieces are all there - DynamoDB, Athena, Quicksight...
antonhag 2y ago
For AWS the solution for container deployments (without dealing with VMs) is Fargate, which imo works reasonably well.
- dkersten 2y ago
  I believe I was actually trying to use that. It’s been a few years so my memory is hazy, but isn’t Fargate just a special case of ECS where they handle the host machines for you? In any case, the problem wasn’t so much ECS or Fargate, beyond the complexity of their UI and config, but rather that Cloudwatch was flaky. The problem that prevented the deployment was in my end, some issue preventing the health check from succeeding or something like that, so the container never came up healthy when deployed (it worked locally). The issue is that AWS didn’t help me figure out what the problem was and Cloudwatch didn’t show any logs about 80% of the time. I literally clicked deploy, waited for the deploy to fail, refresh Cloudwatch, saw no logs, click deploy, repeat until logs. It took about five attempts to see logs. Every single time I made a change (it wasn’t clear the error was on my end so it was quite a frustrating process). On digital ocean, the logs were shown correctly every single time and I was able to determine the problem was on my end after a few attempts, add the required extra logging to track it down, fix it, and get a working deployment in under ten minutes.
Kindling7257 2y ago
I'm not trying to defend AWS, they are kinda shit, but deploying containers straight to EC2s is an extremely supported feature and it is very clear how to do it in the ECS admin panel https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-capacity.html https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...

PaulRobinson 2y ago

For containers, you don't want EC2, you want ECS, possibly even Fargate depending on your use case. They're different compute primitives based on your needs. There isn't a boxed product like Bigquery, but the pieces are all there - DynamoDB, Athena, Quicksight...

antonhag 2y ago

For AWS the solution for container deployments (without dealing with VMs) is Fargate, which imo works reasonably well.

dkersten 2y ago
I believe I was actually trying to use that. It’s been a few years so my memory is hazy, but isn’t Fargate just a special case of ECS where they handle the host machines for you? In any case, the problem wasn’t so much ECS or Fargate, beyond the complexity of their UI and config, but rather that Cloudwatch was flaky. The problem that prevented the deployment was in my end, some issue preventing the health check from succeeding or something like that, so the container never came up healthy when deployed (it worked locally). The issue is that AWS didn’t help me figure out what the problem was and Cloudwatch didn’t show any logs about 80% of the time. I literally clicked deploy, waited for the deploy to fail, refresh Cloudwatch, saw no logs, click deploy, repeat until logs. It took about five attempts to see logs. Every single time I made a change (it wasn’t clear the error was on my end so it was quite a frustrating process). On digital ocean, the logs were shown correctly every single time and I was able to determine the problem was on my end after a few attempts, add the required extra logging to track it down, fix it, and get a working deployment in under ten minutes.

Kindling7257 2y ago

I'm not trying to defend AWS, they are kinda shit, but deploying containers straight to EC2s is an extremely supported feature and it is very clear how to do it in the ECS admin panel https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-capacity.html https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...