AWS IAM: Fix documentation links for security features
Summary
Corrected URLs for data perimeters and SAML encryption documentation.
Security assessment
The update fixes broken links to existing security documentation but does not introduce new security content.
Evidence
+[VPC endpoint condition keys for network perimeter controls](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html)| IAM now supports three new AWS global condition context keys for implementing scalable network perimeter controls: `aws:VpceAccount`, `aws:VpceOrgID`, and `aws:VpceOrgPaths`. These keys help ensure requests come through VPC endpoints owned by specific accounts, organizations, or organizational units, automatically scaling with your VPC endpoint usage without requiring policy updates when you create new endpoints. For more information, see [Establish permissions guardrails using data perimeters](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_data-perimeters.html).| August 28, 2025
Diff
diff --git a/IAM/latest/UserGuide/document-history.md b/IAM/latest/UserGuide/document-history.md index c5cba3ce7..9f2b61f56 100644 --- a//IAM/latest/UserGuide/document-history.md +++ b//IAM/latest/UserGuide/document-history.md @@ -20 +20 @@ Change| Description| Date -[VPC endpoint condition keys for network perimeter controls](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html)| IAM now supports three new AWS global condition context keys for implementing scalable network perimeter controls: `aws:VpceAccount`, `aws:VpceOrgID`, and `aws:VpceOrgPaths`. These keys help ensure requests come through VPC endpoints owned by specific accounts, organizations, or organizational units, automatically scaling with your VPC endpoint usage without requiring policy updates when you create new endpoints. For more information, see [Establish permissions guardrails using data perimeters](https://docs.aws.amazon.com//IAM/latest/UserGuide/access_policies_data-perimeters.html).| August 28, 2025 +[VPC endpoint condition keys for network perimeter controls](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html)| IAM now supports three new AWS global condition context keys for implementing scalable network perimeter controls: `aws:VpceAccount`, `aws:VpceOrgID`, and `aws:VpceOrgPaths`. These keys help ensure requests come through VPC endpoints owned by specific accounts, organizations, or organizational units, automatically scaling with your VPC endpoint usage without requiring policy updates when you create new endpoints. For more information, see [Establish permissions guardrails using data perimeters](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_data-perimeters.html).| August 28, 2025 @@ -57 +57 @@ Change| Description| Date -[Encryption support for SAML identity providers](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_saml.html#id_federation_manage-saml-encryption)| IAM SAML providers now support encrypted assertions in the SAML response from your external IdP. To understand how encryption works with IAM SAML federation, see [Using SAML-based federation for API access](https://docs.aws.amazon.com//IAM/latest/UserGuide/id_roles_providers_saml.html#CreatingSAML-configuring).| February 4, 2024 +[Encryption support for SAML identity providers](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_saml.html#id_federation_manage-saml-encryption)| IAM SAML providers now support encrypted assertions in the SAML response from your external IdP. To understand how encryption works with IAM SAML federation, see [Using SAML-based federation for API access](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_saml.html#CreatingSAML-configuring).| February 4, 2024