As AWS partners, we perform hundreds of AWS account reviews and we always start at the same place: AWS Account Architecture. The reason is as simple as it is critical; properly setting up your first account can be a game changer, particularly for enterprises with many teams helping to bring solutions to market. Starting with the right architecture that is designed to fit your technology and business needs can make all the difference in ensuring security, compliance, operational efficiency and creating a development environment that inspires innovation. As a result, let’s kick-off this paper in the same place we kick-off our assessments, with AWS accounts.
What is an AWS Account?
To access any AWS web service, you must first create an account. This is simply an Amazon.com account typically associated with a payment instrument (credit card or invoicing) that is enabled to use AWS products. It is also referred to as root, master, or parent and you should not confuse it with creating user accounts. These user accounts are called Identity and Access Management (IAM) accounts. When you create an AWS account, you can sign in to the AWS Management Console and access a variety of AWS services, view your activity, view usage reports, and manage your AWS Security Credentials.