Managing Windows on AWS

Introduction

In this series of labs, you will get hands-on experience using AWS tools to help you manage your Windows environment. AWS provides a suite of system management tools in AWS System Manager. AWS System Manager can be used to manage your infrastructure in AWS but also can be used to manage your servers on-premises and even in other cloud providers. AWS System Manager contains the following tools:

  • Resource Groups: Used to organize your AWS resources in the same AWS region.

  • Run Command: Lets you remotely and securely manage the configuration of your managed instances.

  • Inventory: Collect metadata from your AWS managed instances.

  • Distributor: Lets you package your own software to install onto AWS managed instances

  • Patch Manager: Automates the process of patching managed instances with both security related and other types of updates.

  • Automation: Simplifies common maintenance and deployment tasks of Amazon EC2 instances and other AWS resources

  • Parameter Store: Provides secure, hierarchical storage for configuration data management and secrets management

  • State Manager: Provides a secure and scalable configuration management service that automates the process of keeping your Amazon EC2 and hybrid infrastructure in a state that you define

  • Maintenance Windows: Lets you define a schedule for when to perform potentially disruptive actions on your instances such as patching an operating system, updating drivers, or installing software or patches.

  • Session Manager: Provides secure and auditable instance management without the need to open inbound ports, maintain bastion hosts, or manage SSH keys through an interactive one-click browser-based shell or through the AWS CLI.

In this lab, you will work through a couple of challenges and along the way learn how to use the System Manager tools to help you resolve these challenges.

Prerequisites

  • Before you can use this lab, the lab environment must be setup. If the lab was setup by the AWS team, then the CloudFormation template should have been run by the lab setup.

  • You can check if the lab was setup by checking the EC2 instances. If the WEB01 and WEB02 are present, then the lab was setup.

  • If the lab wasn’t setup, then you can setup the environment using CloudFormation. Here is the template: CloudFormation-Template.