Hacker News Reader

I would recommend dedicating an entire AWS account to this. Or, if you have a solid tagging strategy[0], you can craft your IAM policies to only allow Appliku access to resources tagged with a particular tag.

0 - https://docs.aws.amazon.com/IAM/latest/UserGuide/access_tags...

Separate account will be the best strategy. I prefer having separate accounts for every project. Hustle to login between them, but the best isolation that can be between projects.

Sorry, 'hassle' not 'hustle'.

Hey! Thanks for question. I guess there is an article that needs updating. Appliku only needs AmazonEC2FullAccess.

Well, if you feel that something is off you just revoke credentials.

I will update the article now. Thanks again

The point of a rich authorization model is not to have to rely on feelings.

Google got this right w project focused permissions- accounts work aws side but