在打印窗口把「目标」选为「另存为 PDF」即可保存,页面已带 awsgood.com 版权水印。 返回原文

www.awsgood.com

SCS-C02 Exam Guide and Study Plan for Working AWS Ops

2026-11-19 SCS-C02 约 5 分钟

TL;DR

Who SCS-C02 is for — and when to skip it

The exam guide's target candidate is someone with several years of IT security work and real hands-on time securing AWS workloads. That's not a gate, but it's an accurate description of the questions. If you have never written an IAM policy that wasn't "Action": "*", the scenarios read like fiction and you burn your 170 minutes guessing.

My personal litmus test before booking: can you explain out loud why a cross-account S3 GetObject fails when the bucket policy looks correct? If yes, you're probably five or six weeks out. If you had to think about it, start with SAA-C03.

Here's the honest "when NOT to take this exam" list. Skip it if your employer just needs a certification checkbox — SAA-C03 costs the same and covers more ground. Skip it if your actual job is hybrid networking, where ANS-C01 is the credential that changes your day. And skip it if you can't get a sandbox account to destroy and rebuild, because reading about SCP inheritance is not the same as locking yourself out of an OU at 23:00 and working out why the break-glass role still worked.

Domain weights, cost and format

Six domains, and the weighting is public. I've seen people spend three weeks on Threat Detection & Incident Response because it sounds exciting, then get 14% of the paper for it.

Domain Weight What it actually asks
Infrastructure Security 20% VPC design, SG vs NACL, PrivateLink, WAF/Shield, edge controls
Security Logging and Monitoring 18% CloudTrail integrity, Config, log pipeline failures, anomaly alerts
Data Protection 18% KMS key policies, S3 encryption and Object Lock, Macie, secrets rotation
Identity and Access Management 16% Policy evaluation order, SCPs, permission boundaries, role trust
Management and Security Governance 14% Multi-account baselines, compliance reporting, centralised guardrails
Threat Detection and Incident Response 14% GuardDuty findings, EventBridge automation, containment and forensics

Format and logistics, from the guide and the registration page: 65 questions, a mix of single-answer multiple choice and "Select two"/"Select three" multiple response, 170 minutes, scaled score 750 to pass out of 1000. It runs USD 300 at list price; regional pricing and local tax change the final number, so check your own currency on the scheduling page rather than trusting a blog. The certification is valid three years and you recertify by passing the current version before it lapses.

Which exam first, if you're sequencing:

Exam Level Questions / time Pass Pick it when
SAA-C03 Associate 65 / 130 min 720 you need architecture breadth first
SCS-C02 Specialty 65 / 170 min 750 you already touch IAM, KMS, CloudTrail weekly
SAP-C02 Professional 75 / 180 min 750 you design multi-account organisations
ANS-C01 Specialty 65 / 170 min 750 your job is Direct Connect and Transit Gateway

The 7-week plan and the lab commands that carry it

Sixty-odd hours, weighted to the big three domains, with a review week at the end. I front-load IAM even though it's only 16%, because every other domain assumes you can read a policy statement.

Week Focus Hands-on task Hours
1 IAM SCP + permission boundary lab in an Org; break it deliberately 8
2 Logging & Monitoring Org trail → S3 with log file validation, then query it in Athena 9
3 Infrastructure Security SG/NACL puzzles, PrivateLink endpoint, WAF rate rule 9
4 Data Protection Cross-account KMS decrypt, S3 Object Lock, Macie sample bucket 10
5 Threat Detection & IR GuardDuty sample findings, EventBridge → Lambda auto-remediation 8
6 Governance Config rules, Security Hub standards, conformance packs 7
7 Review One full practice exam, re-drill the two weakest domains 10

The baseline lab, which covers roughly 40% of the exam surface for near-zero cost (GuardDuty and Security Hub both have 30-day trials; anything past that bills per volume, and rates differ by region):

export AWS_REGION=us-east-1
ACCT=$(aws sts get-caller-identity --query Account --output text)

# 1. Multi-region trail with integrity validation — feeds Logging & Monitoring
aws s3api create-bucket --bucket scs-study-ct-$ACCT
aws cloudtrail create-trail --name scs-study-trail 
  --s3-bucket-name scs-study-ct-$ACCT 
  --is-multi-region-trail --enable-log-file-validation
aws cloudtrail start-logging --name scs-study-trail

# 2. Detectors and findings — feeds Threat Detection
aws guardduty create-detector --enable
aws securityhub enable-security-hub --enable-default-standards

# 3. The single most useful study command: ask IAM why
aws iam simulate-principal-policy 
  --policy-source-arn arn:aws:iam::$ACCT:role/app-decrypt 
  --action-names kms:Decrypt s3:GetObject 
  --resource-arns arn:aws:kms:us-east-1:$ACCT:key/EXAMPLE-KEY-ID


That last one is the closest thing to a cheat code. It returns `EvalDecision` values line by line, so you can see exactly where an explicit `Deny` in an SCP kills an otherwise allowed action. Practising on your own policies makes the policy-evaluation questions on the exam take thirty seconds instead of four minutes.

## The KMS key-policy denial that cost me a Saturday night

We had a cross-account decrypt pipeline — account `111122223333` reading from a CMK in `444455556666`. The key policy granted the caller's role `kms:Decrypt`. It still failed, and the failure started at 22:40 on a Friday when the batch job tripped its alert.

```text
An error occurred (AccessDeniedException) when calling the Decrypt operation:
User: arn:aws:iam::111122223333:role/app-decrypt is not authorized to perform:
kms:Decrypt on resource: arn:aws:kms:us-east-1:444455556666:key/1a2b3c4d-9e8f-7a6b-5c4d-3e2f1a0b9c8d
because no identity-based policy allows the kms:Decrypt action


That last clause is the whole answer, and I read past it twice. The first configuration mistake was treating the key policy as sufficient. For cross-account KMS, the key policy grants the *account*, and the caller still needs an identity-based policy in its own account — the key policy statement listing `arn:aws:iam::111122223333:root` only delegates to IAM there; it grants nobody anything directly.

How I verified it, in order:

```bash
# a) what the key policy actually delegates
aws kms get-key-policy --key-id 1a2b3c4d-9e8f-7a6b-5c4d-3e2f1a0b9c8d 
  --policy-name default --query Policy --output text | jq -r '.Statement[].Principal.AWS'

# b) what CloudTrail thinks happened
aws cloudtrail lookup-events 
  --lookup-attributes AttributeKey=EventName,AttributeValue=Decrypt 
  --start-time 2026-11-14T22:30:00Z 
  --query 'Events[].CloudTrailEvent' --output text | jq -r '.error