4 ms·
I like AWS multiple accounts support it helps securing specific environments, but I don't like that going this route increases the cost. Here are some things I
by takeda 9y ago
I like AWS multiple accounts support it helps securing specific environments, but I don't like that going this route increases the cost.
Here are some things I don't like:
1. if you want to use AWS support, you need to purchase it per account, otherwise support will refuse any help that involves anything specific to the account (they will only respond with generic documents)
2. with separate account you need to recreate the same components (and therefore pay more) for example if you want internet access on your VPC over IPv4, you need to set up a NAT instance per account, you can't for example use VPC peering and use NAT instance on another account
3. you are being charged for any data going between accounts even if same AZ is used. Yes, I understand that one can't easily tell which AZ is which across accounts since they are randomized per account but still...
- deleted 9y ago[deleted]
- mentat 9y agoIf you use the same billing account I'm pretty sure 1 is not true. I only know at higher support levels though it is not a problem for sure.
- takeda 9y agoWell, I don't have access to the root account to see if these accounts are under the same billing account (but best of my knowledge it is), and the support we purchased is Business. When I had question related to one of account I was told that I will need to open a support ticket on that account, but I couldn't open because they had basic support. We contacted our TAM and he just shrugged. If this is true that would be great. Edit: I checked and looks like our account are consolidated until single master one, although we did not purchase support for the master account since nothing is running on it. If there is a way to not have to purchase separate support I would like to know since it could save some money.