News for hackers. Stuff that matters.

A comment on Amazon EC2-Classic Is Retiring. Parent comment

Re:Amazon EC2-Classic Is Retiring by jitl on Wednesday July 28, 2021 @10:49PM (#27992269)
Notion (my employer) was 100% Elastic Beanstalk until about a month ago, now we’re 100% ECS. We migrated once our 1200 box cluster started stalling deploys randomly while saying everything was healthy in the API. At that many instances, the some pages in the dashboard would hang the browser.

One bad day, it took like 18 hours from deploy attempt started to AWS resolving the situation by fiddling knobs on their side.

Our deploys on ECS take like 15 minutes.

[ Parent | on HN ]
Re:Amazon EC2-Classic Is Retiring by derN3rd on Thursday July 29, 2021 @03:27AM (#27993837)
Did the migration went easy? We are currently running all our production service through EB as well, but we only had smaller issues (e.g. deployments stalling, health checks not working correctly etc).

Would you recommend to invest time learning how ECS works or had your company hires that managed that?

[ Parent | on HN ]
Re:Amazon EC2-Classic Is Retiring by slownews45 on Thursday July 29, 2021 @01:30PM (#27998981)
ECS and some ECS Fargate work great - I really like that combo. Seems pretty low overhead, and ECS anywhere I've had some luck with just playing around (you can do a local box on a 1Gig link with tons of RAM / Storage etc).

My one compliant is around having fallback to on-remise providers / capacity provider etc support - doesn't seem fully fleshed out across ECS/Fargate/ECS anywhere but I may not have read docs properly yet.

[ Parent | on HN ]