Am I understanding AWS Accounts correctly?
I'm coming from Google Cloud, where there is a clear concept of Organizations and Projects. Inside an Organization, you create projects and can easily jump between them.
I'm moving some infrastructure to AWS and have been reading about Organizations and Accounts.
I'd like to have one organizations, with three infrastructure OUs for each environment (dev, staging, production).
From what I've gathered, I add an Account to an Organization, specifying an email, name, and IAM role.
Once that account is created, I sign in with "root" credentials with that email, clicking Forgot Password because now AWS account exists with that email address yet.
I get the lost password email, set the email, and complete the sign up process by:
- Provide contact information
- Agree to the terms of the AWS Customer Agreement
- Provide a payment method, such as a credit card
- Complete phone verification
- Choose a support option
At that point, I can begin administering resources under this Account within the Organization.
Is that right? Because this whole process seems fundamentally flawed. I have to be missing something here, but I cannot find anything.
Does it seem right that:
- I'm creating accounts with aforementioned process?
- I'm setting billing details for each Account, when I'm attempting to make the account that owns the Organization the Payer?
- I have to login to a separate account to administer anything related to that account, despite each Account belonging to the same Organization?
Posted Nov 1, 2019, 1:42 PM UTC
I've talked with AWS technical reps a bunch about this.
They talk a lot about setting up an "account vending machine" -- you should read up on that term. I haven't actually used that pattern myself, though, by way of not needing to yet.
The "Account" in AWS is the strictest, most rigorous level of authorization. Cross-account communication is denied by default, and AWS has put a lot of work into ensuring account data, access, or authorization can't leak over to other accounts. You *can* explicitly permit cross-account communication in a number of ways, though.
This leads to some important points:
Anyway, I don't know anything about GCP so I can't map the AWS concepts to GCP ones. It just strikes me that you are asking about their "account vending machine" pattern.
Here's an example article that dives into this pattern: https://aws.amazon.com/blogs/awsmarketplace/automate-aws-account-provisioning-and-server-migration-using-aws-service-catalog-and-cloudendure-from-aws-marketplace/
Their new product called "Control Tower" can be used and it has an "account vending machine".
Wanted a Account Vending Machine. Looked into it but it required a 'Landing Zone' which included a lot of stuff we didn't need and there seemed to be no way to disable.
Ended up scripting account creation with Ansible, not brilliant but better than doing it manually.
That is all what Control Tower is meant to provide. Control tower will install a landing zone and set up an AVM for you.
This is really what the technical reps talked about -- this concept as a pattern, but not with any specific tool. i.e. using Ansible totally satisfies the pattern.
It does, but it was some effort to get working, as opposed to the AVM which was created exactly for our needs and I assume does what we want without the time we spent cobbling scripts together. If only we could have just had the AVM and not all the other Landing Zone stuff!
Sadly Ansible couldn't handle all of it and we had to supplement with bash scripts. Some of it was down to Organisation module limitations and a lot to password entry/creation/storage - we pushed the limits of Ansible Vault.
Fair enough for Ansible really as this is in that 10% long-tail of low priority feature requirements... I guess all tools (Terraform?) have a similar 10% although maybe in different areas.
I’m curious, has anyone used control tower yet? It doesn’t look like it has an API. Isn’t that unusual for AWS?
Yes, lots of companies. Admittedly it is very early yet and so some of the missing features do prevent some companies from using it (especially given that you currently can't migrate to it, you have to start "clean" as it were).
But, as with most AWS services it will gain features quickly and more and more companies will use it.
Previously, I had 3 accounts myself for personal use of some different things. I created a whole new account to create as my "master" and moved my workloads over to three new accounts in Control Tower just so I can get the security benefits and central "view" it provides. (I'm also checking out the other new service Security Hub.)
True. But Control Tower is unique in what it is and what is intended to do. So, I don't know if it will ever have an API. The AVM sort of does have an API since it is just a "product" offered in Service Catalog.
Anyway, if you have any questions I'm happy to answer them given I have first-hand experience in my own accounts.
100% agree except for one point:
IF the password is a strong password that you've never used elsewhere, changing it frequently actually adds additional risk and is no longer considered best practice.
yeah. i actually considered leaving that one off. there is a lot of industry confusion around this particular item. For example
personally, at work, I follow whatever standard my workplace requires for some sort of compliance reason. at home, I try to use long passwords I don't know.
Did you pull that out of your ass? Or are you going to cite something? Because I have not heard this, and an old ass backup that gets compromised would have your active password(unique or not). So this information seems incorrect.
Why would backups contain passwords?
if you snapshot a VM the password file and ldap shit are in there. If you dump a database with users to a website, the hashed passwords are in it. If you run a mailserver that uses virtual accounts, those users/passwords are in the backup. If you backup your mailserver, you have a pretty reasonable possibility that users have passwords in their mailbox. Passwords still need to be rotated.
EDIT: okay, fine, fine, but when your shit ends up in password dumps on darknet that get found years later, and your password is still valid, that shit is on you.
Here's some reading for ya ass hole.
https://lmgtfy.com/?q=why+you+shouldn%27t+change+passwords+often&s=g