• 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 SSM Agent on Ubuntu Server instances Ubuntu Server **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 Versions 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) Versions 16.04 and 14.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 Versions 16.04 and 14.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" } ] } ```