AWS IAM documentation change
Summary
Updated references from 'Organizations' to 'AWS Organizations' for service name consistency in multiple example scenarios
Security assessment
Changes only correct service name references without altering security content or addressing vulnerabilities. The updates maintain existing security guidance about reviewing access patterns but don't introduce new security features or address specific vulnerabilities.
Diff
diff --git a/IAM/latest/UserGuide/access_policies_last-accessed-example-scenarios.md b/IAM/latest/UserGuide/access_policies_last-accessed-example-scenarios.md index f9d3d93f0..e005b17e0 100644 --- a//IAM/latest/UserGuide/access_policies_last-accessed-example-scenarios.md +++ b//IAM/latest/UserGuide/access_policies_last-accessed-example-scenarios.md @@ -58 +58 @@ Paulo decides to wait for 90 days before he [views the last accessed information -Paulo decides to reduce the policy permissions to include only those five services and the required IAM and Organizations actions. He edits `ExampleDevelopment` policy using the following JSON text. +Paulo decides to reduce the policy permissions to include only those five services and the required IAM and AWS Organizations actions. He edits `ExampleDevelopment` policy using the following JSON text. @@ -145 +145 @@ You can review last accessed information for an IAM identity (user, group, or ro -For example, Arnav Desai is a developer and AWS administrator for Example Corp. When his team started using AWS, they gave all developers power-user access that allowed them full access to all services except IAM and Organizations. As a first step towards [granting least privilege](./best-practices.html#grant-least-privilege), Arnav wants to use the AWS CLI to review the managed policies in his account. +For example, Arnav Desai is a developer and AWS administrator for Example Corp. When his team started using AWS, they gave all developers power-user access that allowed them full access to all services except IAM and AWS Organizations. As a first step towards [granting least privilege](./best-practices.html#grant-least-privilege), Arnav wants to use the AWS CLI to review the managed policies in his account. @@ -233 +233 @@ For example, John Stiles is an AWS Organizations administrator. He is responsibl -John signs into the IAM console using his management account credentials. In the IAM console, he locates the Organizations data for the `Development` OU. He reviews the **Service access report** table and sees two AWS services that have not been accessed in more than his preferred period of 180 days. He remembers adding permissions for the development teams to access Amazon Lex and AWS Database Migration Service. John contacts the development teams and confirms that they no longer have a business need to test these services. +John signs into the IAM console using his management account credentials. In the IAM console, he locates the AWS Organizations data for the `Development` OU. He reviews the **Service access report** table and sees two AWS services that have not been accessed in more than his preferred period of 180 days. He remembers adding permissions for the development teams to access Amazon Lex and AWS Database Migration Service. John contacts the development teams and confirms that they no longer have a business need to test these services. @@ -235 +235 @@ John signs into the IAM console using his management account credentials. In the -John is now ready to act on the last accessed information. He chooses **Edit in AWS Organizations** and is reminded that the SCP is attached to multiple entities. He chooses **Continue**. In AWS Organizations, he reviews the targets to learn to which Organizations entities that the SCP is attached. All of entities are within the `Development` OU. +John is now ready to act on the last accessed information. He chooses **Edit in AWS Organizations** and is reminded that the SCP is attached to multiple entities. He chooses **Continue**. In AWS Organizations, he reviews the targets to learn to which AWS Organizations entities that the SCP is attached. All of entities are within the `Development` OU. @@ -245 +245 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -View access information for Organizations +View access information for AWS Organizations