News for hackers. Stuff that matters.
Re:Principles for Building New SaaS Products on AWS by gfodor on Tuesday May 05, 2020 @06:46PM (#23086018)
What’s the right granularity to shard aws accounts? I haven’t gone down this road. Is it madness to consider this as a multi tenant mechanism vs the usual foreign keys in the database approach? Is applying cloudformation across thousands of accounts feasible?
Re:Principles for Building New SaaS Products on AWS by shortj on Tuesday May 05, 2020 @07:50PM (#23086447)
Probably the most useful mechanism I have for determining this is “if this AWS account disappears, how screwed am I / can I recover.”

I tend to separate all of my projects/services, and each of those to environments.

A cold storage AWS account, audit and security (ship logs, config changes, etc), shared services to another account.

If dev account gets hacked, that sucks, but we can clear it out.

It prod gets hacked (and deleted!) that super sucks. But hopefully cold storage and audit accounts can help us out.

If some other services/projects account gets hacked, I don’t want to be worried about impact to unrelated projects.

Re:Principles for Building New SaaS Products on AWS by gfodor on Tuesday May 05, 2020 @07:51PM (#23086464)
Nice approach - for cold storage what do you mean exactly? Manually rsynced backups or something? Most aws services I’ve used that have backups built in I don’t recall having cross account writability.
Re:Principles for Building New SaaS Products on AWS by shortj on Tuesday May 05, 2020 @07:54PM (#23086482)
RDS snapshot copying, EBS snapshot copies, S3 cross account bucket replication, etc. Write only with no entry points into that account from your other accounts. (Preferably its own locked down IAM role with MFA required)
Re:Principles for Building New SaaS Products on AWS by gfodor on Tuesday May 05, 2020 @08:50PM (#23086823)
Cool- stealing this, thanks! Do you do the backups w a scheduled lambda?
Re:Principles for Building New SaaS Products on AWS by jamesblonde on Wednesday May 06, 2020 @12:31AM (#23087914)
We also use test roles on top of separate dev/prod accounts. It has save us already a couple of times when somebody deleted all instances (by mistake), but the blast radius was kept small.
Re:Principles for Building New SaaS Products on AWS by mrkurt on Tuesday May 05, 2020 @06:50PM (#23086046)
I feel like the harder part of that would be migrations on databases and application code deploys. CloudFormation to configure VPCs would probably work fine.

If you're going to do that, though, you may as well do CloudFormation into customer VPCs and let them do all the "paying Amazon".

Re:Principles for Building New SaaS Products on AWS by kevan on Wednesday May 06, 2020 @12:04AM (#23087807)
Think about where you need fault boundaries (e.g. cellular, zonal, regional, global) and match your account structure to that if possible. In practice that usually means one account per cell/zone/region per environment (test/prod).
Re:Principles for Building New SaaS Products on AWS by akhilcacharya on Tuesday May 05, 2020 @10:33PM (#23087419)
What's wrong with region + stage?