• 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).
# Working with SSM Agent on EC2 instances for Linux
AWS Systems Manager Agent (SSM Agent) processes Systems Manager requests and configures your machine as specified in the request. Use the procedures in following topics to install, configure, or uninstall SSM Agent on Linux operating systems.
**Topics**
+ [Verifying the signature of SSM Agent](verify-agent-signature.md)
+ [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](manually-install-ssm-agent-linux.md)
+ [Configuring SSM Agent to use a proxy on Linux nodes](configure-proxy-ssm-agent.md)
# Verifying the signature of SSM Agent
The AWS Systems Manager Agent (SSM Agent) deb and rpm installer packages for Linux instances are cryptographically signed. You can use a public key to verify that the agent package is original and unmodified. If the files are damaged or have been altered, the verification fails. You can verify the signature of the installer package using either RPM or GPG. The following information is for SSM Agent versions 3.1.1141.0 or later.
To find the correct signature file for your instance's architecture and operating system, see the following table.
*region* represents the identifier for an AWS Region supported by AWS Systems Manager, such as `us-east-2` for the US East (Ohio) Region. 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*.
| Architecture | Operating system | Signature file URL | Agent download file name |
| --- | --- | --- | --- |
| x86\$164 | AlmaLinux, Amazon Linux 2, Amazon Linux 2023, RHEL, Oracle Linux, Rocky Linux | `https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_amd64/amazon-ssm-agent.rpm.sig` `https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_amd64/amazon-ssm-agent.rpm.sig` | `amazon-ssm-agent.rpm` |
| x86\$164 | Debian Server, Ubuntu Server | `https://s3.region.amazonaws.com/amazon-ssm-region/latest/debian_amd64/amazon-ssm-agent.deb.sig` `https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/debian_amd64/amazon-ssm-agent.deb.sig` | amazon-ssm-agent.deb |
| ARM64 | Amazon Linux 2, Amazon Linux 2023, RHEL | `https://s3.region.amazonaws.com/amazon-ssm-region/latest/linux_arm64/amazon-ssm-agent.rpm.sig` `https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_arm64/amazon-ssm-agent.rpm.sig` | amazon-ssm-agent.rpm |
## Verifying the SSM Agent package on a Linux server (v3.3.1802.0 and later)
**Before you begin**
The procedures for **GPG** and **RPM** in this section apply to SSM Agent version 3.3.1802.0 and later. Before verifying the signature of SSM Agent using the following procedure, ensure that you have downloaded the latest agent package for your operating system. For example, `https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_arm64/amazon-ssm-agent.rpm`. For more information about downloading SSM Agent packages, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](manually-install-ssm-agent-linux.md).
If you have a reason to continue using agent version 3.3.1611.0 or earlier, follow the instructions in [Verifying the SSM Agent package on a Linux server (v3.3.1611.0 and earlier)](#verify-agent-signature-previous) instead.
------
#### [ GPG ]
**To verify the SSM Agent package on a Linux server (v3.3.1802.0 and later)**
1. Copy one the following public key and save it to a file named `amazon-ssm-agent.gpg`.
**Important**
The following public key expires on 2026-07-15 (July 15, 2026). Systems Manager will publish a new public key in this topic before the old one expires. We encourage you to subscribe to the RSS feed for this topic to get a notification when the new key is available.
```
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2.0.22 (GNU/Linux)
mQINBGeRNq4BEACrlf5h6Pz+k+M+QCJJ2LfK7d2Tn9J8iJ9qBK2Vwvuxco1rpSO+
KEI3nTeysPuheximps8WOCADX4VlbsKxMZQLjQM4mA26m1Tiw9nAI4kod4bKjiuM
BMUTCD1wfnjH3zQi4kDUdbpfAEMiPgNLVLH85Wf+lhK+Zm+V38DYzLyVj03kX4wK
iG6RMoxzOBZa5gNsVq+j+oCUITGz/URxH713Rgo8WeoEegI0+7iCBLKg+PM0b7GV
2nzkwWJz796HdkqSg8BwXsYaLTrHxa2P1IpwPCisAkyO7gZaMd6Uj69dtMFO+V8a
Qee6b57qGuFKZw7h1Vvc85PbF1Gy/wNIpary57kUHBFUg1vYep/roJuEbJCq97r5
I2liLl4NAyrWb9r/TAVxlXvqM4iZUhxm8GAp0FywMdBr9ZECClKa5HxuVmlm0Wgl
TXoYTOZKeDg6ZoCvyhNxWneCNip74fohXymeFF5L/budhBwy5wuwSniOgTGLo/4C
VgZHWCcN+d0Q3bx/sl2QNqPg5/xzsxEtymXLdVdwLIsLdEQUnIvy8KTs5jol3Dwi
nnEEyhly6wdaw+qDOhkSOT/VnErrSMkYF8VJfa5GjhCBWKw9JVSkaP2CI/VHOgHM
MKROnulq0hRQBR7RmLYt98xu38BHJWMmF8Ga/HJuIxzD1VmkZOPvDDESUwARAQAB
tCdTU00gQWdlbnQgPHNzbS1hZ2VudC1zaWduZXJAYW1hem9uLmNvbT6JAj8EEwEC
ACkFAmeRNq4CGy8FCQLGmIAHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRBR
qOBQ0AUuXTdND/9qldQ1E3dYjBVXOnbhiUQL594bkS5VoEX7D4fZ5UMVZa5pGiz+
husnoRUS9rH1cSeq7aHJu9hSCMuMdvRpuoo0CwLB+7HtzJvAO2M01hcEkUYa6Qdj
njTzP0ZjnoenJmqF9SYmVqAI/VPa9mNQ1OJ+HQ3qh5i6w+FoWlVqEdXjZGrWijub
TqyN33i1Y26t7Os/x8I9fUeNx37y/7Kama8LTdtv9GhWiMVBg2IuVf27HCMYofrQ
m2uCGe61IhtsnhsYaYupmljl+6qgdiuCiS9BAsoIGtqTnu8lnKcGyGz6YnRszN+U
1bNE4w+UFpXWJF8ogpYcghJ06aW/LhjZnQSx3VliLdW8eOJzou41yWmiuL3ZY8eW
KAlD+7eYKS6N6fEJCeNO2VX2lcKtDfaOX+lqGIVyexKayMfpi+0frNzt/92YCpF5
3jkeS77vMMVqKIUiIp1OCGv3XsFpIr6Bt2c2throYPDoQL3zvq6vvG40BKeRQ4tT
Y+5vTc8MeNn3LdzTl9pusxTcKifrJq7f5FIsL2CpAX8uQ+Qz+XWsYQQ5PvyUDtOz
nU/MRZaP6HnqY42bzI9ZlKgXi9IE3MXIwoET9YyzFjkIDvat7SlB4uJCpeIqp/KM
OIrTMb7paGLYmBU6YqxNBkDWItNG7NeZzyhh/R/Qqb4vJaf4S+ZqD1RZXokCHAQQ
AQIABgUCZ5E2rwAKCRB90Jej2tf1/CdnD/46It+RNoE00TesZK5n2bijH5Eljw0E
4/UpMi1SV6t2zY7lIm7TcKNn18tynJNFqB6YXXOwSbBG/fbN2E9RaoUCZw23TmAv
amuHwrfsDqsHb7zzPF0bISYjqEDLQJj/gtEugUc6XY1dEpFSlWJIOvgryG04cFXI
uD2KY87ya4s1R+sEVAJ14K4RlUCiMmzJdR0NJNYJOwBi1gkLEp6jG86ttiG2U7fY
pE2ibV+c0GeIFq8PIzqqENsn9KBuRH5EcbdBwfnsj2XfM4aR3ZtRIdWXkKkdP9Rs
yU5dTF/Y7XPId5h8/gp00+DMlXFBinQ1jE7A7eDYviEFd1ba8P7dIom3Q3gzKiWu
KTGpnykShs5NvpQmvGUF6JqDHI4RK9s3kLqsNyZkhenJfRBrJ/45fQAuP4CRedkF
7PSfX0Xp7kDnKuyK6wEUEfXXrqmuLGDmigTXblO5qgdyMwkOLjiY9znBZbHoKs76
VplOoNgGnN19i3nuMcPf2npFICJv7kTIyn5Fh7pjWDCahl3U/PwoLjrrlEzpyStU
oXSZrK3kiAADEdSODXJl8KYU0Pb27JbRr1ZbWnxb+O39TOhtssstulkR0v+IDGDQ
rQE1b12sKgcNFSzInzWrNGu4S06WN8DYzlrTZ9aSHj+37ZqpXAevi8WOFXKPV3PA
E6+O8RI2451Dcg==
=aDkv
-----END PGP PUBLIC KEY BLOCK-----
```
1. Import the public key into your keyring, and note the returned key value.
```
gpg --import amazon-ssm-agent.gpg
```
1. Verify the fingerprint. Be sure to replace *key-value* with the value from the preceding step. We recommend that you use GPG to verify the fingerprint even if you use RPM to verify the installer package.
```
gpg --fingerprint key-value
```
This command returns output similar to the following:
```
pub 4096R/D0052E5D 2025-01-22 [expires: 2026-07-15]
Key fingerprint = 4855 A9E6 8332 16D6 A77D 8FE4 51A8 E050 D005 2E5D
uid SSM Agent
```
The fingerprint should match the following.
`4855 A9E6 8332 16D6 A77D 8FE4 51A8 E050 D005 2E5D`
If the fingerprint doesn't match, don't install the agent. Contact AWS Support.
1. Download the signature file according to your instance's architecture and operating system if you haven't already done so.
1. Verify the installer package signature. Be sure to replace the *signature-filename* and *agent-download-filename* with the values you specified when downloading the signature file and agent, as listed in the table earlier in this topic.
```
gpg --verify signature-filename agent-download-filename
```
For example, for the x86\$164 architecture on Amazon Linux 2:
```
gpg --verify amazon-ssm-agent.rpm.sig amazon-ssm-agent.rpm
```
This command returns output similar to the following:
```
gpg: Signature made Sat 08 Feb 2025 12:05:08 AM UTC using RSA key ID D0052E5D
gpg: Good signature from "SSM Agent "
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 4855 A9E6 8332 16D6 A77D 8FE4 51A8 E050 D005 2E5D
```
If the output includes the phrase `BAD signature`, check whether you performed the procedure correctly. If you continue to get this response, contact Support and don't install the agent. The warning message about the trust doesn't mean that the signature isn't valid, only that you haven't verified the public key. A key is trusted only if you or someone who you trust has signed it. If the output includes the phrase `Can't check signature: No public key`, verify you downloaded SSM Agent version 3.1.1141.0 or later.
------
#### [ RPM ]
**To verify the SSM Agent package on a Linux server (v3.3.1802.0 and later)**
1. Copy the following public key and save it to a file named `amazon-ssm-agent.gpg`.
**Important**
The following public key expires on 2026-07-15 (July 15, 2026). Systems Manager will publish a new public key in this topic before the old one expires. We encourage you to subscribe to the RSS feed for this topic to get a notification when the new key is available.
```
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2.0.22 (GNU/Linux)
mQINBGeRNq4BEACrlf5h6Pz+k+M+QCJJ2LfK7d2Tn9J8iJ9qBK2Vwvuxco1rpSO+
KEI3nTeysPuheximps8WOCADX4VlbsKxMZQLjQM4mA26m1Tiw9nAI4kod4bKjiuM
BMUTCD1wfnjH3zQi4kDUdbpfAEMiPgNLVLH85Wf+lhK+Zm+V38DYzLyVj03kX4wK
iG6RMoxzOBZa5gNsVq+j+oCUITGz/URxH713Rgo8WeoEegI0+7iCBLKg+PM0b7GV
2nzkwWJz796HdkqSg8BwXsYaLTrHxa2P1IpwPCisAkyO7gZaMd6Uj69dtMFO+V8a
Qee6b57qGuFKZw7h1Vvc85PbF1Gy/wNIpary57kUHBFUg1vYep/roJuEbJCq97r5
I2liLl4NAyrWb9r/TAVxlXvqM4iZUhxm8GAp0FywMdBr9ZECClKa5HxuVmlm0Wgl
TXoYTOZKeDg6ZoCvyhNxWneCNip74fohXymeFF5L/budhBwy5wuwSniOgTGLo/4C
VgZHWCcN+d0Q3bx/sl2QNqPg5/xzsxEtymXLdVdwLIsLdEQUnIvy8KTs5jol3Dwi
nnEEyhly6wdaw+qDOhkSOT/VnErrSMkYF8VJfa5GjhCBWKw9JVSkaP2CI/VHOgHM
MKROnulq0hRQBR7RmLYt98xu38BHJWMmF8Ga/HJuIxzD1VmkZOPvDDESUwARAQAB
tCdTU00gQWdlbnQgPHNzbS1hZ2VudC1zaWduZXJAYW1hem9uLmNvbT6JAj8EEwEC
ACkFAmeRNq4CGy8FCQLGmIAHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRBR
qOBQ0AUuXTdND/9qldQ1E3dYjBVXOnbhiUQL594bkS5VoEX7D4fZ5UMVZa5pGiz+
husnoRUS9rH1cSeq7aHJu9hSCMuMdvRpuoo0CwLB+7HtzJvAO2M01hcEkUYa6Qdj
njTzP0ZjnoenJmqF9SYmVqAI/VPa9mNQ1OJ+HQ3qh5i6w+FoWlVqEdXjZGrWijub
TqyN33i1Y26t7Os/x8I9fUeNx37y/7Kama8LTdtv9GhWiMVBg2IuVf27HCMYofrQ
m2uCGe61IhtsnhsYaYupmljl+6qgdiuCiS9BAsoIGtqTnu8lnKcGyGz6YnRszN+U
1bNE4w+UFpXWJF8ogpYcghJ06aW/LhjZnQSx3VliLdW8eOJzou41yWmiuL3ZY8eW
KAlD+7eYKS6N6fEJCeNO2VX2lcKtDfaOX+lqGIVyexKayMfpi+0frNzt/92YCpF5
3jkeS77vMMVqKIUiIp1OCGv3XsFpIr6Bt2c2throYPDoQL3zvq6vvG40BKeRQ4tT
Y+5vTc8MeNn3LdzTl9pusxTcKifrJq7f5FIsL2CpAX8uQ+Qz+XWsYQQ5PvyUDtOz
nU/MRZaP6HnqY42bzI9ZlKgXi9IE3MXIwoET9YyzFjkIDvat7SlB4uJCpeIqp/KM
OIrTMb7paGLYmBU6YqxNBkDWItNG7NeZzyhh/R/Qqb4vJaf4S+ZqD1RZXokCHAQQ
AQIABgUCZ5E2rwAKCRB90Jej2tf1/CdnD/46It+RNoE00TesZK5n2bijH5Eljw0E
4/UpMi1SV6t2zY7lIm7TcKNn18tynJNFqB6YXXOwSbBG/fbN2E9RaoUCZw23TmAv
amuHwrfsDqsHb7zzPF0bISYjqEDLQJj/gtEugUc6XY1dEpFSlWJIOvgryG04cFXI
uD2KY87ya4s1R+sEVAJ14K4RlUCiMmzJdR0NJNYJOwBi1gkLEp6jG86ttiG2U7fY
pE2ibV+c0GeIFq8PIzqqENsn9KBuRH5EcbdBwfnsj2XfM4aR3ZtRIdWXkKkdP9Rs
yU5dTF/Y7XPId5h8/gp00+DMlXFBinQ1jE7A7eDYviEFd1ba8P7dIom3Q3gzKiWu
KTGpnykShs5NvpQmvGUF6JqDHI4RK9s3kLqsNyZkhenJfRBrJ/45fQAuP4CRedkF
7PSfX0Xp7kDnKuyK6wEUEfXXrqmuLGDmigTXblO5qgdyMwkOLjiY9znBZbHoKs76
VplOoNgGnN19i3nuMcPf2npFICJv7kTIyn5Fh7pjWDCahl3U/PwoLjrrlEzpyStU
oXSZrK3kiAADEdSODXJl8KYU0Pb27JbRr1ZbWnxb+O39TOhtssstulkR0v+IDGDQ
rQE1b12sKgcNFSzInzWrNGu4S06WN8DYzlrTZ9aSHj+37ZqpXAevi8WOFXKPV3PA
E6+O8RI2451Dcg==
=aDkv
-----END PGP PUBLIC KEY BLOCK-----
```
1. Import the public key into your keyring, and note the returned key value.
```
rpm --import amazon-ssm-agent.gpg
```
1. Verify the fingerprint. We recommend that you use GPG to verify the fingerprint even if you use RPM to verify the installer package.
```
rpm -qa gpg-pubkey --qf '%{Description}' | gpg --with-fingerprint | grep -A 1 "ssm-agent-signer@amazon.com"
```
This command returns output similar to the following:
```
pub 4096R/D0052E5D 2025-01-22 SSM Agent
Key fingerprint = 4855 A9E6 8332 16D6 A77D 8FE4 51A8 E050 D005 2E5D
```
The fingerprint should match the following.
`4855 A9E6 8332 16D6 A77D 8FE4 51A8 E050 D005 2E5D`
If the fingerprint doesn't match, don't install the agent. Contact AWS Support.
1. Verify the installer package signature. Be sure to replace the *agent-download-filename* with the values you specified when downloading the agent, as listed in the table earlier in this topic.
```
rpm --checksig agent-download-filename
```
For example, for the x86\$164 architecture on Amazon Linux 2:
```
rpm --checksig amazon-ssm-agent.rpm
```
This command returns output similar to the following.
```
amazon-ssm-agent.rpm: rsa sha1 md5 OK
```
If `pgp` is missing from the output and you have imported the public key, then the agent isn't signed. If the output contains the phrase `NOT OK (MISSING KEYS: (MD5) key-id)`, check whether you performed the procedure correctly and verify you downloaded SSM Agent version 3.1.1141.0 or later. If you continue to get this response, contact Support and don't install the agent.
------
## Verifying the SSM Agent package on a Linux server (v3.3.1611.0 and earlier)
**Before you begin**
The procedures for **GPG** and **RPM** in this section apply to SSM Agent version 3.3.1611.0 and earlier versions. We recommend always using the latest version of the agent. For information, see [Verifying the SSM Agent package on a Linux server (v3.3.1802.0 and later)](#verify-agent-signature-current). However, if you have a specific reason to continue using agent version 3.3.1611.0 or earlier, follow the instructions in one of the following procedures.
------
#### [ GPG ]
**To verify the SSM Agent package on a Linux server (v3.3.1611.0 and earlier)**
1. Copy the following public keys and save it to a file named `amazon-ssm-agent.gpg`.
**Important**
The public key shown below expired on 2025-02-17 (February 17, 2025) and works for Version 3.3.1611.0 and earlier versions up to 3.2.1542.0, and only if it was used previously to verify the agent's signature. Systems Manager will publish a new public key in this topic before the old one expires. We encourage you to subscribe to the RSS feed for this topic to get a notification when the new key is available.
```
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2.0.22 (GNU/Linux)
mQENBGTtIoIBCAD2M1aoGIE0FXynAHM/jtuvdAVVaX3Q4ZejTqrX+Jq8ElAMhxyO
GzHu2CDtCYxtVxXK3unptLVt2kGgJwNbhYC393jDeZx5dCda4Nk2YXX1UK3P461i
axuuXRzMYvfM4RZn+7bJTu635tA07q9Xm6MGD4TCTvsjBfViOxbrxOg5ozWbJdSw
fSR8MwUrRfmFpAefRlYfCEuZ8FHywa9U6jLeWt2O/kqrZliJOAGjGzXtB7EZkqKb
faCCxikjjvhF1awdEqSK4DQorC/OvQc4I5kP5y2CJbtXvXO73QH2yE75JMDIIx9x
rOsIRUoSfK3UrWaOVuAnEEn5ueKzZNqGG1J1ABEBAAG0J1NTTSBBZ2VudCA8c3Nt
LWFnZW50LXNpZ25lckBhbWF6b24uY29tPokBPwQTAQIAKQUCZO0iggIbLwUJAsaY
gAcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJELwfSVyX3QTt+icH/A//tJsW
I+7Ay8FGJh8dJPNy++HIBjVSFdGNJFWNbw1Z8uZcazHEcUCH3FhW4CLQLTZ3OVPz
qvFwzDtRDVIN/Y9EGDhLMFvimrE+/z4olWsJ5DANf6BnX8I5UNIcRt5d8SWH1BEJ
2FWIBZFgKyTDI6XzRC5x4ahtgpOVAGeeKDehs+wh6Ga4W0/K4GsviP1Kyr+Ic2br
NAIq0q0IHyN1q9zam3Y0+jKwEuNmTj+Bjyzshyv/X8S0JWWoXJhkexkOvWeBYNNt
5wI4QcSteyfIzp6KlQF8q11Hzz9D9WaPfcBEYyhq7vLEARobkbQMBzpkmaZua241
0RaWG50HRvrgm4aJAhwEEAECAAYFAmTtIoMACgkQfdCXo9rX9fwwqBAAzkTgYJ38
sWgxpn7Ux/81F2BWR1sVkmP79i++fXyJlKI8xtcJFQZhzeUos69KBUCy7mgx5bYU
P7NA5o9DUbwz/QS0i1Cqm4+jtFlX0MXe4FikXcqfDPnnzN8mVB2H+fa43iHR1PuH
GgUWuNdxzSoIYRmLZXWmeN5YXPcmixlhLzcE2TOQn1mOKcu2fKdLtBQ8KiEkmjiu
naoLxnUcyk1zMhaha+LzEkQdOyasix0ggylN2ViWVnlmfy0niuXDxW0qZWPdLStF
OODiX3iqGmkH3rDfy6nvxxBR4GIs+MGD72fpWzzrINDgkGI2i2t1+0AX/mps3aTy
+ftlgrim8stYWB58XXDAb0vad06sNye5/zDzfr0I9HupJrTzFhaYJQjWPaSlINto
LDJnBXohiUIPRYRcy/k012oFHDWZHT3H6CyjK9UD5UlxA9H7dsJurANs6FOVRe+7
34uJyxDZ/W7zLG4AVG0zxibrUSoaJxwcOjVPVsQAlrwG/GTs7tcAccsJqbJ1Py/w
9AgJl8VU2qc8POsHNXk348gjP7C8PDnGMpZFzr9f5INctRushpiv7onX+aWJVX7T
n2uX/TP3LCyH/MsrNJrJOQnMYFRLQitciP0E+F+eA3v9CY6mDuyb8JSx5HuGGUsG
S4bKBOcA8vimEpwPoT8CE7fdsZ3Qkwdu+pw=
=zr5w
-----END PGP PUBLIC KEY BLOCK-----
```
1. Import the public key into your keyring, and note the returned key value.
```
gpg --import amazon-ssm-agent.gpg
```
1. Verify the fingerprint. Be sure to replace *key-value* with the value from the preceding step. We recommend that you use GPG to verify the fingerprint even if you use RPM to verify the installer package.
```
gpg --fingerprint key-value
```
This command returns output similar to the following.
```
pub 2048R/97DD04ED 2023-08-28 [expired: 2025-02-17]
Key fingerprint = DE92 C7DA 3E56 E923 31D6 2A36 BC1F 495C 97DD 04ED
uid SSM Agent
```
The fingerprint should match the following.
`DE92 C7DA 3E56 E923 31D6 2A36 BC1F 495C 97DD 04ED`
If the fingerprint doesn't match, don't install the agent. Contact AWS Support.
1. Download the signature file according to your instance's architecture and operating system if you haven't already done so.
1. Verify the installer package signature. Be sure to replace the *signature-filename* and *agent-download-filename* with the values you specified when downloading the signature file and agent, as listed in the table earlier in this topic.
```
gpg --verify signature-filename agent-download-filename
```
For example, for the x86\$164 architecture on Amazon Linux 2:
```
gpg --verify amazon-ssm-agent.rpm.sig amazon-ssm-agent.rpm
```
This command returns output similar to the following:
```
gpg: Signature made Fri 10 Jan 2025 01:54:18 AM UTC using RSA key ID 97DD04ED
gpg: Good signature from "SSM Agent "
gpg: Note: This key has expired!
Primary key fingerprint: DE92 C7DA 3E56 E923 31D6 2A36 BC1F 495C 97DD 04ED
```
If the output includes the phrase `BAD signature`, check whether you performed the procedure correctly. If you continue to get this response, contact Support and don't install the agent. The warning message about the trust doesn't mean that the signature isn't valid, only that you haven't verified the public key. A key is trusted only if you or someone who you trust has signed it. If the output includes the phrase `Can't check signature: No public key`, verify you downloaded SSM Agent version 3.1.1141.0 or later.
------
#### [ RPM ]
**To verify the SSM Agent package on a Linux server (v3.3.1611.0 and earlier)**
1. Copy the following public key and save it to a file named `amazon-ssm-agent.gpg`.
**Important**
The public key shown below expired on 2025-02-17 (February 17, 2025) and works for Version 3.3.1611.0 and earlier versions up to 3.2.1542.0, and only if it was used previously to verify the agent's signature. Systems Manager will publish a new public key in this topic before the old one expires. We encourage you to subscribe to the RSS feed for this topic to get a notification when the new key is available.
```
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2.0.22 (GNU/Linux)
mQENBGTtIoIBCAD2M1aoGIE0FXynAHM/jtuvdAVVaX3Q4ZejTqrX+Jq8ElAMhxyO
GzHu2CDtCYxtVxXK3unptLVt2kGgJwNbhYC393jDeZx5dCda4Nk2YXX1UK3P461i
axuuXRzMYvfM4RZn+7bJTu635tA07q9Xm6MGD4TCTvsjBfViOxbrxOg5ozWbJdSw
fSR8MwUrRfmFpAefRlYfCEuZ8FHywa9U6jLeWt2O/kqrZliJOAGjGzXtB7EZkqKb
faCCxikjjvhF1awdEqSK4DQorC/OvQc4I5kP5y2CJbtXvXO73QH2yE75JMDIIx9x
rOsIRUoSfK3UrWaOVuAnEEn5ueKzZNqGG1J1ABEBAAG0J1NTTSBBZ2VudCA8c3Nt
LWFnZW50LXNpZ25lckBhbWF6b24uY29tPokBPwQTAQIAKQUCZO0iggIbLwUJAsaY
gAcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJELwfSVyX3QTt+icH/A//tJsW
I+7Ay8FGJh8dJPNy++HIBjVSFdGNJFWNbw1Z8uZcazHEcUCH3FhW4CLQLTZ3OVPz
qvFwzDtRDVIN/Y9EGDhLMFvimrE+/z4olWsJ5DANf6BnX8I5UNIcRt5d8SWH1BEJ
2FWIBZFgKyTDI6XzRC5x4ahtgpOVAGeeKDehs+wh6Ga4W0/K4GsviP1Kyr+Ic2br
NAIq0q0IHyN1q9zam3Y0+jKwEuNmTj+Bjyzshyv/X8S0JWWoXJhkexkOvWeBYNNt
5wI4QcSteyfIzp6KlQF8q11Hzz9D9WaPfcBEYyhq7vLEARobkbQMBzpkmaZua241
0RaWG50HRvrgm4aJAhwEEAECAAYFAmTtIoMACgkQfdCXo9rX9fwwqBAAzkTgYJ38
sWgxpn7Ux/81F2BWR1sVkmP79i++fXyJlKI8xtcJFQZhzeUos69KBUCy7mgx5bYU
P7NA5o9DUbwz/QS0i1Cqm4+jtFlX0MXe4FikXcqfDPnnzN8mVB2H+fa43iHR1PuH
GgUWuNdxzSoIYRmLZXWmeN5YXPcmixlhLzcE2TOQn1mOKcu2fKdLtBQ8KiEkmjiu
naoLxnUcyk1zMhaha+LzEkQdOyasix0ggylN2ViWVnlmfy0niuXDxW0qZWPdLStF
OODiX3iqGmkH3rDfy6nvxxBR4GIs+MGD72fpWzzrINDgkGI2i2t1+0AX/mps3aTy
+ftlgrim8stYWB58XXDAb0vad06sNye5/zDzfr0I9HupJrTzFhaYJQjWPaSlINto
LDJnBXohiUIPRYRcy/k012oFHDWZHT3H6CyjK9UD5UlxA9H7dsJurANs6FOVRe+7
34uJyxDZ/W7zLG4AVG0zxibrUSoaJxwcOjVPVsQAlrwG/GTs7tcAccsJqbJ1Py/w
9AgJl8VU2qc8POsHNXk348gjP7C8PDnGMpZFzr9f5INctRushpiv7onX+aWJVX7T
n2uX/TP3LCyH/MsrNJrJOQnMYFRLQitciP0E+F+eA3v9CY6mDuyb8JSx5HuGGUsG
S4bKBOcA8vimEpwPoT8CE7fdsZ3Qkwdu+pw=
=zr5w
-----END PGP PUBLIC KEY BLOCK-----
```
1. Import the public key into your keyring, and note the returned key value.
```
rpm --import amazon-ssm-agent.gpg
```
1. Verify the fingerprint. We recommend that you use GPG to verify the fingerprint even if you use RPM to verify the installer package.
```
rpm -qa gpg-pubkey --qf '%{Description}' | gpg --with-fingerprint | grep -A 1 "ssm-agent-signer@amazon.com"
```
This command returns output similar to the following:
```
pub 2048R/97DD04ED 2023-08-28 SSM Agent
Key fingerprint = DE92 C7DA 3E56 E923 31D6 2A36 BC1F 495C 97DD 04ED
```
The fingerprint should match the following.
`DE92 C7DA 3E56 E923 31D6 2A36 BC1F 495C 97DD 04ED`
If the fingerprint doesn't match, don't install the agent. Contact AWS Support.
1. Verify the installer package signature. Be sure to replace the *agent-download-filename* with the values you specified when downloading the agent, as listed in the table earlier in this topic.
```
rpm --checksig agent-download-filename
```
For example, for the x86\$164 architecture on Amazon Linux 2:
```
rpm --checksig amazon-ssm-agent.rpm
```
This command returns output similar to the following.
```
amazon-ssm-agent.rpm: rsa sha1 md5 OK
```
If `pgp` is missing from the output and you have imported the public key, then the agent isn't signed. If the output contains the phrase `NOT OK (MISSING KEYS: (MD5) key-id)`, check whether you performed the procedure correctly and verify you downloaded SSM Agent version 3.1.1141.0 or later. If you continue to get this response, contact Support and don't install the agent.
------
# 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"
}
]
}
```
# Configuring SSM Agent to use a proxy on Linux nodes
You can configure AWS Systems Manager Agent (SSM Agent) to communicate through an HTTP proxy by creating an override configuration file and adding `http_proxy`, `https_proxy`, and `no_proxy` settings to the file. An override file also preserves the proxy settings if you install newer or older versions of SSM Agent. This section includes procedures for creating an override file in both *upstart* and *systemd* environments. If you intend to use Session Manager, note that HTTPS proxy servers aren't supported.
**Topics**
+ [Configure SSM Agent to use a proxy (upstart)](#ssm-agent-proxy-upstart)
+ [Configure SSM Agent to use a proxy (systemd)](#ssm-agent-proxy-systemd)
## Configure SSM Agent to use a proxy (upstart)
Use the following procedure to create an override configuration file for an `upstart` environment.
**To configure SSM Agent to use a proxy (upstart)**
1. Connect to the managed instance where you installed SSM Agent.
1. Open a simple editor like VIM, and depending on whether you're using an HTTP proxy server or HTTPS proxy server, add one of the following configurations.
**For an HTTP proxy server:**
```
env http_proxy=http://hostname:port
env https_proxy=http://hostname:port
env no_proxy=IP address for instance metadata services (IMDS)
```
**For an HTTPS proxy server:**
```
env http_proxy=http://hostname:port
env https_proxy=https://hostname:port
env no_proxy=IP address for instance metadata services (IMDS)
```
**Important**
Add the `no_proxy` setting to the file and specify the IP address. The IP address for `no_proxy` is the instance metadata services (IMDS) endpoint for Systems Manager. If you don't specify `no_proxy`, calls to Systems Manager take on the identity from the proxy service (if IMDSv1 fallback is enabled) or calls to Systems Manager fail (if IMDSv2 is enforced).
For IPv4, specify `no_proxy=169.254.169.254`.
For IPv6, specify `no_proxy=[fd00:ec2::254]`. The IPv6 address of the instance metadata service is compatible with IMDSv2 commands. The IPv6 address is only accessible on instances built on the [AWS Nitro System](https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-nitro-instances.html). For more information, see [How Instance Metadata Service Version 2 works](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-metadata-v2-how-it-works.html) in the *Amazon EC2 User Guide*.
1. Save the file with the name `amazon-ssm-agent.override` in the following location: `/etc/init/`
1. Stop and restart SSM Agent using the following commands.
```
sudo service stop amazon-ssm-agent
sudo service start amazon-ssm-agent
```
**Note**
For more information about working with `.override` files in Upstart environments, see [init: Upstart init daemon job configuration](https://www.systutorials.com/docs/linux/man/5-init/).
## Configure SSM Agent to use a proxy (systemd)
Use the following procedure to configure SSM Agent to use a proxy in a `systemd` environment.
**Note**
Some of the steps in this procedure contain explicit instructions for Ubuntu Server instances where SSM Agent was installed using Snap.
1. Connect to the instance where you installed SSM Agent.
1. Run one of the follow commands, depending on the operating system type.
+ On Ubuntu Server instances where SSM Agent is installed by using a snap:
```
sudo systemctl edit snap.amazon-ssm-agent.amazon-ssm-agent
```
On other operating systems:
```
sudo systemctl edit amazon-ssm-agent
```
1. Open a simple editor like VIM, and depending on whether you're using an HTTP proxy server or HTTPS proxy server, add one of the following configurations.
![\[Enter new content above the line "### Lines below this comment will be discarded."\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/update-proxy-callout.png)
**For an HTTP proxy server:**
```
[Service]
Environment="http_proxy=http://hostname:port"
Environment="https_proxy=http://hostname:port"
Environment="no_proxy=IP address for instance metadata services (IMDS)"
```
**For an HTTPS proxy server:**
```
[Service]
Environment="http_proxy=http://hostname:port"
Environment="https_proxy=https://hostname:port"
Environment="no_proxy=IP address for instance metadata services (IMDS)"
```
**Important**
Add the `no_proxy` setting to the file and specify the IP address. The IP address for `no_proxy` is the instance metadata services (IMDS) endpoint for Systems Manager. If you don't specify `no_proxy`, calls to Systems Manager take on the identity from the proxy service (if IMDSv1 fallback is enabled) or calls to Systems Manager fail (if IMDSv2 is enforced).
For IPv4, specify `no_proxy=169.254.169.254`.
For IPv6, specify `no_proxy=[fd00:ec2::254]`. The IPv6 address of the instance metadata service is compatible with IMDSv2 commands. The IPv6 address is only accessible on instances built on the [AWS Nitro System](https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-nitro-instances.html). For more information, see [How Instance Metadata Service Version 2 works](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-metadata-v2-how-it-works.html) in the *Amazon EC2 User Guide*.
1. Save your changes. The system automatically creates one of the following files, depending on the operating system type.
+ On Ubuntu Server instances where SSM Agent is installed by using a snap:
`/etc/systemd/system/snap.amazon-ssm-agent.amazon-ssm-agent.service.d/override.conf`
+ On Amazon Linux 2, Amazon Linux 2023, and RHEL instances:
`/etc/systemd/system/amazon-ssm-agent.service.d/override.conf`
+ On other operating systems:
`/etc/systemd/system/amazon-ssm-agent.service.d/amazon-ssm-agent.override`
1. Restart SSM Agent by using one of the following commands, depending on the operating system type.
+ On Ubuntu Server instances installed by using a snap:
```
sudo systemctl daemon-reload && sudo systemctl restart snap.amazon-ssm-agent.amazon-ssm-agent
```
+ On other operating systems:
```
sudo systemctl daemon-reload && sudo systemctl restart amazon-ssm-agent
```
**Note**
For more information about working with `.override` files in systemd environments, see [Modifying Existing Unit Files](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/chap-managing_services_with_systemd#sect-Managing_Services_with_systemd-Unit_File_Modify) in the *Red Hat Enterprise Linux 7 System Administrator's Guide*.