alt Hacker NewsI have been working with AWS for almost a decade on professionally and never saw a reason not just to run test and develop in a real isolated AWS account with security policies (guardrails) and give out accounts with budget alerts.
I have been working with AWS for almost a decade on professionally and never saw a reason not just to run test and develop in a real isolated AWS account with security policies (guardrails) and give out accounts with budget alerts.
We all have personal AWS environments and use them as need arises at my org. Doesn't stop the fact cloudformation deployments take inordinate amounts of time for seemingly no reason. Basic shit like pushing a new ECS task takes 10+ minutes alone. Need to push an IAM policy change by itself? 5 minutes. Maybe it's the CDK, but we've only been on that a couple years, prior we used a ansible and cloudformation templates directly but it wasn't any better. This compounds with each dev and each change across multiple stacks. Not only that cloudformation easily gets "stuck" in unrecoverable states when rollback fails and you have to manually clean up to clean up drift which can easily eat your entire day. I'll note that our stacks have good separation by concerns, doesn't matter. A full deployment of a single ECS service easily takes 30 minutes. This is so wasteful it's absurd. I'd love to NOT have to use a shim like LocalStack but the alternative is what?