AWS Systems Manager and EC2 Run Commands

Question 1

What can you do with Systems Manager and EC2 Run Commands

Answer 1

Automate common and ad hoc configuration changes without having to log in to the instances.

Question 2

True or false: Like most AWS services, Systems Manager and EC2 Run Commands require an IAM role?

Answer 2

True.

Question 3

For which AWS Services will you find the correct use case for Systems Manager and Run Commands?

Answer 3

EC2

Question 4

What is the default, AWS-managed role for Systems Manager?

Answer 4

EC2 role for Simple Systems Manager

Question 5

True or False: In Systems Manager, you can choose to run commands against manually selected instances, or against instances with specific tags?

Answer 5

True.

Question 6

True or false: Systems Manager is another example of why proper tagging is critical to managing your AWS environment?

Answer 6

True. Tagging will allow you to easily differentiate which servers require what Run Commands and prevent the requirement of manually selecting instances.

Question 7

In which ways can systems be targeted for Run Commands?

Answer 7

Through manual selection, or applied in groups via instance tagging.

Question 8

True or False: Systems Management is an agentless service, not requiring any software being applied to the instances themselves?

Answer 8

False: An SSM agent needs to be installed on all managed instances.

Question 9

Where are commands and parameters defined?

Answer 9

in a Systems Manager Document

Question 10

From where can commands be issued?

Answer 10

AWS Console, AWS CLI, AWS Tools, PowerShell, Systems Manager API, or Amazon SDKs

Question 11

True or false: AWS Systems Manager is for AWS systems only?

Answer 11

False: You can manage EC2 and on-prem systems with Systems Manager.