AWS Security ChangesHomeSearch

AWS IAM documentation change

Service: IAM · 2025-04-03 · Documentation low

File: IAM/latest/UserGuide/document-history.md

Summary

Added 'AWS' prefix to Organizations references in multiple changelog entries

Security assessment

Consistent product naming updates in historical documentation, no security content changes

Diff

diff --git a/IAM/latest/UserGuide/document-history.md b/IAM/latest/UserGuide/document-history.md
index 2d409cc1e..3a374ce60 100644
--- a//IAM/latest/UserGuide/document-history.md
+++ b//IAM/latest/UserGuide/document-history.md
@@ -29 +29 @@ Change| Description| Date
-[Support for AWS Organizations resource control policies (RCPs)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policy-types)| Use an Organizations resource control policy (RCP) to define the maximum permissions for resources within accounts in your organization or organizational unit (OU). RCPs limit permissions that identity-based and resource-based policies can grant to resources in accounts within your organization.| November 13, 2024  
+[Support for AWS Organizations resource control policies (RCPs)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policy-types)| Use an AWS Organizations resource control policy (RCP) to define the maximum permissions for resources within accounts in your organization or organizational unit (OU). RCPs limit permissions that identity-based and resource-based policies can grant to resources in accounts within your organization.| November 13, 2024  
@@ -100 +100 @@ Change| Description| Date
-[Control access for groups of AWS accounts in AWS Organizations](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-principal-org-paths)| You can now reference organizational units (OUs) from AWS Organizations in IAM policies. If you use Organizations to organize your accounts into OUs, you can require that principals belong to a specific OU before granting access to your resources. Principals include AWS account root user, IAM users and IAM roles. To do this, specify the OU path in the `aws:PrincipalOrgPaths` condition key in your policies.| November 20, 2019  
+[Control access for groups of AWS accounts in AWS Organizations](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-principal-org-paths)| You can now reference organizational units (OUs) from AWS Organizations in IAM policies. If you use AWS Organizations to organize your accounts into OUs, you can require that principals belong to a specific OU before granting access to your resources. Principals include AWS account root user, IAM users and IAM roles. To do this, specify the OU path in the `aws:PrincipalOrgPaths` condition key in your policies.| November 20, 2019  
@@ -105 +105 @@ Change| Description| Date
-[Viewing Organizations service last accessed information in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_last-accessed.html)| You can now view service last accessed information for an AWS Organizations entity or policy in the **AWS Organizations** section of the IAM console. You can also use the AWS CLI or AWS API to retrieve the data report. This data includes information about the allowed services that principals in an Organizations account last attempted to access and when. You can use this information to identify unnecessary permissions so that you can refine your Organizations policies to better adhere to the principle of least privilege.| June 20, 2019  
+[Viewing AWS Organizations service last accessed information in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_last-accessed.html)| You can now view service last accessed information for an AWS Organizations entity or policy in the **AWS Organizations** section of the IAM console. You can also use the AWS CLI or AWS API to retrieve the data report. This data includes information about the allowed services that principals in an AWS Organizations account last attempted to access and when. You can use this information to identify unnecessary permissions so that you can refine your AWS Organizations policies to better adhere to the principle of least privilege.| June 20, 2019