SOA-C03 - Deployment, Provisioning, and Automation (22% of the exam) - Section 3.6
Automate operational processes using AWS Systems Manager Run Command, Patch Manager, State Manager, Parameter Store and Session Manager.
Automate fleet operations using AWS Systems Manager Run Command for ad-hoc execution, Patch Manager for OS patching, State Manager for configuration drift remediation, and Parameter Store for centralised secrets and configuration values. Recognise which Systems Manager capability to apply for each operational scenario without requiring SSH access to instances.
Systems Manager Run CommandPatch ManagerState ManagerParameter Store
Practice question for this objective
lock_openFree sampleDeployment, Provisioning, and Automationmedium
Auditors require that administrators can no longer connect to private EC2 instances over SSH on port 22, yet engineers still need an interactive shell for troubleshooting, with every session command logged to CloudWatch Logs for review. The instances run the SSM agent and have no public IP. Which approach meets the access and logging requirement with the least network exposure?
AOpen SSH only from a bastion host in a public subnet and forward the bastion authentication logs to CloudWatch Logs so administrators retain an audited shell path.
BUse Run Command to send individual troubleshooting commands to the instances and store the output in CloudWatch Logs so administrators avoid opening an SSH connection.
CUse Session Manager to provide the interactive shell through the SSM agent and enable session logging to CloudWatch Logs, keeping inbound SSH closed.check_circle Correct
DAttach an internet gateway and a security group that allows SSH from the corporate IP range, then send the instance SSH logs to CloudWatch Logs for the auditors.
Use Systems Manager Session Manager with session logging to give audited interactive shell access without opening inbound SSH. Session Manager establishes an interactive shell to an instance through the SSM agent and the Systems Manager endpoint, so it needs no open inbound port, no bastion and no public IP. Enabling session logging streams the commands and output of each session to CloudWatch Logs or S3, which gives auditors the full record they need while removing the SSH attack surface entirely.
Why A is wrong: A bastion still relies on port 22 and an internet-facing host, which the auditors are removing, and bastion logs capture connection events rather than the commands typed inside each interactive session.
Why B is wrong: Run Command executes discrete documents and returns their output but gives no live interactive shell, so engineers cannot troubleshoot iteratively the way an open session allows.
Why C is correct: Session Manager opens a shell over the agent and the Systems Manager service with no inbound port, and its logging feature streams session command output to CloudWatch Logs, meeting both the no-SSH and full-audit requirements.
Why D is wrong: This keeps SSH on port 22 open and adds internet reachability to private instances, directly contradicting the requirement to remove SSH access and minimise network exposure.
Exam traps in Deployment, Provisioning, and Automation
Answers that look right on this material and are not. Each one is a distractor from a different question in the SOA-C03 bank for this domain.
Use State Manager to associate a patch document with the fleet on a weekly schedule so security updates are applied and a compliance report is produced for each instance.
errorWhy it is wrong: State Manager applies documents to keep configuration in a desired state but has no concept of a patch baseline, auto-approval delay or patch compliance reporting, so it cannot express this patching policy.
Issue a Run Command against the Monitored tag whenever the Auto Scaling group reports that it has launched a new instance, installing the agent on that specific host each time.
errorWhy it is wrong: Run Command is a one-time push and would need to be triggered on every launch and every drift event, so it does not continuously hold new and existing instances in the desired state on its own.
Use Run Command to push the agent configuration document to the fleet whenever the compliance team notices that an instance has drifted from the required state.
errorWhy it is wrong: Run Command applies a document once when an operator invokes it, so it relies on someone spotting drift and triggering a run, which fails the requirement for automatic recurring enforcement.