AWS systems-manager documentation change
Summary
Updated documentation to reflect supported OS versions (Amazon Linux 2023.8, RHEL 8.x) in examples and guidance. Removed references to outdated RHEL 5/7 versions and deprecated Amazon Linux 2016.09.
Security assessment
Changes update version numbers and examples to current supported OS versions but do not directly address vulnerabilities. While using supported versions is a security best practice, there is no explicit mention of patching vulnerabilities or addressing exploits.
Diff
diff --git a/systems-manager/latest/userguide/distributor-working-with-packages-create.md b/systems-manager/latest/userguide/distributor-working-with-packages-create.md index 75fe133d9..bcedde215 100644 --- a//systems-manager/latest/userguide/distributor-working-with-packages-create.md +++ b//systems-manager/latest/userguide/distributor-working-with-packages-create.md @@ -54 +54 @@ Use the `In-place` update option to add new or updated files to an existing pack -For the **Simple** package creation workflow, because you upload each installable file only once, extra steps are required to instruct Distributor to target a single file at multiple operating systems. For example, if you upload an installable software file named `Logtool_v1.1.1.rpm`, you must change some defaults in the **Simple** workflow to target the same software at both Amazon Linux and Ubuntu operating systems. When targeting multiple platforms, do one of the following. +For the **Simple** package creation workflow, because you upload each installable file only once, extra steps are required to instruct Distributor to target a single file at multiple operating systems. For example, if you upload an installable software file named `Logtool_v1.1.1.rpm`, you must change some defaults in the **Simple** workflow to target the same software on supported versions of both Amazon Linux and Ubuntu Server operating systems. When targeting multiple platforms, do one of the following. @@ -108 +108 @@ An example package, [ExamplePackage.zip](https://docs.aws.amazon.com/systems-man -The foundation of your package is at least one .zip file of software or installable assets. A package includes one .zip file per operating system that you want to support, unless one .zip file can be installed on multiple operating systems. For example, Red Hat Enterprise Linux and Amazon Linux instances can typically run the same .RPM executable files, so you need to attach only one .zip file to your package to support both operating systems. +The foundation of your package is at least one .zip file of software or installable assets. A package includes one .zip file per operating system that you want to support, unless one .zip file can be installed on multiple operating systems. For example, supported versions of Red Hat Enterprise Linux and Amazon Linux instances can typically run the same .RPM executable files, so you need to attach only one .zip file to your package to support both operating systems. @@ -264 +264 @@ You can add the `_any` wildcard value to indicate that the package supports all -The following example adds `_any` to show that the first package, `data1.zip`, is supported for all architectures of Amazon Linux 2016.09. The second package, `data2.zip`, is supported for all releases of Amazon Linux, but only for managed nodes with `x86_64` architecture. Both the `2016.09` and `_any` versions are entries under `amazon`. There is one platform (Amazon Linux), but different supported versions, architectures, and associated .zip files. +The following example adds `_any` to show that the first package, `data1.zip`, is supported for all architectures of Amazon Linux 2016.09. The second package, `data2.zip`, is supported for all releases of Amazon Linux, but only for managed nodes with `x86_64` architecture. Both the `2023.8` and `_any` versions are entries under `amazon`. There is one platform (Amazon Linux), but different supported versions, architectures, and associated .zip files. @@ -268 +268 @@ The following example adds `_any` to show that the first package, `data1.zip`, i - "2016.09": { + "2023.8": { @@ -281 +281 @@ The following example adds `_any` to show that the first package, `data1.zip`, i -You can refer to a .zip file more than once in the `"packages"` section of the manifest, if the .zip file supports more than one platform. For example, if you have a .zip file that supports both Red Hat Enterprise Linux 7.x versions and Amazon Linux, you have two entries in the `"packages"` section that point to the same .zip file, as shown in the following example. +You can refer to a .zip file more than once in the `"packages"` section of the manifest, if the .zip file supports more than one platform. For example, if you have a .zip file that supports both Red Hat Enterprise Linux 8.x versions and Amazon Linux, you have two entries in the `"packages"` section that point to the same .zip file, as shown in the following example. @@ -285 +285 @@ You can refer to a .zip file more than once in the `"packages"` section of the m - "2018.03": { + "2023.8.20250715 ": { @@ -292 +292 @@ You can refer to a .zip file more than once in the `"packages"` section of the m - "7.*": { + "8.*": { @@ -322 +322 @@ The `"files"` section of the manifest includes one reference to each of the .zip - "test-agent-rhel5-x86.nano.zip": { + "test-agent-rhel8-x86.nano.zip": { @@ -337 +337 @@ The `"files"` section of the manifest includes one reference to each of the .zip - "test-agent-rhel5-x86.rpm.zip": { + "test-agent-rhel8-x86.rpm.zip": { @@ -341,5 +340,0 @@ The `"files"` section of the manifest includes one reference to each of the .zip - }, - "test-agent-rhel5-x86_64.rpm.zip": { - "checksums": { - "sha256": "EXAMPLE7ce8a2c471a23b5c90761a180fd157ec0469e12ed38a7094d1EXAMPLE" - }