Security is the #1 weighted domain on most AWS exams. On the Solutions Architect Associate, it's 30% of the exam. Master security, and you're a third of the way to passing.
Why Security Is Critical
AWS operates on the Shared Responsibility Model:
- AWS is responsible for: Security OF the cloud (physical, network, hypervisor)
- You are responsible for: Security IN the cloud (data, access, configuration)
Understanding this distinction is fundamental to every security question.
Core Security Services
IAM (Identity and Access Management)
The most important security service. Understand:
Identities
- Users (people)
- Groups (collection of users)
- Roles (assumed by services/applications)
Policies
- Identity-based policies (attached to users/groups/roles)
- Resource-based policies (attached to resources)
- Permission boundaries
- Service control policies (SCPs)
Policy Evaluation Logic
- Explicit Deny → Always wins
- Explicit Allow → Grants access
- Implicit Deny → Default (no statement)
KMS (Key Management Service)
AWS encryption key management:
- Customer Managed Keys (CMK) - You control
- AWS Managed Keys - AWS manages for you
- AWS Owned Keys - Fully AWS managed
Key Concepts
- Envelope encryption
- Key rotation
- Key policies vs IAM policies
- Grants for temporary access
Other Security Services
AWS WAF - Web application firewall AWS Shield - DDoS protection AWS GuardDuty - Threat detection AWS Inspector - Vulnerability assessment AWS Macie - Data discovery and protection AWS Secrets Manager - Secrets rotation AWS Certificate Manager - SSL/TLS certificates
The Shared Responsibility Model
AWS Responsibility (Security OF the Cloud)
- Physical security of data centers
- Network infrastructure
- Hypervisor security
- Hardware maintenance
Your Responsibility (Security IN the Cloud)
- IAM configuration
- Data encryption
- Network configuration (security groups, NACLs)
- Operating system patches
- Application security
Varies by Service Type
| Service Type | AWS Manages | You Manage |
|---|---|---|
| Infrastructure (EC2) | Hardware | OS, patching, data |
| Container (RDS) | OS, patching | Data, access |
| Abstracted (S3, Lambda) | Most | Data, access |
IAM Deep Dive
IAM Policies Structure
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::mybucket/*",
"Condition": {
"IpAddress": {"aws:SourceIp": "192.168.1.0/24"}
}
}
]
}
Know each element:
- Effect: Allow or Deny
- Action: What operations
- Resource: Which resources
- Condition: When to apply
IAM Roles vs Users
Use Roles when:
- EC2 instances need AWS access
- Lambda functions need permissions
- Cross-account access needed
- Federated users
Use Users when:
- Long-term individual access
- Programmatic access with keys
- Console access needed
IAM Best Practices
- Never use root account for daily tasks
- Enable MFA on root and all users
- Use groups to assign permissions
- Grant least privilege - minimum necessary
- Use roles for applications
- Rotate credentials regularly
- Use policy conditions for extra security
Encryption in AWS
Encryption at Rest
S3
- SSE-S3 (S3-managed keys)
- SSE-KMS (KMS-managed keys)
- SSE-C (customer-provided keys)
EBS
- KMS encryption
- Encrypted snapshots
RDS
- KMS encryption
- Must enable at creation
Encryption in Transit
- HTTPS/TLS for data transfer
- VPN for network traffic
- Client-side encryption
Key Management Decisions
| Scenario | Solution |
|---|---|
| Simple encryption, minimal management | SSE-S3 |
| Audit key usage, control rotation | SSE-KMS |
| Regulatory requirement for your keys | SSE-C |
| Cross-account access to encrypted data | KMS with key policy |
Security Best Practices by Service
S3 Security
- Block public access (account level)
- Use bucket policies for access control
- Enable versioning
- Enable MFA Delete
- Use VPC endpoints for private access
- Enable access logging
EC2 Security
- Use security groups (least privilege)
- Use IAM roles, not access keys
- Keep AMIs patched
- Use Systems Manager for patch management
- Enable detailed monitoring
RDS Security
- Deploy in private subnets
- Use security groups
- Enable encryption at creation
- Enable automated backups
- Use IAM database authentication
Common Exam Scenarios
Scenario 1: "Developers need temporary access to production"
Answer: IAM roles with time-limited sessions, or temporary credentials from STS
Scenario 2: "Ensure S3 objects are encrypted with company-managed keys"
Answer: SSE-KMS with customer-managed CMK, or bucket policy requiring encryption
Scenario 3: "Third-party needs access to specific S3 bucket"
Answer: Cross-account IAM role or bucket policy with external account
Scenario 4: "Audit all API calls in AWS account"
Answer: AWS CloudTrail enabled for all regions
Scenario 5: "Automatically detect compromised credentials"
Answer: AWS GuardDuty for threat detection
Security Study Checklist
- Memorize Shared Responsibility Model
- Understand IAM policy evaluation logic
- Know encryption options for each service
- Practice writing IAM policies
- Understand KMS key types
- Know when to use each security service
- Complete hands-on IAM labs
Hands-On Labs
Essential security labs:
- Create IAM users, groups, and policies
- Set up MFA for users
- Create IAM roles for EC2
- Configure S3 bucket policies
- Enable KMS encryption for S3
- Set up CloudTrail logging
Identify Your Security Gaps
Security is 30% of most AWS exams. Do you know where you stand?
StudyTech's AI identifies your exact security gaps:
- IAM policies, roles, and evaluation logic
- Encryption options (KMS, SSE-S3, SSE-C)
- Shared Responsibility Model scenarios
- Security service selection (WAF, Shield, GuardDuty)
Over 1,000 learners are using StudyTech to master AWS security faster. Our AI creates a personalized study plan in 10 minutes.
Don't let security questions be the reason you fail. Know your gaps before exam day.