A Lot can happen with AWS Systems Manager

Systems manager has lot of use cases that this can be used as a solution.

Configuration steps

Servers with internet access

How to install and check the service status

Step 1: Installation command

#### yum install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_amd64/amazon-ssm-agent.rpm

If there is no internet connectivity manually download rpm and copy to servers

Step 2: installation verification

#### rpm –qa |grep amazon-ssm

Step 3: start the service

#### service amazon-ssm-agent start

Redirecting to /bin/systemctl start amazon-ssm-agent.service

Step 4: status check

#### service amazon-ssm-agent status

Redirecting to /bin/systemctl status amazon-ssm-agent.service

● amazon-ssm-agent.service - amazon-ssm-agent

Loaded: loaded (/etc/systemd/system/amazon-ssm-agent.service; enabled; vendor preset: disabled)

Active: active (running) since Fri 2020-04-17 06:03:12 UTC; 3h 9min ago

Main PID: 32019 (amazon-ssm-agen)

CGroup: /system.slice/amazon-ssm-agent.service

└─32019 /usr/bin/amazon-ssm-agent

Apr 17 08:44:00 aue1l77ecmaasu02 amazon-ssm-agent[32019]: 2020-04-17 08:44:00 INFO [HealthCheck] HealthCheck reporting agent health.

Apr 17 08:48:12 aue1l77ecmaasu02 amazon-ssm-agent[32019]: 2020-04-17 08:48:12 INFO [LongRunningPluginsManager] There are no long running plugins currently ge...lthcheck

Apr 17 08:49:00 aue1l77ecmaasu02 amazon-ssm-agent[32019]: 2020-04-17 08:49:00 INFO [HealthCheck] HealthCheck reporting agent health.

Apr 17 08:53:13 aue1l77ecmaasu02 amazon-ssm-agent[32019]: 2020-04-17 08:53:13 INFO [MessagingDeliveryService] [Association] Schedule manager refreshed with 0...sociated

Apr 17 08:54:00 aue1l77ecmaasu02 amazon-ssm-agent[32019]: 2020-04-17 08:54:00 INFO [HealthCheck] HealthCheck reporting agent health.

Apr 17 08:59:00 aue1l77ecmaasu02 amazon-ssm-agent[32019]: 2020-04-17 08:59:00 INFO [HealthCheck] HealthCheck reporting agent health.

Apr 17 09:03:12 aue1l77ecmaasu02 amazon-ssm-agent[32019]: 2020-04-17 09:03:12 INFO [LongRunningPluginsManager] There are no long running plugins currently ge...lthcheck

Apr 17 09:03:25 aue1l77ecmaasu02 amazon-ssm-agent[32019]: 2020-04-17 09:03:25 INFO [MessagingDeliveryService] [Association] Schedule manager refreshed with 0...sociated

Apr 17 09:04:00 aue1l77ecmaasu02 amazon-ssm-agent[32019]: 2020-04-17 09:04:00 INFO [HealthCheck] HealthCheck reporting agent health.

Apr 17 09:09:00 aue1l77ecmaasu02 amazon-ssm-agent[32019]: 2020-04-17 09:09:00 INFO [HealthCheck] HealthCheck reporting agent health.

Hint: Some lines were ellipsized, use -l to show in full.

Step 5: SSM Logs verification at OS

#### cat /var/log/amazon/ssm/amazon-ssm-agent.log

Sample output:

2020-04-17 08:43:30 INFO [MessagingDeliveryService] [Association] Schedule manager refreshed with 0 associations, 0 new associations associated

2020-04-17 08:44:00 INFO [HealthCheck] HealthCheck reporting agent health.

2020-04-17 08:48:12 INFO [LongRunningPluginsManager] There are no long running plugins currently getting executed - skipping their healthcheck

2020-04-17 08:49:00 INFO [HealthCheck] HealthCheck reporting agent health.

2020-04-17 08:53:13 INFO [MessagingDeliveryService] [Association] Schedule manager refreshed with 0 associations, 0 new associations associated

2020-04-17 08:54:00 INFO [HealthCheck] HealthCheck reporting agent health.

2020-04-17 08:59:00 INFO [HealthCheck] HealthCheck reporting agent health.

2020-04-17 09:03:12 INFO [LongRunningPluginsManager] There are no long running plugins currently getting executed - skipping their healthcheck

2020-04-17 09:03:25 INFO [MessagingDeliveryService] [Association] Schedule manager refreshed with 0 associations, 0 new associations associated

2020-04-17 09:04:00 INFO [HealthCheck] HealthCheck reporting agent health.

2020-04-17 09:09:00 INFO [HealthCheck] HealthCheck reporting agent health.

2020-04-17 09:13:23 INFO [MessagingDeliveryService] [Association] Schedule manager refreshed with 0 associations, 0 new associations associated

2020-04-17 09:14:00 INFO [HealthCheck] HealthCheck reporting agent health.

Things to be done at AWS management console

Step 1: Requires a valid AWS management console access to access EC2, Systems Manager

Step 2: Prerequisite for server to list in systems manager

· Ec2 Instance should be attached with SSM Role (SSM to access EC2 service)

Step 3: Navigate to systems manager console – Managed Instances

Search with instance ID

Instance will be listed and will be able to manage this for all SSM supported features now.