AWS systems-manager-automation-runbooks documentation change
Summary
Updated IAM documentation link in security note
Security assessment
Existing security warning about S3 containment risks remains unmodified. Only documentation URLs were reformatted.
Diff
diff --git a/systems-manager-automation-runbooks/latest/userguide/automation-awssupport-contains3resource.md b/systems-manager-automation-runbooks/latest/userguide/automation-awssupport-contains3resource.md index 579975139..9e95dd2c9 100644 --- a//systems-manager-automation-runbooks/latest/userguide/automation-awssupport-contains3resource.md +++ b//systems-manager-automation-runbooks/latest/userguide/automation-awssupport-contains3resource.md @@ -13 +13 @@ The `AWSSupport-ContainS3Resource` runbook provides an automated solution for th - * This runbook performs various operations that require elevated privileges, such as modifying Amazon S3 bucket policies, tags, and public access configurations. These actions could potentially lead to privilege escalation or impact other workloads that depend on the targeted Amazon S3 bucket. You should review the permissions granted to the role specified by the `AutomationAssumeRole` parameter and ensure they are appropriate for the intended use case. You can refer to the following AWS documentation for more information on IAM permissions: [`Identity and Access Management (IAM) Permissions`](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_controlling.html) [`AWS AWS Systems Manager Automation Permissions`](https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-setup-iam.html). + * This runbook performs various operations that require elevated privileges, such as modifying Amazon S3 bucket policies, tags, and public access configurations. These actions could potentially lead to privilege escalation or impact other workloads that depend on the targeted Amazon S3 bucket. You should review the permissions granted to the role specified by the `AutomationAssumeRole` parameter and ensure they are appropriate for the intended use case. You can refer to the following AWS documentation for more information on IAM permissions: [`Identity and Access Management (IAM) Permissions`](https://docs.aws.amazon.com//IAM/latest/UserGuide/access_controlling.html) [`AWS AWS Systems Manager Automation Permissions`](https://docs.aws.amazon.com//systems-manager/latest/userguide/automation-setup-iam.html). @@ -370 +370 @@ Systems Manager Automation - * [Run an automation](https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-working-executing.html) + * [Run an automation](https://docs.aws.amazon.com//systems-manager/latest/userguide/automation-working-executing.html) @@ -372 +372 @@ Systems Manager Automation - * [Setting up an Automation](https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-setup.html) + * [Setting up an Automation](https://docs.aws.amazon.com//systems-manager/latest/userguide/automation-setup.html)