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

www.awsgood.com

SCS-C03 Exam Domain Deep Dive: Security Logging and Monitoring (61 chars ✓)

2026-11-17 SCS-C03 Security - Specialty 约 6 分钟

TL;DR

Then the failure story.

The trail that said "Logging" and shipped nothing

Story.

Then a code block.

Then "Who should sit it" with exam facts table.

Then domains table.

Then Domain 2 deep dive with the second table and Logs Insights query.

Then study plan + technique.

Then Sources.

Let me make sure paragraphs are ≤4 sentences and vary.

Write now.

For the exam facts table:

Detail Value
Questions 65 (multiple choice / multiple response)
Time 170 minutes
Passing score 750 on a 100–1000 scaled score
Fee $300 USD in the US; varies by country
Validity 3 years
Delivery Pearson VUE test center or online proctored
Prerequisites none official; AWS recommends 3–5 years of security/ops experience

Also: "Response: 2 hours 50 minutes".

Now the second table for Domain 2 task areas. Third table? Only one table required; two is fine.

Let me count words as I go, roughly targeting 1600.

Careful with banned words: "leverage", "robust", "seamless", "unlock the power", "in today's world", "it is worth noting", "in conclusion", "this article will walk you through".

Also avoid triadic openers and "Overall".

Write.

For the "When not to sit SCS-C03 yet" — H3 under who-should-sit.

Source links:

Use 3-4 links.

Now write the whole thing.

One more: "Include at least one 'hard-won lesson'" ✓ (the trail story).

Also mention awsgood.com managed services once near the end — e.g., "If you'd rather not hand-roll the org trail, bucket policy, and KMS grant yourself, that's part of what we do at awsgood.com." Keep non-salesy. Place near the end, before Sources or in study plan section. I'll put it in the study plan section or after the deep dive.

Let's write.

Word count check will come naturally.

Draft content:


TL;DR

The trail that said "Logging" and shipped nothing

At 02:40 on 2026-02-11 an alert that should have fired on a root-account console login never arrived. Not a broken alarm — a silent pipeline. Our org trail in us-east-1 showed Status: Logging in the console, S3 delivery was healthy, but the CloudWatch Logs group had zero events for the last 36 hours, so the EventBridge rule that matches ConsoleLogin had nothing to match.

First thing I ran:

aws cloudtrail get-trail-status --name acme-org-trail 
  --query '{s3Err:LatestDeliveryError,cwlErr:LatestCloudWatchLogsDeliveryError,cwlTime:LatestCloudWatchLogsDeliveryTime}'


Output:

```json
{
  "s3Err": null,
  "cwlErr": "Insufficient permissions to write to CloudWatch Logs",
  "cwlTime": "2026-02-09T14:12:07Z"
}


The `s3Err` being null is what makes this nasty — the trail is fine by S3 standards, and a status page that only checks `LatestDeliveryError` says everything is green.

Root cause took another 20 minutes: the CloudTrail role's inline policy granted `logs:PutLogEvents` on `arn:aws:logs:us-east-1:111122223333:log-group:/aws/cloudtrail/acme-org-trail`, with no `:log-stream:*` suffix. PutLogEvents authorizes against the log stream ARN, not the group. Everything else — the assume-role trust policy, the KMS grant, the S3 bucket policy — was correct.

Fix + verify:

```bash
# 1. scope the policy to the stream ARN
aws iam put-role-policy --role-name CloudTrailToCWL 
  --policy-name PutEvents 
  --policy-document '{"Version":"2012-10-17","Statement":[{"Effect":"Allow","Action":["logs:CreateLogStream","logs:PutLogEvents"],"Resource":"arn:aws:logs:us-east-1:111122223333:log-group:/aws/cloudtrail/acme-org-trail:log-stream:*"}]}'

# 2. watch delivery catch up (usually within 5 minutes)
watch -n 30 'aws cloudtrail get-trail-status --name acme-org-trail 
  --query "LatestCloudWatchLogsDeliveryTime" --output text'


The timestamp started advancing within four minutes, and the log stream `111122223333_CloudTrail_us-east-1` filled in. Lesson: monitor the delivery timestamp, not the trail status. If `LatestCloudWatchLogsDeliveryTime` is more than 15 minutes stale on a busy org trail, you have an incident.

That's the shape of most Domain 2 questions...

Hmm, "watch" command with quotes could be messy but fine.

## Who should sit SCS-C03, and when to wait

Prose + table.

## Domain weights...

Table.

## Inside Domain 2...

Prose + table + Logs Insights query.

## Study plan and exam technique

## Sources

Good. Now write fully with word count in mind.

I'll write it out.

For the "Who should sit" section, include the exam facts table. Prose around it. Include an H3 "When not to sit SCS-C03 yet".

Also mention which exam first: SAA-C03 before SCS-C03.

Now for Domain 2 deep dive, mention:
- Centralized logging: org trail with `--is-organization-trail`, S3 bucket policy with `aws:SourceArn`, KMS CMK needs `kms:GenerateDataKey*` in bucket policy for CloudTrail and `logs.region.amazonaws.com` for Logs.
- Log integrity validation + digest files + `aws cloudtrail validate-logs`.
- Protection: Object Lock, MFA delete.
- VPC Flow Logs to S3/Logs/Firehose; aggregation interval 1 min vs default 10 min; rejected traffic only filter.
- GuardDuty delegated admin via `aws guardduty enable-organization-admin-account`; 90-day retention; export findings to S3.
- Security Hub + EventBridge for alerting; note ASFF.
- Security Lake OCSF.
- CloudWatch Logs retention default never expires; set 30/90 days + export to S3.
- Query: Logs Insights vs Athena.

Command for enabling org trail with CloudWatch Logs:
```bash
aws cloudtrail create-trail --name acme-org-trail 
  --s3-bucket-name acme-org-cloudtrail-archive 
  --is-organization-trail 
  --kms-key-id arn:aws:kms:us-east-1:111122223333:key/...
  --cloud-watch-logs-log-group-arn arn:aws:logs:us-east-1:111122223333:log-group:/aws/cloudtrail/acme-org-trail:*
  --cloud-watch-logs-role-arn arn:aws:iam::111122223333:role/CloudTrailToCWL

Good — and note the log group ARN ends with `:*` (not a log-stream ARN? Actually the CLI expects the log group ARN with `:*`? The docs example uses `arn:aws:logs:us-east-1:123456789012:log-group:my-log-group:*`? Hmm. Common usage: `--cloud-watch-logs-log-group-arn arn:aws:logs:us-east-1:123456789012:log-group:CloudTrail:*`. I've seen that. Fine, I'll use `:*`.

Logs Insights query for CloudTrail:


fields @timestamp, eventSource, eventName, errorCode, sourceIPAddress, userIdentity.arn
| filter eventName in ["ConsoleLogin","AssumeRole","CreateAccessKey"]
| stats count() as hits by eventName, sourceIPAddress
| sort hits desc
| limit 25


Study plan: weeks.

Alright, writing final. Keep total under