AWS Security ChangesHomeSearch

AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2025-11-13 · Documentation low

File: prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/managing-permissions-for-individuals.md

Summary

Removed AWS Proton from the list of service-linked role examples

Security assessment

The change narrows the example to AWS Service Catalog but does not provide evidence of a security concern. It is likely a documentation simplification.

Diff

diff --git a/prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/managing-permissions-for-individuals.md b/prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/managing-permissions-for-individuals.md
index 5f3c239f0..5d411983c 100644
--- a//prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/managing-permissions-for-individuals.md
+++ b//prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/managing-permissions-for-individuals.md
@@ -9 +9 @@ By using permissions sets, the permissions boundary, and the **CloudFormationRol
-You can also use _service-linked roles_ , which grant permissions to an AWS service to provision resources on your behalf. Instead of granting permissions to the IAM principal (user, user group, or role), you can grant the permissions to the service. For example, the service-linked roles for [AWS Proton](https://docs.aws.amazon.com/proton/latest/userguide/Welcome.html) and [AWS Service Catalog](https://docs.aws.amazon.com/servicecatalog/latest/adminguide/introduction.html) allow you to provision your own templates, resources, and environments, without assigning permissions to the IAM principal. For more information, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) and [Using service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html) (IAM documentation).
+You can also use _service-linked roles_ , which grant permissions to an AWS service to provision resources on your behalf. Instead of granting permissions to the IAM principal (user, user group, or role), you can grant the permissions to the service. For example, the service-linked role for [AWS Service Catalog](https://docs.aws.amazon.com/servicecatalog/latest/adminguide/introduction.html) allows you to provision your own templates, resources, and environments, without assigning permissions to the IAM principal. For more information, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) and [Using service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html) (IAM documentation).