AWS Systems Manager Requirements and Building Blocks


Course Introduction
Amazon CloudWatch
AWS Config
What is AWS Config?
AWS Control Tower
AWS Control Tower
PREVIEW19m 56s
AWS Resource Access Manager
AWS Management
AWS Service Catalog
PREVIEW10m 34s
AWS Trusted Advisor Best Practices
AWS Health Dashboard
AWS Data Visualization
Finding Compliance Data with AWS Artifact
Observability in AWS
Start course
6h 2m

This section of the AWS Certified Solutions Architect - Professional learning path introduces the AWS management and governance services relevant to the AWS Certified Solutions Architect - Professional exam. These services are used to help you audit, monitor, and evaluate your AWS infrastructure and resources and form a core component of resilient and performant architectures. 

Want more? Try a Lab Playground or do a Lab Challenge!

Learning Objectives

  • Understand the benefits of using AWS CloudWatch and audit logs to manage your infrastructure
  • Learn how to record and track API requests using AWS CloudTrail
  • Learn what AWS Config is and its components
  • Manage multi-account environments with AWS Organizations and Control Tower
  • Learn how to carry out logging with CloudWatch, CloudTrail, CloudFront, and VPC Flow Logs
  • Learn about AWS data transformation tools such as AWS Glue and data visualization services like Amazon Athena and QuickSight
  • Learn how AWS CloudFormation can be used to represent your infrastructure as code (IaC)
  • Understand SLAs in AWS

AWS Systems Manager, Requirements and Building Blocks. The SSM Agent. AWS Systems Manager requires an agent for its management service. The Systems Manager Agent is the software required to be installed and configured on all instances in order for them to be called managed instances.

A managed instance is an instance with the ability to communicate and be operated by Systems Manager. The agent executes and process tasks you specify through any of the Systems Manager features, like the Run Command. The agent is installed by default on the Amazon Linux AMIs, the AWS Windows AMIs, and available on the Amazon Linux repo. The agent is open-sourced and available on GitHub. You can install the agent on a physical server or a virtual machine in your data center or even another cloud provider. You can manage Windows Server 2003 or later, and Linux distributions like Amazon Linux, Ubuntu, Red Hat Enterprise Linux, SUSE, and CentOS.

Managed Instance Roles. A managed instance will require an Identity and Access Management role applied as an instance profile in order for Systems Manager to be able to interact with the agent and make the instance visible in the Systems Manager Fleet Manager console. AWS provides pre-defined managed policies for Systems Manager. They usually have the acronym SSM as part of their name. One of them is called Amazon EC2 Role for SSM, which can save you time in the instance configuration. You can also create your own custom role if needed or use one of the many other SSM-related policies available. To register servers and virtual machines in your data center or other cloud providers outside the scope of Amazon EC2, you can create a hybrid activation and use the activation code and activation ID supplied to configure the agent and centrally manage your hybrid environment and EC2 instances from one location.

Fleet Manager Feature. Once you configure a managed instance, you can go to the Systems Manager console. And under the Node Management section, you will see the Fleet Manager feature. All your managed instances will be displayed in this console. Fleet Manager will give you visibility into the details of each managed instance, including Instance ID, Platform Type, Instance Type, Operating System name, IP Address, and the version of the SSM Agent that is installed among many other features. One interesting item about the Fleet Manager managed instance console is that under instance action, you can connect to the instance using the Session Manager feature of Systems Manager.

The Session Manager feature of Systems Manager is a fully-managed capability that lets you connect to any managed instance using an interactive browser shell login for Linux, Windows, and MacOS instances. It requires no open inbound ports and no need to manage bastion hosts or Secure Shell keys for connectivity to your instance. You also don't need Secure Shell clients for Linux, or Remote Desktop Protocol clients for Windows when using Session Manager. Communication between Session Manager and instances uses Transport Layer Security version 1.2, or TLS 1.2 for short. Security of the communication can be increased using your own Key Management Service keys. Session Manager tracks all commands and output produced in a session, and also provides full logging and session auditing activity that can be dispatched to CloudTrail, CloudWatch, or an Amazon S3 buckets as a result. Session Manager can control which users can access specific instances by using Identity and Access Management policies. It works through the interactive browser shell or using the AWS Command Line Interface.

About the Author
Learning Paths

Danny has over 20 years of IT experience as a software developer, cloud engineer, and technical trainer. After attending a conference on cloud computing in 2009, he knew he wanted to build his career around what was still a very new, emerging technology at the time — and share this transformational knowledge with others. He has spoken to IT professional audiences at local, regional, and national user groups and conferences. He has delivered in-person classroom and virtual training, interactive webinars, and authored video training courses covering many different technologies, including Amazon Web Services. He currently has six active AWS certifications, including certifications at the Professional and Specialty level.