4 ms·
> You have poor architecture, poor tagging, poor VPC design, poor IAM policy and role modelling or don't know what you are doing to start with. Yeah. So you ar
by Aeolun 4y ago
> You have poor architecture, poor tagging, poor VPC design, poor IAM policy and role modelling or don't know what you are doing to start with.
Yeah. So you are saying it’s a great idea for 80% of all companies?
> My favourite thing doing is spending 2 days opening support tickets in 10 different accounts to get a limit raised and then tracking the state of all the tickets and limit changes
I agree this sucks balls though.
- scarface74 4y agoThen don’t do that. There are APIs to both list all of the accounts in the organization and request service limits. It’s a three line bash script. Let me take that back, you have to assume the role in each account using either the autogenerated Organization role or Control Tower role.
- Aeolun 4y ago> There are APIs to both list all of the accounts in the organization and request service limits. It’s a three line bash script. You assume I have access to all that. Then there’s the situations in which you request a limit higher than what they’ll automatically give you, and you end up running through 10 support requests :/
- scarface74 4y agoSurely you aren’t administering your AWS accounts clicking around in the console all day? You are responsible for opening tickets for accounts but don’t have permissions to use the CLI within CloudShell?
- coredog64 4y agoIf you don’t feel like writing the three lines, ask your TAM.