• The AWS Systems Manager CloudWatch Dashboard will no longer be available after April 30, 2026. Customers can continue to use Amazon CloudWatch console to view, create, and manage their Amazon CloudWatch dashboards, just as they do today. For more information, see [Amazon CloudWatch Dashboard documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Dashboards.html).
# Manually installing and uninstalling SSM Agent on EC2 instances for Linux
Before you manually install AWS Systems Manager Agent (SSM Agent) on an Amazon Elastic Compute Cloud (Amazon EC2) Linux operating system, review the following information.
**Installation on other machine types**
The procedures in this section are designed specifically for Amazon EC2 instances. For on-premises servers, virtual machines, or other non-EC2 environments, use the `ssm-setup-cli` tool as described in [How to install the SSM Agent on hybrid Linux nodes](hybrid-multicloud-ssm-agent-install-linux.md).
Using EC2 installation procedures on non-EC2 systems can potentially result in security vulnerabilities. The `ssm-setup-cli` tool provides additional security protections for non-EC2 machines.
We strongly recommend that you avoid using OS versions that have reached End-of-Life (EOL). OS vendors including AWS typically don't provide security patches or other updates for versions that have reached EOL. Continuing to use an EOL system greatly increases the risk of not being able to apply upgrades, including security fixes, and other operational problems. AWS does not test Systems Manager functionality on OS versions that have reached EOL.
**SSM Agent installation file URLs**
You can access the installation files for SSM Agent that are stored in any commercial AWS Region. We also provide installation files in a globally available Amazon Simple Storage Service (Amazon S3) bucket that you can use as an alternative or backup source of files.
If you're manually installing the agent on a instance or two, you can use the commands in the **Quick installation** procedures we provide to save time. The commands provided in these procedures can also be passed to Amazon EC2 instances as scripts through user data.
If you're creating a script or template to use for installing the agent on multiple instances, we recommend that you use the installation files in or near an AWS Region where you're geographically located. For bulk installations, this can increase the speed of your downloads and reduce latency. In these cases, we recommend using the **Create custom installation commands** procedures in the installation topics.
**Amazon Machine Images with the agent preinstalled**
SSM Agent is preinstalled on some Amazon Machine Images (AMIs) provided by AWS. For information, see [Find AMIs with the SSM Agent preinstalled](ami-preinstalled-agent.md).
**Keeping the agent up to date**
An updated version of SSM Agent is released whenever new tools are added to Systems Manager or updates are made to existing tools. Failing to use the latest version of the agent can prevent your managed node from using various Systems Manager tools and features. For that reason, we recommend that you automate the process of keeping SSM Agent up to date on your machines. For information, see [Automating updates to SSM Agent](ssm-agent-automatic-updates.md). Subscribe to the [SSM Agent Release Notes](https://github.com/aws/amazon-ssm-agent/blob/mainline/RELEASENOTES.md) page on GitHub to get notifications about SSM Agent updates.
**Choose your operating system**
To view the procedure for manually installing SSM Agent on the specified operating system, choose a link from the following list:
**Note**
For a list of supported versions of each of the following operating systems, see [Supported operating systems for Systems Manager](operating-systems-and-machine-types.md#prereqs-operating-systems).
+ [AlmaLinux](agent-install-alma.md)
+ [Amazon Linux 2 and Amazon Linux 2023](agent-install-al2.md)
+ [Debian Server](agent-install-deb.md)
+ [Oracle Linux](agent-install-oracle.md)
+ [Red Hat Enterprise Linux](agent-install-rhel.md)
+ [Rocky Linux](agent-install-rocky.md)
+ [Ubuntu Server](agent-install-ubuntu.md)
## Uninstalling SSM Agent from Linux instances
Use the package manager for your operating system to uninstall SSM Agent from Linux instances. Depending on the operating system, the uninstall command will be similar to the following example command:
```
sudo dpkg -r amazon-ssm-agent
```
# Manually install SSM Agent on AlmaLinux instances
Use the information in this section to help you manually install or reinstall SSM Agent on an AlmaLinux instance.
**Before you begin**
Before you install SSM Agent on an AlmaLinux instance, note the following:
+ Ensure that Python 3 is installed on your AlmaLinux instance. This is required in order for SSM Agent to work properly.
+ For important information that applies to installation of SSM Agent on all Linux-based operating systems, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](manually-install-ssm-agent-linux.md).
**Topics**
+ [
## Quick installation commands for SSM Agent on AlmaLinux
](#quick-install-alma)
+ [
## Create custom agent installation commands for AlmaLinux in your Region
](#custom-url-alma)
## Quick installation commands for SSM Agent on AlmaLinux
Use the following steps to manually install SSM Agent on a single instance. This procedure uses globally available installation files.
**Before you begin**
Before you install SSM Agent on a AlmaLinux instance, note the following:
+ Ensure that Python 3 is installed on your AlmaLinux instance. This is required in order for SSM Agent to work properly.
**To install SSM Agent on AlmaLinux**
1. Connect to your AlmaLinux instance using your preferred method, such as SSH.
1. Copy the command for your instance’s architecture and run it on the instance.
**Note**
Even though URLs in the following commands include an `ec2-downloads-windows` directory, these are the correct global installation files for AlmaLinux.
x86\$164 instances
```
sudo dnf install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_amd64/amazon-ssm-agent.rpm
```
ARM64 instances
```
sudo dnf install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_arm64/amazon-ssm-agent.rpm
```
1. (Recommended) Run the following command to verify that the agent is running.
```
sudo systemctl status amazon-ssm-agent
```
In most cases, the command reports that the agent is running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/etc/systemd/system/amazon-ssm-agent.service; enabled; vendo>
Active: active (running) since Tue 2025-04-19 16:40:41 UTC; 9s ago
Main PID: 4898 (amazon-ssm-agen)
Tasks: 14 (limit: 4821)
Memory: 34.6M
CGroup: /system.slice/amazon-ssm-agent.service
├─4898 /usr/bin/amazon-ssm-agent
└─4954 /usr/bin/ssm-agent-worker
--truncated--
```
In rare cases, the command reports that the agent is installed but not running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/etc/systemd/system/amazon-ssm-agent.service; enabled; vendo>
Active: inactive (dead) since Tue 2025-04-19 16:42:05 UTC; 2s ago
--truncated--
```
To activate the agent in these cases, run the following commands.
```
sudo systemctl enable amazon-ssm-agent
```
```
sudo systemctl start amazon-ssm-agent
```
## Create custom agent installation commands for AlmaLinux in your Region
When you install SSM Agent on multiple instances using a script or template, we recommend using installation files that are stored in the AWS Region you're working in.
For the following commands, we provide examples that use a publicly accessible S3 bucket in the US East (Ohio) Region (`us-east-2`).
**Tip**
You can also replace a global URL in the procedure [Quick installation commands for SSM Agent on AlmaLinux](#quick-install-alma) earlier in this topic with a custom Regional URL you construct.
In the following command, replace *region* with your own information. For a list of supported *region* values, see the **Region** column in [Systems Manager service endpoints](https://docs.aws.amazon.com/general/latest/gr/ssm.html#ssm_region) in the *Amazon Web Services General Reference*.
**x86\$164**
```
sudo dnf install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_amd64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo dnf install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_amd64/amazon-ssm-agent.rpm
```
**ARM64**
```
sudo dnf install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_arm64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo dnf install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_arm64/amazon-ssm-agent.rpm
```
# Manually installing SSM Agent on Amazon Linux 2 and Amazon Linux 2023 instances
In most cases, the Amazon Machine Images (AMIs) for Amazon Linux 2 and Amazon Linux 2023 that are provided by AWS come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. For more information, see [Find AMIs with the SSM Agent preinstalled](ami-preinstalled-agent.md).
In the event that SSM Agent isn’t preinstalled on a new Amazon Linux 2 or Amazon Linux 2023 instance, or if you need to manually reinstall the agent, use the information on this page to help you.
**Before you begin**
Before you install SSM Agent on an Amazon Linux 2 or Amazon Linux 2023 instance, note the following:
+ For important information that applies to installation of SSM Agent on all Linux-based operating systems, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](manually-install-ssm-agent-linux.md).
+ If you use a `yum` command to update SSM Agent on a managed node after the agent has been installed or updated using the SSM document `AWS-UpdateSSMAgent`, you might see the following message: `"Warning: RPMDB altered outside of yum."` This message is expected and can be safely ignored.
**Topics**
+ [
## Quick installation commands for SSM Agent on Amazon Linux 2 or Amazon Linux 2023
](#quick-install-al2)
+ [
## Create custom agent installation commands for Amazon Linux 2 or Amazon Linux 2023 in your Region
](#custom-url-al2)
## Quick installation commands for SSM Agent on Amazon Linux 2 or Amazon Linux 2023
Use the following steps to manually install SSM Agent on a single instance. This procedure uses globally available installation files.
**To install SSM Agent on Amazon Linux 2 or Amazon Linux 2023 using quick copy and paste commands**
1. Connect to your Amazon Linux 2 or Amazon Linux 2023 instance using your preferred method, such as SSH.
1. Copy the command for your instance’s architecture and run it on the instance.
**Note**
Even though URLs in the following commands include an `ec2-downloads-windows` directory, these are the correct global installation files for Amazon Linux 2 and Amazon Linux 2023.
**x86\$164**
```
sudo yum install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_amd64/amazon-ssm-agent.rpm
```
**ARM64**
```
sudo yum install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_arm64/amazon-ssm-agent.rpm
```
1. (Recommended) Run the following command to verify that the agent is running.
```
sudo systemctl status amazon-ssm-agent
```
In most cases, the command reports that the agent is running, as shown in the following example.
```
amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/usr/lib/systemd/system/amazon-ssm-agent.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-10-20 19:09:29 UTC; 4min 6s ago
--truncated--
```
In rare cases, the command reports that the agent is installed but not running, as shown in the following example.
```
amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/usr/lib/systemd/system/amazon-ssm-agent.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Wed 2021-10-20 22:16:41 UTC; 18s ago
--truncated--
```
To activate the agent in these cases, run the following command.
```
sudo systemctl start amazon-ssm-agent
```
## Create custom agent installation commands for Amazon Linux 2 or Amazon Linux 2023 in your Region
When you install SSM Agent on multiple instances using a script or template, we recommend using installation files that are stored in the AWS Region you're working in.
For the following commands, we provide examples that use a publicly accessible S3 bucket in the US East (Ohio) Region (`us-east-2`).
**Tip**
You can also replace a global URL in the procedure [Quick installation commands for SSM Agent on Amazon Linux 2 or Amazon Linux 2023](#quick-install-al2) earlier in this topic with a custom Regional URL you construct.
In the following command, replace *region* with your own information. For a list of supported *region* values, see the **Region** column in [Systems Manager service endpoints](https://docs.aws.amazon.com/general/latest/gr/ssm.html#ssm_region) in the *Amazon Web Services General Reference*.
**x86\$164**
```
sudo yum install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_amd64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo yum install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_amd64/amazon-ssm-agent.rpm
```
**ARM64**
```
sudo yum install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_arm64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo yum install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_arm64/amazon-ssm-agent.rpm
```
# Manually install SSM Agent on CentOS Stream instances
The Amazon Machine Images (AMIs) for CentOS Stream that are provided by AWS do not come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. For a list of AWS managed AMIs on which the agent might be preinstalled, see [Find AMIs with the SSM Agent preinstalled](ami-preinstalled-agent.md).
Use the information in this section to help you manually install or reinstall SSM Agent on a CentOS Stream instance.
**Before you begin**
Before you install SSM Agent on a CentOS Stream instance, note the following:
+ For important information that applies to installation of SSM Agent on all Linux-based operating systems, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](manually-install-ssm-agent-linux.md).
**Topics**
+ [
## Quick installation commands for SSM Agent on CentOS Stream
](#quick-install-centos-stream)
+ [
## Create custom agent installation commands for CentOS Stream in your Region
](#custom-url-centos-stream)
## Quick installation commands for SSM Agent on CentOS Stream
Use the following steps to manually install SSM Agent on a single instance. This procedure uses globally available installation files.
**To install SSM Agent on CentOS Stream**
1. Connect to your CentOS Stream instance using your preferred method, such as SSH.
1. Copy the command for your instance’s architecture and run it on the instance.
**Note**
Even though URLs in the following commands include an `ec2-downloads-windows` directory, these are the correct global installation files for CentOS Stream.
x86\$164 instances
```
sudo dnf install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_amd64/amazon-ssm-agent.rpm
```
ARM64 instances
```
sudo dnf install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_arm64/amazon-ssm-agent.rpm
```
1. (Recommended) Run the following command to verify that the agent is running.
```
sudo systemctl status amazon-ssm-agent
```
In most cases, the command reports that the agent is running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/etc/systemd/system/amazon-ssm-agent.service; enabled; vendo>
Active: active (running) since Tue 2025-04-19 16:40:41 UTC; 9s ago
Main PID: 4898 (amazon-ssm-agen)
Tasks: 14 (limit: 4821)
Memory: 34.6M
CGroup: /system.slice/amazon-ssm-agent.service
├─4898 /usr/bin/amazon-ssm-agent
└─4954 /usr/bin/ssm-agent-worker
‐‐truncated‐‐
```
In rare cases, the command reports that the agent is installed but not running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/etc/systemd/system/amazon-ssm-agent.service; enabled; vendo>
Active: inactive (dead) since Tue 2025-04-19 16:42:05 UTC; 2s ago
‐‐truncated
```
To activate the agent in these cases, run the following commands.
```
sudo systemctl enable amazon-ssm-agent
```
```
sudo systemctl start amazon-ssm-agent
```
## Create custom agent installation commands for CentOS Stream in your Region
When you install SSM Agent on multiple instances using a script or template, we recommend using installation files that are stored in the AWS Region you're working in.
For the following commands, we provide examples that use a publicly accessible S3 bucket in the US East (Ohio) Region (`us-east-2`).
**Tip**
You can also replace a global URL in the procedure [Quick installation commands for SSM Agent on CentOS Stream](#quick-install-centos-stream) earlier in this topic with a custom Regional URL you construct.
In the following command, replace *region* with your own information. For a list of supported *region* values, see the **Region** column in [Systems Manager service endpoints](https://docs.aws.amazon.com/general/latest/gr/ssm.html#ssm_region) in the *Amazon Web Services General Reference*.
**x86\$164**
```
sudo dnf install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_amd64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo dnf install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_amd64/amazon-ssm-agent.rpm
```
**ARM64**
```
sudo dnf install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_arm64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo dnf install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_arm64/amazon-ssm-agent.rpm
```
# Manually installing SSM Agent on Debian Server instances
The Amazon Machine Images (AMIs) for Debian Server that are provided by AWS do not come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. For a list of AWS managed AMIs on which the agent might be preinstalled, see [Find AMIs with the SSM Agent preinstalled](ami-preinstalled-agent.md).
Use the information in this section to help you manually install or reinstall SSM Agent on a Debian Server instance.
**Before you begin**
Before you install SSM Agent on a Debian Server instance, note the following:
+ For important information that applies to installation of SSM Agent on all Linux-based operating systems, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](manually-install-ssm-agent-linux.md).
**Topics**
+ [
## Quick installation commands for SSM Agent on Debian Server
](#quick-install-debian)
+ [
## Create custom agent installation commands for Debian Server in your Region
](#custom-url-debian)
## Quick installation commands for SSM Agent on Debian Server
Use the following steps to manually install SSM Agent on a single instance. This procedure uses globally available installation files.
**To install SSM Agent on Debian Server**
1. Connect to your Debian Server instance using your preferred method, such as SSH.
1. Run the following command to create a temporary directory on the instance.
```
mkdir /tmp/ssm
```
1. Run the following command to change to the temporary directory.
```
cd /tmp/ssm
```
1. Copy the command for your instance’s architecture and run it on the instance.
**Note**
Even though URLs in the following commands include an `ec2-downloads-windows` directory, these are the correct global installation files for Debian Server.
For Debian Server 8, only the x86\$164 architecture is supported.
x86\$164 instances
```
wget https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/debian_amd64/amazon-ssm-agent.deb
```
ARM64 instances
```
wget https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/debian_arm64/amazon-ssm-agent.deb
```
1. Run the following command.
```
sudo dpkg -i amazon-ssm-agent.deb
```
1. (Recommended) Run the following command to verify that the agent is running.
```
sudo systemctl status amazon-ssm-agent
```
In most cases, the command reports that the agent is running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/lib/systemd/system/amazon-ssm-agent.service; enabled; vendor
Active: active (running) since Tue 2025-04-19 16:25:03 UTC; 4s ago
Main PID: 628 (amazon-ssm-agen)
CGroup: /system.slice/amazon-ssm-agent.service
├─628 /usr/bin/amazon-ssm-agent
└─650 /usr/bin/ssm-agent-worker
--truncated--
```
In rare cases, the command reports that the agent is installed but not running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/lib/systemd/system/amazon-ssm-agent.service; enabled; vendor
Active: inactive (dead) since Tue 2025-04-19 16:26:30 UTC; 5s ago
Main PID: 628 (code=exited, status=0/SUCCESS)
--truncated--
```
To activate the agent in these cases, run the following commands.
```
sudo systemctl enable amazon-ssm-agent
```
```
sudo systemctl start amazon-ssm-agent
```
## Create custom agent installation commands for Debian Server in your Region
When you install SSM Agent on multiple instances using a script or template, we recommend using installation files that are stored in the AWS Region you're working in.
For the following commands, we provide examples that use a publicly accessible S3 bucket in the US East (Ohio) Region (`us-east-2`).
**Tip**
You can also replace a global URL in the procedure [Quick installation commands for SSM Agent on Debian Server](#quick-install-debian) earlier in this topic with a custom Regional URL you construct.
In the following command, replace *region* with your own information. For a list of supported *region* values, see the **Region** column in [Systems Manager service endpoints](https://docs.aws.amazon.com/general/latest/gr/ssm.html#ssm_region) in the *Amazon Web Services General Reference*.
x86\$164
```
wget https://s3.region.amazonaws.com/amazon-ssm-region/latest/debian_amd64/amazon-ssm-agent.deb
```
```
sudo dpkg -i amazon-ssm-agent.deb
```
See the following example.
```
wget https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/debian_amd64/amazon-ssm-agent.deb
```
```
sudo dpkg -i amazon-ssm-agent.deb
```
ARM64
```
wget https://s3.region.amazonaws.com/amazon-ssm-region/latest/debian_arm64/amazon-ssm-agent.deb
```
```
sudo dpkg -i amazon-ssm-agent.deb
```
See the following example.
```
wget https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/debian_arm64/amazon-ssm-agent.deb
```
```
sudo dpkg -i amazon-ssm-agent.deb
```
# Manually installing SSM Agent on Oracle Linux instances
The Amazon Machine Images (AMIs) for Oracle Linux that are provided by AWS do not come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. For a list of AWS managed AMIs on which the agent might be preinstalled, see [Find AMIs with the SSM Agent preinstalled](ami-preinstalled-agent.md).
Use the information in this section to help you manually install or reinstall SSM Agent on an Oracle Linux instance.
**Before you begin**
Before you install SSM Agent on an Oracle Linux instance, note the following:
+ For important information that applies to installation of SSM Agent on all Linux-based operating systems, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](manually-install-ssm-agent-linux.md).
+ If you use a `yum` command to update SSM Agent on a managed node after the agent has been installed or updated using the SSM document `AWS-UpdateSSMAgent`, you might see the following message: `"Warning: RPMDB altered outside of yum."` This message is expected and can be safely ignored.
**Topics**
+ [
## Quick installation commands for SSM Agent on Oracle Linux
](#quick-install-oracle)
+ [
## Create custom agent installation commands for Oracle Linux in your Region
](#custom-url-oracle)
## Quick installation commands for SSM Agent on Oracle Linux
Use the following steps to manually install SSM Agent on a single instance. This procedure uses globally available installation files.
**To install SSM Agent on Oracle Linux using quick copy and paste commands**
1. Connect to your Oracle Linux instance using your preferred method, such as SSH.
1. Copy the following command and run it on the instance.
**Note**
Even though URL in the following command includes an `ec2-downloads-windows` directory, these are the correct global installation files for Oracle Linux.
**x86\$164**
```
sudo yum install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_amd64/amazon-ssm-agent.rpm
```
1. (Recommended) Run the following command to verify that the agent is running.
```
sudo systemctl status amazon-ssm-agent
```
In most cases, the command reports that the agent is running, as shown in the following example.
```
amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/usr/lib/systemd/system/amazon-ssm-agent.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-10-20 19:09:29 UTC; 4min 6s ago
--truncated--
```
In rare cases, the command reports that the agent is installed but not running, as shown in the following example.
```
amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/usr/lib/systemd/system/amazon-ssm-agent.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Wed 2021-10-20 22:16:41 UTC; 18s ago
--truncated--
```
To activate the agent in these cases, run the following commands.
```
sudo systemctl enable amazon-ssm-agent
```
```
sudo systemctl start amazon-ssm-agent
```
## Create custom agent installation commands for Oracle Linux in your Region
When you install SSM Agent on multiple instances using a script or template, we recommend using installation files that are stored in the AWS Region you're working in.
For the following commands, we provide examples that use a publicly accessible S3 bucket in the US East (Ohio) Region (`us-east-2`).
**Tip**
You can also replace a global URL in the procedure [Quick installation commands for SSM Agent on Oracle Linux](#quick-install-oracle) earlier in this topic with a custom Regional URL you construct.
In the following command, replace *region* with your own information. For a list of supported *region* values, see the **Region** column in [Systems Manager service endpoints](https://docs.aws.amazon.com/general/latest/gr/ssm.html#ssm_region) in the *Amazon Web Services General Reference*.
**x86\$164**
```
sudo yum install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_amd64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo yum install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_amd64/amazon-ssm-agent.rpm
```
# Manually installing SSM Agent on Red Hat Enterprise Linux instances
The Amazon Machine Images (AMIs) for Red Hat Enterprise Linux (RHEL) that are provided by AWS do not come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. For a list of AWS managed AMIs on which the agent might be preinstalled, see [Find AMIs with the SSM Agent preinstalled](ami-preinstalled-agent.md).
Use the information in this section to help you manually install or reinstall SSM Agent on a RHEL instance.
**Before you begin**
Before you install SSM Agent on a RHEL instance, note the following:
+ For important information that applies to installation of SSM Agent on all Linux-based operating systems, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](manually-install-ssm-agent-linux.md).
+ If you use a `yum` command to update SSM Agent on a managed node after the agent has been installed or updated using the SSM document `AWS-UpdateSSMAgent`, you might see the following message: `"Warning: RPMDB altered outside of yum."` This message is expected and can be safely ignored.
**Topics**
+ [
# Install SSM Agent on RHEL 8.x, 9.x, and 10.x
](agent-install-rhel-8-9.md)
+ [
# Install SSM Agent on RHEL 7.x
](agent-install-rhel-7.md)
# Install SSM Agent on RHEL 8.x, 9.x, and 10.x
The Amazon Machine Images (AMIs) for RHEL 8 and 9 that are provided by AWS do not come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. Use the information on this page to help you install or reinstall the agent on RHEL 8 and 9 instances.
**Before you begin**
Before you install SSM Agent on a RHEL 8, 9, or 10 instance, note the following:
+ Ensure that either Python 2 or Python 3 is installed on your RHEL 8, 9, or 10 instance. This is required in order for SSM Agent to work properly.
**Topics**
+ [
## Quick installation commands for SSM Agent on RHEL 8, 9, and 10
](#quick-install-rhel-8-9)
+ [
## Create custom agent installation commands for RHEL 8, 9, and 10 in your Region
](#custom-url-rhel-8-9)
## Quick installation commands for SSM Agent on RHEL 8, 9, and 10
Use the following steps to manually install SSM Agent on a single instance. This procedure uses globally available installation files.
**To install SSM Agent on RHEL 8.x, 9.x, or 10.x**
1. Connect to your RHEL 8, 9, or 10 instance using your preferred method, such as SSH.
1. Copy the command for your instance’s architecture and run it on the instance.
**Note**
Even though URLs in the following commands include an `ec2-downloads-windows` directory, these are the correct global installation files for RHEL 8, 9, and 10.
x86\$164 instances
```
sudo dnf install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_amd64/amazon-ssm-agent.rpm
```
ARM64 instances
```
sudo dnf install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_arm64/amazon-ssm-agent.rpm
```
1. (Recommended) Run the following command to verify that the agent is running.
```
sudo systemctl status amazon-ssm-agent
```
In most cases, the command reports that the agent is running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/etc/systemd/system/amazon-ssm-agent.service; enabled; vendo>
Active: active (running) since Tue 2025-04-19 16:40:41 UTC; 9s ago
Main PID: 4898 (amazon-ssm-agen)
Tasks: 14 (limit: 4821)
Memory: 34.6M
CGroup: /system.slice/amazon-ssm-agent.service
├─4898 /usr/bin/amazon-ssm-agent
└─4954 /usr/bin/ssm-agent-worker
--truncated--
```
In rare cases, the command reports that the agent is installed but not running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/etc/systemd/system/amazon-ssm-agent.service; enabled; vendo>
Active: inactive (dead) since Tue 2025-04-19 16:42:05 UTC; 2s ago
--truncated--
```
To activate the agent in these cases, run the following commands.
```
sudo systemctl enable amazon-ssm-agent
```
```
sudo systemctl start amazon-ssm-agent
```
## Create custom agent installation commands for RHEL 8, 9, and 10 in your Region
When you install SSM Agent on multiple instances using a script or template, we recommend using installation files that are stored in the AWS Region you're working in.
For the following commands, we provide examples that use a publicly accessible S3 bucket in the US East (Ohio) Region (`us-east-2`).
**Tip**
You can also replace a global URL in the procedure [Quick installation commands for SSM Agent on RHEL 8, 9, and 10](#quick-install-rhel-8-9) earlier in this topic with a custom Regional URL you construct.
In the following command, replace *region* with your own information. For a list of supported *region* values, see the **Region** column in [Systems Manager service endpoints](https://docs.aws.amazon.com/general/latest/gr/ssm.html#ssm_region) in the *Amazon Web Services General Reference*.
**x86\$164**
```
sudo dnf install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_amd64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo dnf install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_amd64/amazon-ssm-agent.rpm
```
**ARM64**
```
sudo dnf install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_arm64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo dnf install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_arm64/amazon-ssm-agent.rpm
```
# Install SSM Agent on RHEL 7.x
The Amazon Machine Images (AMIs) for RHEL 7 that are provided by AWS do not come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. Use the information on this page to help you install or reinstall the agent on RHEL 7 instances.
**Topics**
+ [
## Quick installation commands for SSM Agent on RHEL 7
](#quick-install-rhel-7)
+ [
## Create custom agent installation commands for RHEL 7 in your Region
](#custom-url-rhel-7)
## Quick installation commands for SSM Agent on RHEL 7
Use the following steps to manually install SSM Agent on a single instance. This procedure uses globally available installation files.
**To install SSM Agent on RHEL 7.x**
1. Connect to your RHEL 7 instance using your preferred method, such as SSH.
1. Copy the command for your instance’s architecture and run it on the instance.
**Note**
Even though URLs in the following commands include an `ec2-downloads-windows` directory, these are the correct global installation files for RHEL 7.
x86\$164 instances
```
sudo yum install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_amd64/amazon-ssm-agent.rpm
```
ARM64 instances
```
sudo yum install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_arm64/amazon-ssm-agent.rpm
```
1. (Recommended) Run the following command to verify that the agent is running.
```
sudo systemctl status amazon-ssm-agent
```
In most cases, the command reports that the agent is running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/etc/systemd/system/amazon-ssm-agent.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2025-04-19 16:47:36 UTC; 22s ago
Main PID: 1342 (amazon-ssm-agen)
CGroup: /system.slice/amazon-ssm-agent.service
├─1342 /usr/bin/amazon-ssm-agent
└─1362 /usr/bin/ssm-agent-worker
--truncated--
```
In rare cases, the command reports that the agent is installed but not running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/etc/systemd/system/amazon-ssm-agent.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Tue 2025-04-19 16:48:56 UTC; 5s ago
Process: 1342 ExecStart=/usr/bin/amazon-ssm-agent (code=exited, status=0/SUCCESS)
Main PID: 1342 (code=exited, status=0/SUCCESS)
--truncated--
```
To activate the agent in these cases, run the following commands.
```
sudo systemctl enable amazon-ssm-agent
```
```
sudo systemctl start amazon-ssm-agent
```
## Create custom agent installation commands for RHEL 7 in your Region
When you install SSM Agent on multiple instances using a script or template, we recommend using installation files that are stored in the AWS Region you're working in.
For the following commands, we provide examples that use a publicly accessible S3 bucket in the US East (Ohio) Region (`us-east-2`).
**Tip**
You can also replace a global URL in the procedure [Quick installation commands for SSM Agent on RHEL 7](#quick-install-rhel-7) earlier in this topic with a custom Regional URL you construct.
In the following command, replace *region* with your own information. For a list of supported *region* values, see the **Region** column in [Systems Manager service endpoints](https://docs.aws.amazon.com/general/latest/gr/ssm.html#ssm_region) in the *Amazon Web Services General Reference*.
**x86\$164**
```
sudo yum install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_amd64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo yum install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_amd64/amazon-ssm-agent.rpm
```
**ARM64**
```
sudo yum install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_arm64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo yum install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_arm64/amazon-ssm-agent.rpm
```
# Manually install SSM Agent on Rocky Linux instances
The Amazon Machine Images (AMIs) for Rocky Linux that are provided by AWS do not come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. For a list of AWS managed AMIs on which the agent might be preinstalled, see [Find AMIs with the SSM Agent preinstalled](ami-preinstalled-agent.md).
Use the information in this section to help you manually install or reinstall SSM Agent on an Rocky Linux instance.
**Before you begin**
Before you install SSM Agent on a Rocky Linux instance, note the following:
+ For important information that applies to installation of SSM Agent on all Linux-based operating systems, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](manually-install-ssm-agent-linux.md).
**Topics**
+ [
## Quick installation commands for SSM Agent on Rocky Linux
](#quick-install-rocky)
+ [
## Create custom agent installation commands for Rocky Linux in your Region
](#custom-url-rocky)
## Quick installation commands for SSM Agent on Rocky Linux
Use the following steps to manually install SSM Agent on a single instance. This procedure uses globally available installation files.
**Before you begin**
Before you install SSM Agent on a Rocky Linux instance, note the following:
+ Ensure that either Python 2 or Python 3 is installed on your Rocky Linux instance. This is required in order for SSM Agent to work properly.
**To install SSM Agent on Rocky Linux**
1. Connect to your Rocky Linux instance using your preferred method, such as SSH.
1. Copy the command for your instance’s architecture and run it on the instance.
**Note**
Even though URLs in the following commands include an `ec2-downloads-windows` directory, these are the correct global installation files for Rocky Linux.
x86\$164 instances
```
sudo dnf install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_amd64/amazon-ssm-agent.rpm
```
ARM64 instances
```
sudo dnf install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_arm64/amazon-ssm-agent.rpm
```
1. (Recommended) Run the following command to verify that the agent is running.
```
sudo systemctl status amazon-ssm-agent
```
In most cases, the command reports that the agent is running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/etc/systemd/system/amazon-ssm-agent.service; enabled; vendo>
Active: active (running) since Tue 2025-04-19 16:40:41 UTC; 9s ago
Main PID: 4898 (amazon-ssm-agen)
Tasks: 14 (limit: 4821)
Memory: 34.6M
CGroup: /system.slice/amazon-ssm-agent.service
├─4898 /usr/bin/amazon-ssm-agent
└─4954 /usr/bin/ssm-agent-worker
--truncated--
```
In rare cases, the command reports that the agent is installed but not running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/etc/systemd/system/amazon-ssm-agent.service; enabled; vendo>
Active: inactive (dead) since Tue 2025-04-19 16:42:05 UTC; 2s ago
--truncated--
```
To activate the agent in these cases, run the following commands.
```
sudo systemctl enable amazon-ssm-agent
```
```
sudo systemctl start amazon-ssm-agent
```
## Create custom agent installation commands for Rocky Linux in your Region
When you install SSM Agent on multiple instances using a script or template, we recommend using installation files that are stored in the AWS Region you're working in.
For the following commands, we provide examples that use a publicly accessible S3 bucket in the US East (Ohio) Region (`us-east-2`).
**Tip**
You can also replace a global URL in the procedure [Quick installation commands for SSM Agent on Rocky Linux](#quick-install-rocky) earlier in this topic with a custom Regional URL you construct.
In the following command, replace *region* with your own information. For a list of supported *region* values, see the **Region** column in [Systems Manager service endpoints](https://docs.aws.amazon.com/general/latest/gr/ssm.html#ssm_region) in the *Amazon Web Services General Reference*.
**x86\$164**
```
sudo dnf install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_amd64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo dnf install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_amd64/amazon-ssm-agent.rpm
```
**ARM64**
```
sudo dnf install -y https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_arm64/amazon-ssm-agent.rpm
```
See the following example.
```
sudo dnf install -y https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_arm64/amazon-ssm-agent.rpm
```
# Manually install SSM Agent on SUSE Linux Enterprise Server instances
In most cases, the Amazon Machine Images (AMIs) for SUSE Linux Enterprise Server (SLES) that are provided by AWS come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. For more information, see [Find AMIs with the SSM Agent preinstalled](ami-preinstalled-agent.md).
In the event that SSM Agent isn’t preinstalled on a new SLES instance, or if you need to manually reinstall the agent, use the information on this page to help you.
**Before you begin**
Before you install SSM Agent on a SLES instance, note the following:
+ For important information that applies to installation of SSM Agent on all Linux-based operating systems, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](manually-install-ssm-agent-linux.md).
**Topics**
+ [
## Quick installation commands for SSM Agent on SLES
](#quick-install-sles)
+ [
## Create custom agent installation commands for SLES in your Region
](#custom-url-sles)
## Quick installation commands for SSM Agent on SLES
Use the following steps to manually install SSM Agent on a single instance. This procedure uses globally available installation files.
**To install SSM Agent on SLES using quick copy and paste commands**
1. Connect to your SLES instance using your preferred method, such as SSH.
1. **Option 1**: Use a `zypper` command:
+ Run the following command:
```
sudo zypper install amazon-ssm-agent
```
+ Enter `y` in response to any prompts.
**Option 2**: Use an `rpm` command.
+ Create a temporary directory on the instance.
```
mkdir /tmp/ssm
```
+ Change to the temporary directory.
```
cd /tmp/ssm
```
+ Run the following commands one at a time to download and run the SSM Agent installer.
**Note**
Even though URLs in the following commands include an `ec2-downloads-windows` directory, these are the correct global installation files for SLES.
x86\$164 instances:
```
wget https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_amd64/amazon-ssm-agent.rpm
```
ARM64 instances:
```
wget https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_arm64/amazon-ssm-agent.rpm
```
+ Run the following command.
```
sudo rpm ‐‐install amazon-ssm-agent.rpm
```
+ (Recommended) Run the following command to verify that the agent is running.
```
sudo systemctl status amazon-ssm-agent
```
In most cases, the command reports that the agent is running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/usr/lib/systemd/system/amazon-ssm-agent.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2025-02-21 23:13:28 UTC; 7s ago
Main PID: 2102 (amazon-ssm-agen)
Tasks: 15 (limit: 512)
CGroup: /system.slice/amazon-ssm-agent.service
├─2102 /usr/sbin/amazon-ssm-agent
└─2107 /usr/sbin/ssm-agent-worker
‐‐truncated‐‐
```
In rare cases, the command reports that the agent is installed but not running, as shown in the following example.
```
● amazon-ssm-agent.service - amazon-ssm-agent
Loaded: loaded (/usr/lib/systemd/system/amazon-ssm-agent.service; disabled; vendor preset: disabled)
Active: inactive (dead)
‐‐truncated‐‐
```
To activate the agent in these cases, run the following commands.
```
sudo systemctl enable amazon-ssm-agent
```
```
sudo systemctl start amazon-ssm-agent
```
## Create custom agent installation commands for SLES in your Region
When you install SSM Agent on multiple instances using a script or template, we recommend using installation files that are stored in the AWS Region you're working in.
For the following commands, we provide examples that use a publicly accessible S3 bucket in the US East (Ohio) Region (`us-east-2`).
**Tip**
You can also replace a global URL in the procedure [Quick installation commands for SSM Agent on SLES](#quick-install-sles) earlier in this topic with a custom Regional URL you construct.
In the following command, replace *region* with your own information. For a list of supported *region* values, see the **Region** column in [Systems Manager service endpoints](https://docs.aws.amazon.com/general/latest/gr/ssm.html#ssm_region) in the *Amazon Web Services General Reference*.
**x86\$164**
```
wget https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_amd64/amazon-ssm-agent.rpm
```
```
sudo rpm ‐‐install amazon-ssm-agent.rpm
```
See the following example.
```
wget https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_amd64/amazon-ssm-agent.rpm
```
```
sudo rpm ‐‐install amazon-ssm-agent.rpm
```
**ARM64**
```
wget https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_arm64/amazon-ssm-agent.rpm
```
```
sudo rpm ‐‐install amazon-ssm-agent.rpm
```
See the following example.
```
wget https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/linux_arm64/amazon-ssm-agent.rpm
```
```
sudo rpm ‐‐install amazon-ssm-agent.rpm
```
# Manually installing SSM Agent on Ubuntu Server instances
**Important**
Before you install SSM Agent on a 64-bit version of Ubuntu Server, ensure that you are using the correct installation tools. Beginning with Amazon Machine Images (AMIs) that are identified with 20180627, SSM Agent is pre-installed on version 16.04 using Snap packages. On instances created from earlier AMIs, SSM Agent must be installed using deb installer packages. For more information, see [Determining the correct SSM Agent version to install on 64-bit Ubuntu Server 16.04 instances](agent-install-ubuntu-about-v16.md).
In most cases, the Amazon Machine Images (AMIs) for Ubuntu Server that are provided by AWS come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. For more information, see [Find AMIs with the SSM Agent preinstalled](ami-preinstalled-agent.md).
In the event that SSM Agent isn’t preinstalled on a new Ubuntu Server instance, or if you need to manually reinstall the agent, use the information in this section to help you.
**Before you begin**
Before you install SSM Agent on an Ubuntu Server instance, note the following:
+ For important information that applies to installation of SSM Agent on all Linux-based operating systems, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](manually-install-ssm-agent-linux.md).
**Topics**
+ [
# Install SSM Agent on Ubuntu Server 16.04 LTS 64-bit (Snap), 18.04, 20.04, 22.04 LTS, 23.10, 24.04 LTS, 24.0, and 25.04
](agent-install-ubuntu-64-snap.md)
+ [
# Install SSM Agent on Ubuntu Server 16.04 64-bit (deb)
](agent-install-ubuntu-64-deb.md)
+ [
# Install SSM Agent on Ubuntu Server 16.04 32-bit
](agent-install-ubuntu-32.md)
+ [
# Determining the correct SSM Agent version to install on 64-bit Ubuntu Server 16.04 instances
](agent-install-ubuntu-about-v16.md)
# Install SSM Agent on Ubuntu Server 16.04 LTS 64-bit (Snap), 18.04, 20.04, 22.04 LTS, 23.10, 24.04 LTS, 24.0, and 25.04
**Before you begin**
Before you install SSM Agent on an Ubuntu Server 16.04 LTS 64-bit (Snap), 18.04, 20.04, 22.04 LTS, 23.10, 24.04 LTS, 24.0, and 25.04, note the following:
Version 16.04 installation by Snaps or deb installers
On Ubuntu Server 16.04, SSM Agent is installed using either Snaps or deb installation packages, depending on the version of the 16.04 AMI.
SSM Agent installer files locations
On Ubuntu Server 16.04 LTS 64-bit (Snap), 18.04, 20.04, 22.04 LTS, 23.10, 24.04 LTS, 24.0, and 25.04, SSM Agent installer files, including agent binaries and config files, are stored in the following directory: `/snap/amazon-ssm-agent/current/`. If you make changes to any configuration files in this directory, then you must copy these files from the `/snap` directory to the `/etc/amazon/ssm/` directory. Log and library files haven't changed (`/var/lib/amazon/ssm`, `/var/log/amazon/ssm`).
Using the Snap `candidate` channel
The *candidate* channel in the Snap store contains the latest version of SSM Agent (including all of the latest bug fixes); not the stable channel. To learn more about the differences between the candidate and stable channels, see **Risk-levels** at [https://snapcraft.io/docs/channels](https://snapcraft.io/docs/channels).
If you want to track SSM Agent version information on the candidate channel, run the following command on your Ubuntu Server 20.04, 18.04, and 16.04 LTS 64-bit instances.
```
sudo snap switch --channel=candidate amazon-ssm-agent
```
Snaps recommended on versions 18.04 and later
On Ubuntu Server 18.04, 20.04, 22.04 LTS, 23.10, 24.04 LTS, 24.0, and 25.04, we recommend you only use Snaps. Also verify that only one instance of the agent is installed and running on your instances. If you want to use SSM Agent without Snaps, uninstall the SSM Agent. Then [install the SSM Agent as a debian package](agent-install-ubuntu-64-deb.md) using the instructions for installing SSM Agent on Ubuntu Server 16.04 (deb). Before installing, ensure you don't have any Snaps installed that overlap with the list of packages you want managed as debian packages.
`Maximum timeout exceeded` error message
Because of a known issue with Snap, you might see a `Maximum timeout exceeded` error with `snap` commands. If you get this error, run the following commands one at a time to start the agent, stop it, and check its status:
```
sudo systemctl start snap.amazon-ssm-agent.amazon-ssm-agent.service
```
```
sudo systemctl stop snap.amazon-ssm-agent.amazon-ssm-agent.service
```
```
sudo systemctl status snap.amazon-ssm-agent.amazon-ssm-agent.service
```
**To install SSM Agent on Ubuntu Server 16.04 LTS 64-bit (Snap), 18.04, 20.04, 22.04 LTS, 23.10, 24.04 LTS, 24.0, and 25.04 (with Snap package)**
1. SSM Agent is installed, by default, on Ubuntu Server 16.04 LTS 64-bit (Snap), 18.04, 20.04, 22.04 LTS, 23.10, 24.04 LTS, 24.0, and 25.04 AMIs with an identifier of `20180627` or later.
You can use the following script if you need to install SSM Agent on an on-premises server or if you need to reinstall the agent. You don't need to specify a URL for the download, because the `snap` command automatically downloads the agent from the [Snap app store](https://snapcraft.io/amazon-ssm-agent) at [https://snapcraft.io](https://snapcraft.io).
```
sudo snap install amazon-ssm-agent --classic
```
1. Run the following command to determine if SSM Agent is running.
```
sudo snap list amazon-ssm-agent
```
1. Run the following command to start the service if the previous command returned `amazon-ssm-agent is stopped`, `inactive`, or `disabled`.
```
sudo snap start amazon-ssm-agent
```
1. Check the status of the agent.
```
sudo snap services amazon-ssm-agent
```
# Install SSM Agent on Ubuntu Server 16.04 64-bit (deb)
**Important**
Before you install SSM Agent on a 64-bit version of Ubuntu Server, ensure that you are using the correction installation tools. Beginning with Amazon Machine Images (AMIs) that are identified with 20180627, SSM Agent is pre-installed on version 16.04 using Snap packages. On instances created from earlier AMIs, SSM Agent must be installed using deb installer packages. For more information, see [Determining the correct SSM Agent version to install on 64-bit Ubuntu Server 16.04 instances](agent-install-ubuntu-about-v16.md).If SSM Agent is installed on your instance in conjunction with a Snap and you install or update SSM Agent using a deb installer package, the installation or SSM Agent operations might fail.
In most cases, the Amazon Machine Images (AMIs) Ubuntu Server 16.04 that are provided by AWS come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. For more information, see [Find AMIs with the SSM Agent preinstalled](ami-preinstalled-agent.md).
In the event that SSM Agent isn’t preinstalled on a new Ubuntu Server 16.04 instance prior to version 20180627 or you need to manually reinstall the agent, use the information on this page to help you.
## Quick installation commands for SSM Agent on Ubuntu Server 16.04 (deb)
Use the following steps to manually install SSM Agent on a single instance. This procedure uses globally available installation files.
**To install SSM Agent on Ubuntu Server 16.04 64-bit (deb) using quick copy and paste commands**
1. Connect to your Ubuntu Server instance using your preferred method, such as SSH.
1. Run the following command to create a temporary directory on the instance.
```
mkdir /tmp/ssm
```
1. Change to the temporary directory.
```
cd /tmp/ssm
```
1. Run the following commands.
**Note**
Even though URLs in the following commands include an `ec2-downloads-windows` directory, these are the correct global installation files for Ubuntu Server 16.04 64-bit.
```
wget https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/debian_amd64/amazon-ssm-agent.deb
```
```
sudo dpkg -i amazon-ssm-agent.deb
```
1. (Recommended) Run the following command to determine if SSM Agent is running.
Ubuntu Server 16.04
```
sudo systemctl status amazon-ssm-agent
```
In most cases, the command reports that the agent is running.
In rare cases, the command reports that the agent is installed but not running, as shown in the following example.
1. Run the following command to start the service if the previous command returned `amazon-ssm-agent is stopped`, `inactive`, or `disabled`.
Ubuntu Server 16.04:
```
sudo systemctl enable amazon-ssm-agent
```
## Create custom installation commands for SSM Agent on Ubuntu Server 16.04 64-bit (deb) in your Region
When you install SSM Agent on multiple instances using a script or template, we recommend using installation files that are stored in the AWS Region you're working in.
For the following commands, we provide examples that use a publicly accessible S3 bucket in the US East (Ohio) Region (`us-east-2`).
**Tip**
You can also replace a global URL in the procedure [Quick installation commands for SSM Agent on Ubuntu Server 16.04 (deb)](#quick-install-ub-16-14-64-bit) earlier in this topic with a custom Regional URL you construct.
In the following command, replace *region* with your own information. For a list of supported *region* values, see the **Region** column in [Systems Manager service endpoints](https://docs.aws.amazon.com/general/latest/gr/ssm.html#ssm_region) in the *Amazon Web Services General Reference*.
```
wget https://s3.region.amazonaws.com/amazon-ssm-region/latest/debian_amd64/amazon-ssm-agent.deb
```
```
sudo dpkg -i amazon-ssm-agent.deb
```
See the following example.
```
wget https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/debian_amd64/amazon-ssm-agent.deb
```
```
sudo dpkg -i amazon-ssm-agent.deb
```
# Install SSM Agent on Ubuntu Server 16.04 32-bit
In most cases, the Amazon Machine Images (AMIs) Ubuntu Server 16.04 that are provided by AWS come with AWS Systems Manager Agent (SSM Agent) preinstalled by default. For more information, see [Find AMIs with the SSM Agent preinstalled](ami-preinstalled-agent.md).
In the event that SSM Agent isn’t preinstalled on a new Ubuntu Server 16.04 instance or you need to manually reinstall the agent, use the information on this page to help you.
## Quick installation commands for SSM Agent on Ubuntu Server 16.04 32-bit (deb)
Use the following steps to manually install SSM Agent on a single instance. This procedure uses globally available installation files.
**To install SSM Agent on Ubuntu Server 16.04 32-bit (deb) using quick copy and paste commands**
1. Connect to your Ubuntu Server instance using your preferred method, such as SSH.
1. Run the following command to create a temporary directory on the instance.
```
mkdir /tmp/ssm
```
1. Change to the temporary directory.
```
cd /tmp/ssm
```
1. Run the following commands.
**Note**
Even though URL in the following command include an `ec2-downloads-windows` directory, this is the correct global installation file for Ubuntu Server 16.04 32-bit.
```
wget https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/debian_386/amazon-ssm-agent.deb
```
```
sudo dpkg -i amazon-ssm-agent.deb
```
1. (Recommended) Run the following command to determine if SSM Agent is running.
Ubuntu Server 16.04
```
sudo systemctl status amazon-ssm-agent
```
In most cases, the command reports that the agent is running.
In rare cases, the command reports that the agent is installed but not running, as shown in the following example.
1. Run the following command to start the service if the previous command returned `amazon-ssm-agent is stopped`, `inactive`, or `disabled`.
Ubuntu Server 16.04:
```
sudo systemctl enable amazon-ssm-agent
```
## Create custom installation commands for SSM Agent on Ubuntu Server 16.04 32-bit (deb) in your Region
When you install SSM Agent on multiple instances using a script or template, we recommend using installation files that are stored in the AWS Region you're working in.
For the following commands, we provide examples that use a publicly accessible S3 bucket in the US East (Ohio) Region (`us-east-2`).
**Tip**
You can also replace a global URL in the procedure [Quick installation commands for SSM Agent on Ubuntu Server 16.04 32-bit (deb)](#quick-install-ub-16-14-32-bit) earlier in this topic with a custom Regional URL you construct.
In the following command, replace *region* with your own information. For a list of supported *region* values, see the **Region** column in [Systems Manager service endpoints](https://docs.aws.amazon.com/general/latest/gr/ssm.html#ssm_region) in the *Amazon Web Services General Reference*.
```
wget https://s3.region.amazonaws.com/amazon-ssm-region/latest/debian_386/amazon-ssm-agent.deb
```
```
sudo dpkg -i amazon-ssm-agent.deb
```
See the following example.
```
wget https://s3.us-east-2.amazonaws.com/amazon-ssm-us-east-2/latest/debian_386/amazon-ssm-agent.deb
```
```
sudo dpkg -i amazon-ssm-agent.deb
```
# Determining the correct SSM Agent version to install on 64-bit Ubuntu Server 16.04 instances
**Important**
Before you install SSM Agent on a 64-bit version of Ubuntu Server, ensure that you are using the correction installation tools. Beginning with Amazon Machine Images (AMIs) that are identified with 20180627, SSM Agent is pre-installed on version 16.04 using Snap packages. On instances created from earlier AMIs, SSM Agent must be installed using deb installer packages. For more information, see [Determining the correct SSM Agent version to install on 64-bit Ubuntu Server 16.04 instances](#agent-install-ubuntu-about-v16)
Be aware that if an instance has more than one installation of the SSM Agent (for example, one installed using a Snap and one installed using a deb installer), your agent operations won't work correctly.
You can verify the source AMI ID creation date for an instance using either of the following methods. These procedures apply only to AWS managed AMIs.
**Verify a source AMI ID creation date (console)**
1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/).
1. In the left navigation pane, choose **Instances**.
1. Select an instance.
1. On the **Details** tab, check for a `YYYYMMDD` identifier in the value under **AMI name** field. For example: `ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20180627`.
**Verify a source AMI ID creation date (AWS CLI)**
+ Run the following command.
```
aws ec2 describe-images --image-ids ami-id
```
*ami-id* represents the ID of an AMI provided by AWS, such as `ami-07c8bc5c1ce9598c3`.
If successful, the command returns information like the following, in which you can check the `CreationDate` and `Name` fields for information.
```
{
"Images": [
{
"Architecture": "x86_64",
"CreationDate": "2020-07-24T20:40:27.000Z",
"ImageId": "ami-07c8bc5c1ce9598c3",
-- truncated --
"ImageOwnerAlias": "amazon",
"Name": "amzn2-ami-hvm-2.0.20200722.0-x86_64-gp2",
"RootDeviceName": "/dev/xvda",
"RootDeviceType": "ebs",
"SriovNetSupport": "simple",
"VirtualizationType": "hvm"
}
]
}
```