AWS Security ChangesHomeSearch

AWS organizations documentation change

Service: organizations · 2026-06-28 · Documentation low

File: organizations/latest/userguide/create-vpc-endpoint.md

Summary

Updated VPC endpoint service name syntax to use region placeholders instead of hardcoded us-east-1 values.

Security assessment

General documentation improvement for regional endpoint configuration. No security vulnerabilities or security features are mentioned in the changes.

Diff

diff --git a/organizations/latest/userguide/create-vpc-endpoint.md b/organizations/latest/userguide/create-vpc-endpoint.md
index 40c0ff99f..a85aad3cb 100644
--- a//organizations/latest/userguide/create-vpc-endpoint.md
+++ b//organizations/latest/userguide/create-vpc-endpoint.md
@@ -13 +13 @@ For information about creating and configuring an endpoint using the Amazon VPC
-When you create an AWS Organizations endpoint, use the following as the service name:
+When you create an AWS Organizations endpoint, use the following service name, replacing `region` with the Region that you are connecting from:
@@ -16 +16 @@ When you create an AWS Organizations endpoint, use the following as the service
-    com.amazonaws.us-east-1.organizations
+    com.amazonaws.region.organizations
@@ -21 +21 @@ If you require FIPS 140-2 validated cryptographic modules when accessing AWS, us
-    com.amazonaws.us-east-1.organizations-fips
+    com.amazonaws.region.organizations-fips