A hands-on AWS security lab in twenty slides, in the console and the CLI: bring back the bucket, the database and the load balancer; create an organization with a test account and assume the cross-account role project-auditor in it; encrypt the bucket with the customer managed key alias/project-data, watch alice and bob refused kms:Decrypt, make alice a key user, and re-encrypt an RDS snapshot to share it; attach the WAF web ACL project-waf to the load balancer with the core rule set and a rate limit; put the test account in a Sandbox OU and block a Region with the SCP deny-other-regions; clean up.
The slides
The tool is a hands-on lab in twenty slides, one step each, with the steps to follow beside a terminal and a picture of
the two accounts and what each holds:
- Introduction: what the lab adds to the project.
- 1. What the lab needs
- Bring back the bucket, the users and the database: from the S3 lab and the database lab, by the CLI.
- Check the load balancer:
project-alb, from session 6.
- 2. A role in a second account
- Create the organization and a test account: our account becomes the management account.
- Reach the test account as its administrator:
OrganizationAccountAccessRole. - Create the role project-auditor in the test account: trusting our account, with
SecurityAudit. - Switch to project-auditor in the console, and assume project-auditor from the CLI.
- 3. A customer managed key
- Create the customer managed key:
alias/project-data. - Encrypt the bucket with the key: SSE-KMS by default, and
notes.txt copied onto itself. - Watch alice and bob refused:
kms:Decrypt. - Make alice a key user: she reads,
bob does not. - Re-encrypt an RDS snapshot with the key, and share the copy with the test account.
- 4. WAF on the load balancer
- Attach the web ACL project-waf to the load balancer: AWS's core rule set.
- Add the rate-based rule rate-limit: 100 requests in 5 minutes.
- Read the blocked requests.
- 5. An SCP on the test account
- Put the test account in a Sandbox OU.
- Attach deny-other-regions to the Sandbox OU.
- Watch the SCP refuse a Region: for
project-auditor, and not for jane in the management account.
- 6. Clean up
The buttons on the left and right edges move between slides. So do the arrow keys and a swipe.
The lab starts where
Getting Started with AWS ends: the CLI works as jane.
The slides
AWS Security in Depth explain what it uses.
The placeholders
Our account is 111122223333 and the test account 444455556666; the key ID, the web ACL's ID and lock token, the
OU's and the SCP's IDs, the load balancer's name and the VPC IDs are in AWS's placeholder forms. 192.0.2.10 is our
computer. The lab has not been run yet: the console steps follow AWS's documentation, and the outputs the CLI's service
model.
Sources