AWS Security ChangesHomeSearch

AWS systems-manager documentation change

Service: systems-manager · 2025-08-16 · Documentation low

File: systems-manager/latest/userguide/security_iam_service-with-iam.md

Summary

Replaced image-based footnote callouts with bold text markers in resource ARN documentation

Security assessment

The change improves documentation formatting but doesn't alter security content or address vulnerabilities. The footnote content about resource versioning and parameter hierarchies remains unchanged.

Diff

diff --git a/systems-manager/latest/userguide/security_iam_service-with-iam.md b/systems-manager/latest/userguide/security_iam_service-with-iam.md
index d872210ed..87b84306c 100644
--- a//systems-manager/latest/userguide/security_iam_service-with-iam.md
+++ b//systems-manager/latest/userguide/security_iam_service-with-iam.md
@@ -161 +161 @@ Automation execution | arn:aws:ssm:`region`:`account-id`:automation-execution/`a
-Automation definition (with version subresource) |  arn:aws:ssm:`region`:`account-id`:automation-definition/`automation-definition-id`:`version-id` ![Footnote callout 1 to explain a line in a JSON policy](/images/systems-manager/latest/userguide/images/callout01.png)  
+Automation definition (with version subresource) |  arn:aws:ssm:`region`:`account-id`:automation-definition/`automation-definition-id`:`version-id` **1**  
@@ -178 +178 @@ A parameter named with a hierarchical construction:
-  * arn:aws:ssm:`region`:`account-id`:parameter/`parameter-name-root`/`level-2`/`level-3`/`level-4`/`level-5` ![Footnote callout 2 to explain a line in a JSON policy](/images/systems-manager/latest/userguide/images/callout02.png)
+  * arn:aws:ssm:`region`:`account-id`:parameter/`parameter-name-root`/`level-2`/`level-3`/`level-4`/`level-5` **2**
@@ -183 +183 @@ Response plan |  arn:aws:ssm-incidents:`region`:`account-id`:response-plan/`resp
-Session |  arn:aws:ssm:`region`:`account-id`:session/`session-id` ![Footnote callout 3 to explain a line in a JSON policy](/images/systems-manager/latest/userguide/images/callout03.png)  
+Session |  arn:aws:ssm:`region`:`account-id`:session/`session-id` **3**  
@@ -187 +187 @@ All Systems Manager resources owned by the specified AWS account in the specifie
-![Footnote callout 1 to explain a line in a JSON policy](/images/systems-manager/latest/userguide/images/callout01.png) For automation definitions, Systems Manager supports a second-level resource, _version ID_. In AWS, these second-level resources are known as _subresources_. Specifying a version subresource for an automation definition resource allows you to provide access to certain versions of an automation definition. For example, you might want to ensure that only the latest version of an automation definition is used in your node management.
+**1** For automation definitions, Systems Manager supports a second-level resource, _version ID_. In AWS, these second-level resources are known as _subresources_. Specifying a version subresource for an automation definition resource allows you to provide access to certain versions of an automation definition. For example, you might want to ensure that only the latest version of an automation definition is used in your node management.
@@ -189 +189 @@ All Systems Manager resources owned by the specified AWS account in the specifie
-![Footnote callout 2 to explain a line in a JSON policy](/images/systems-manager/latest/userguide/images/callout02.png) To organize and manage parameters, you can create names for parameters with a hierarchical construction. With hierarchical construction, a parameter name can include a path that you define by using forward slashes. You can name a parameter resource with a maximum of fifteen levels. We suggest that you create hierarchies that reflect an existing hierarchical structure in your environment. For more information, see [Creating Parameter Store parameters in Systems Manager](./sysman-paramstore-su-create.html).
+**2** To organize and manage parameters, you can create names for parameters with a hierarchical construction. With hierarchical construction, a parameter name can include a path that you define by using forward slashes. You can name a parameter resource with a maximum of fifteen levels. We suggest that you create hierarchies that reflect an existing hierarchical structure in your environment. For more information, see [Creating Parameter Store parameters in Systems Manager](./sysman-paramstore-su-create.html).
@@ -191 +191 @@ All Systems Manager resources owned by the specified AWS account in the specifie
-![Footnote callout 3 to explain a line in a JSON policy](/images/systems-manager/latest/userguide/images/callout03.png) In most cases, the session ID is constructed using the ID of the account user who started the session, plus an alphanumeric suffix. For example:
+**3** In most cases, the session ID is constructed using the ID of the account user who started the session, plus an alphanumeric suffix. For example: