AWS awssupport documentation change
Summary
Added an Important note emphasizing customer responsibility to review managed policy scope and maintain additional policies for uncovered services
Security assessment
The change adds guidance about security responsibility and policy management but does not address a specific vulnerability. It highlights the need for manual verification of permissions scope, which is a security best practice but not evidence of a resolved security issue.
Diff
diff --git a/awssupport/latest/user/managed-policies-partner-led-support.md b/awssupport/latest/user/managed-policies-partner-led-support.md index 24d2fd365..61b77b0c5 100644 --- a//awssupport/latest/user/managed-policies-partner-led-support.md +++ b//awssupport/latest/user/managed-policies-partner-led-support.md @@ -21 +21,5 @@ You can attach `AWSPartnerLedSupportReadOnlyAccess` to your users, groups, and r -This policy can be used to grant read-only access to APIs that can read service metadata for services in your AWS account. You can use this policy to provide your partners in the AWS Partner-Led Support Program with access to the services specified in the permissions details section below. +This policy can be used to grant read-only access to APIs that can read service metadata for services in your AWS account. You can use this policy to provide your partners in the AWS Partner-Led Support Program with access to the services specified in the following permissions details section. + +###### Important + +Although AWSPartnerLedSupportReadOnlyAccess is a managed policy provided by AWS, you're responsible for reviewing the services and permissions that are included in the policy to verify that they meet your specific support requirements. Don't assume that this managed policy automatically includes all existing or new AWS services. You might need to create and maintain additional custom policies to cover services outside the scope of this managed policy.