Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by WrtCdEvrydy | Hacker News Reader

Parent Full thread

WrtCdEvrydy·

The use is that most people use AWS like if it was a datacenter they don't own.

If you're going for AWS, you should consider rewriting a lot of your services to use AWS features well.

Auto Scaling Groups and Fargate EC2 are some common components I see few companies using.

If your instances are the same size through the day, you are doing it wrong!*

*Exception: If you provide the same level of service and traffic 24/7.

View on HN

This is [unfortunately] correct. If you marry your company's destiny to AWS, their managed products are far more cost-effective than using them as a datacenter [no doubt this is intentional by Amazon]. If you're just using the EC2 services, much like owning the hardware, unused CPU and RAM is wasted money.

I recently gave Fargate a try and was very unimpressed with the costs.

Anecdata is terrible, but my experience running 1 Fargate container 24x7 on the lowest specs (0.25 CPU and 512 MB RAM) to handle baseline was was going to cost as much as a no-contract T3.micro EC2 instance with much more capacity (2 CPU and 1 GB RAM). AWS Kubernetes was also a bust at $120/mo just to get started (that's the cost before an EC2 server is provisioned).

Fargate has two flavors, ECS or EC2.

EC2 is just EC2 with scaling groups while ECS is a fully non-managed solution that's for small items.

The ECS one is weirdly difficult to set up. If you just want Docker Repo (ECR) -> deploy with some config -> expose a single ingress point it sounds perfect, but I had a TON of trouble with it recently

ECS is best done through Terraform, there's existing templates that will allow you to do this fairly easily.

If it helps, I had the exact same experience. Setup was possible but involved way too many decisions for the obvious use case.

Reply on news.ycombinator.com