News for hackers. Stuff that matters.
Re:Using the New AWS Secrets Manager for Serverless by scarface74 on Tuesday January 08, 2019 @09:54PM (#18861890)
VPCs are not a substitute for accounts. Most AWS resources must have unique names across the account like lambdas, SQS queues, sns topics etc.

When you have one account you end up prefixing/suffixing resource names for different environments. It gets to be really ugly.

Re:Using the New AWS Secrets Manager for Serverless by sudosteph on Wednesday January 09, 2019 @02:29PM (#18867949)
Not a problem. Just deploy with CloudFormation and it will give you unique names for your resources automatically. You can use the same template for everything and filter by the stack tags it auto adds. Still way easier than dealing with creds, billing, and monitoring for 3 different non-prod accounts. Though I admit that the new aws organizations feature has made the billing setup stuff a little easier.