5 ms·
> However for my own projects, we consider local development like this an anti-pattern. IaC tools like Terraform/CDK/SST make it easy to spin up environments fo
by movedx 5y ago
> However for my own projects, we consider local development like this an anti-pattern. IaC tools like Terraform/CDK/SST make it easy to spin up environments for each developer in the cloud.
But what do you test your IAC against? If you consider using something like Terratest, then combining it with LocalStack means you can run Terratest nearly instantly and test your IAC.
Plus developers being able to run "AWS" locally menas they, too, benefit from the instant feedback loop. That alone is a good enough reason to use LocalStack, but there are other massive positives: no credentials to a real AWS account to leak; no developers spinning up some new AI tool 'cos it looks cool; and more.
- thdxr 5y agoWe test it against real AWS deployments. With a proper multi-account strategy + SSO, there are no AWS credentials to leak + blast radius is limited. The feedback loop is definitely a problem but projects like SST return the instant feedback loop to you.
- genewitch 5y agoThe credentials are the API keys and secrets, not the login and passwords. One improper setting in IAM and an accidental pastebin or GitHub means half the automated hacks have access to the same thing the IAM user does. I did this once on accident by hitting control-V instead of control-c and overwriting my censored version before pasting into GitHub so other people could save the 4 hours of tedious scripting I had to do. GitHub sends an email within minutes, but I was already miles away from a computer when I got the email...
- movedx 5y agoAnd I think this can be a good idea, but only sometimes. Mostly I think you should just use LocalStack.