A team responds to GuardDuty findings of the type that an EC2 instance is communicating with a known command-and-control host. On such a finding they must automatically isolate the instance by attaching a quarantine security group and capture a forensic snapshot, with the response running consistently for every matching finding and no operator in the loop. The logic involves several conditional AWS API calls that must run on receipt of the finding event. Which design BEST automates this response?
- ACreate an "Amazon EventBridge" rule that matches the GuardDuty finding and invokes an "AWS Lambda" function granted a least-privilege role to attach the quarantine security group and create the forensic snapshot. Correct
- BEnable "AWS Config" with a managed rule and attach automatic remediation so that the instance is moved to a quarantine security group whenever the rule reports it as non-compliant.
- CConfigure a "Systems Manager State Manager" association that periodically checks instances against the GuardDuty console and quarantines any that have an active command-and-control finding.
- DForward the GuardDuty finding to an "Amazon SNS" topic so a security engineer is notified and then attaches the quarantine security group and takes the snapshot manually.
Why A is correct: EventBridge can pattern-match the specific GuardDuty finding and invoke a Lambda function that performs the conditional API calls to isolate the instance and snapshot it, giving consistent automated incident response under a scoped role with no operator needed.
Why B is wrong: Config remediation reacts to resource configuration drift, but a GuardDuty threat finding is not a configuration-compliance state, so a Config rule would not be evaluated by the finding and could not drive this response.
Why C is wrong: State Manager applies a desired configuration on a schedule and cannot consume GuardDuty findings, so the response would lag behind the threat and would not be driven by the finding event the scenario requires.
Why D is wrong: An SNS notification surfaces the threat promptly, which is appealing, but it leaves the containment to a human, so it fails the requirement for an automated, operator-free response on every matching finding.