Examkin

Question

Difficulty: EasyAWS Systems Manager Configuration and Run Command Automation

A SysOps Administrator needs to distribute and execute a custom administrative task across multiple AWS accounts using AWS Systems Manager Run Command. The task requires a custom command document. The administrator has already configured the necessary IAM roles. What is the correct sequence of steps to deploy and run this custom task?

  1. 1Draft the document content in YAML or JSON format, defining the parameters and execution steps.
  2. 2Create the custom SSM Command document in the primary AWS account.
  3. 3Modify the permissions of the custom document to share it with the target AWS accounts.
  4. 4Invoke Systems Manager Run Command in the target accounts, referencing the shared document.

Answer

The correct sequence of steps is: draft the document content in YAML or JSON format, create the custom SSM Command document in the primary AWS account, modify the permissions of the custom document to share it with the target AWS accounts, and invoke Systems Manager Run Command in the target accounts referencing the shared document.
The correct order follows the natural lifecycle of a custom Systems Manager document. First, the administrator must draft the document schema (YAML or JSON). Second, the administrator creates the document in the primary AWS account. Third, the administrator shares the document with the other AWS accounts. Finally, the administrators in the target accounts execute the shared document using Run Command.

Step-by-Step Solution

1
Draft the document content in YAML or JSON format.
A structured configuration template defining parameters and commands is ready.
You must define what the document does before you can create it.
2
Create the custom Systems Manager Command document in the primary AWS account.
The document exists as an active resource within the primary account.
A document must exist locally before it can be shared with other accounts.
3
Modify the permissions of the custom document to share it with target AWS accounts.
The document is now visible and accessible to the target accounts.
Sharing is required before target accounts can access or execute the document.
4
Invoke Systems Manager Run Command in the target accounts referencing the shared document.
The command is executed on target instances in the shared accounts.
Execution can only be initiated once the shared resource is accessible in the target accounts.

Key Concept

Systems Manager Document lifecycle: authoring, creating, sharing, and cross-account execution.
Rate this question

Topics

AWS Systems Manager Configuration and Run Command Automation