Shared responsibility
AWS secures the cloud; you secure what you put in it
AWS: security of the cloud. Customer: security in the cloud.
This picture is the single most examined idea in the whole exam. The top half is the customer. You are responsible for your data, your applications, identity and access management, the configuration of operating systems, networks and firewalls, and encryption. AWS calls this security in the cloud. The bottom half is AWS: the software that provides compute, storage, database and networking, and the hardware and global infrastructure beneath it. That is security of the cloud.
Shared responsibility · Going deeper
Inherited, shared and customer-specific controls
Shared controls: patch management, configuration management, awareness and training.
Responsibility by service
The more managed the service, the less is yours
The line moves with the service, but your data and your permissions are always yours.
The dividing line is not in the same place for every service. On EC2, you manage the guest operating system and everything above it. On RDS, AWS patches the operating system and the database engine. You keep the data, the users and the network settings. On Lambda, there is no server you can see. You own the code and its permissions. On S3, the same: you own the data and who can read it. Look at the top two rows. They are purple in every column.
Check yourself
A company runs a database on Amazon RDS. Which of these is still the company's responsibility?
The root user
It can do anything, so it should do almost nothing
Protect the root user with MFA, give it no access keys, and keep it for root-only tasks.
Every AWS account starts with one identity: the root user, signed in with the email address that opened the account. It can do everything, and no policy can restrict it. So it is locked away. Turn on multi-factor authentication. Never create access keys for it. Give it a strong password, and do not use it day to day. Bring it out only for the handful of tasks nothing else can do, such as changing the account details or closing the account.
The root user · Going deeper
Tasks only the root user can do
Recognise the list: account details, closing the account, restoring an administrator.
IAM
Users, groups, roles and policies: only a policy grants anything
Users are people, groups hold users, roles are assumed, and policies grant permissions.
Identity and Access Management, IAM, has four parts. Users, one for each person, usually collected into groups so that permissions are managed once. Policies: JSON documents that allow or deny actions on resources. A policy does nothing until it is attached to a user, a group or a role. Roles: identities with no password and no keys, assumed for a time by an AWS service, by someone from another account, or by a federated sign-in. And one rule over all of it: least privilege.
IAM · Going deeper
Inside a policy
Everything is denied by default; an Allow permits; an explicit Deny always wins.
Credentials
People use a password and MFA; programs on AWS use roles
For code running on AWS, the answer is an IAM role: temporary credentials and nothing stored.
How an identity proves itself depends on what it is. A person signing in to the console uses a password, and should add MFA: a code from a device they hold. The command line and the SDKs use access keys. These are long-lived, so they must be rotated and never written into code. Code that runs on AWS should have neither. It gets a role, with temporary credentials that AWS rotates. Other secrets, such as database passwords, belong in Secrets Manager, which can rotate them, or in Systems Manager Parameter Store.
Credentials · Going deeper
Clue words for access management
Identity Center for your workforce, Cognito for your customers.
Check yourself
An application on EC2 must read files from S3. Which arrangement is the most secure?
IAM Identity Center
One sign-in, and the right access in every account
IAM Identity Center is single sign-on for your workforce across all your AWS accounts.
Companies rarely have one AWS account. They have dozens. Their people already have identities in a corporate directory. IAM Identity Center connects that directory to AWS: one portal, one sign-in, MFA once. For each account, an administrator assigns a permission set: read only in production, power user in development. People receive temporary credentials for exactly that. This is the recommended way to give humans access to AWS.
Check yourself
Which statement about the root user is correct?
Lesson complete
You finished “Shared responsibility and your AWS account”
Answer the questions along the way to see your score here.