Centralized EC2 Management Across Multiple AWS Accounts Using AWS Systems Manager
A company wants to centralize management of Amazon EC2 instances across multiple AWS accounts. They need to be able to run commands on instances in any account from a central management account. Which service should be used?
Quick Answer
AWS Systems Manager is the correct choice for centralized EC2 management across multiple AWS accounts because it provides a unified control plane via the Systems Manager Agent, enabling you to run commands, manage patches, and automate operations on instances in any account without requiring SSH or bastion hosts. This works by configuring cross-account IAM roles and sharing Systems Manager resources through AWS Resource Access Manager, allowing a central management account to securely target instances across the organization. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of operational governance at scale, often appearing as a distractor against solutions like AWS Config or AWS OpsWorks; a common trap is assuming you need a VPN or VPC peering for command execution, but Systems Manager operates over the AWS control plane. Remember the mnemonic “SSM = Single Source of Management” to recall that it centralizes EC2 administration without network-level dependencies.
⚠ Common exam trap
Many candidates confuse AWS Config's compliance and auditing capabilities with Systems Manager's operational command execution, or mistakenly think OpsWorks (which also uses agents) is suitable for cross-account command execution, but OpsWorks lacks native cross-account centralized command features and is more focused on application lifecycle management.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
AWS Systems Manager
AWS Systems Manager (SSM) is the correct choice because it provides a unified interface to manage EC2 instances across multiple AWS accounts via the Systems Manager Agent (SSM Agent). With SSM, you can use Run Command, Session Manager, or State Manager to execute commands on instances in any account, as long as the instances are registered in AWS Systems Manager and the appropriate cross-account IAM roles and resource access manager (RAM) sharing are configured. This centralizes management without requiring SSH or bastion hosts.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
AWS Systems Manager
Why this is correct
Systems Manager Run Command and Session Manager can target instances across accounts.
- ✗
AWS Config
Why it's wrong here
Config is for resource inventory and compliance.
- ✗
Amazon ECS
Why it's wrong here
ECS is for container orchestration.
- ✗
AWS OpsWorks
Why it's wrong here
OpsWorks is for configuration management, not command execution across accounts.
Go deeper
Related to this question
About these practice questions
This SAP-C02 question is part of Courseiva's 1,660-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on SAP-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company wants to centralize management of Amazon EC2 instances across multiple accounts using AWS Systems Manager. The company uses AWS Organizations. What is the simplest way to enable Systems Manager to manage instances in all accounts?
easy- A.Use AWS Config to aggregate configuration data
- B.Use Systems Manager Automation runbooks in each account
- ✓ C.Use Systems Manager Explorer with multi-account management
- D.Use CloudFormation StackSets to deploy Systems Manager agents
Why C: Systems Manager Explorer provides a built-in, multi-account view that aggregates operational data (e.g., patch compliance, inventory) from all member accounts in AWS Organizations without requiring custom scripts or manual setup. It leverages AWS Organizations to automatically discover and manage instances across accounts, making it the simplest centralized management solution.
Variation 2. A company wants to use AWS Systems Manager to automate patching of EC2 instances across multiple AWS accounts. What is the most efficient way to manage this centrally?
easy- A.Use AWS Systems Manager Patch Manager in the management account.
- ✓ B.Use AWS Systems Manager Quick Setup to configure patching across accounts.
- C.Use AWS Systems Manager Automation documents in each account.
- D.Use AWS Config rules to trigger patching in each account.
Why B: AWS Systems Manager Quick Setup is the most efficient way to centrally configure patching across multiple AWS accounts because it automates the deployment of SSM Patch Manager resources, including patch baselines, maintenance windows, and IAM roles, across accounts in an AWS Organization. It eliminates the need to manually set up patching in each account, providing a single-pane-of-glass management experience from the management account.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.