AWS directoryservice documentation change
Summary
Updated documentation to remove 'AWS' prefix from 'Directory Service' and 'Directory Service Data' references throughout the text. No functional changes to the VPC interface endpoint setup process.
Security assessment
The changes are purely branding/terminology updates (removing redundant 'AWS' prefixes) and do not introduce new security controls, address vulnerabilities, or modify security recommendations. The content still describes the same security feature (PrivateLink integration) without altering its implementation or security implications.
Diff
diff --git a/directoryservice/latest/admin-guide/vpc-interface-endpoints.md b/directoryservice/latest/admin-guide/vpc-interface-endpoints.md index 3b8a2a9af..33c3b3393 100644 --- a//directoryservice/latest/admin-guide/vpc-interface-endpoints.md +++ b//directoryservice/latest/admin-guide/vpc-interface-endpoints.md @@ -7 +7 @@ ConsiderationsAvailabilityCreate an interface Amazon VPC endpointCreate an endpo -# AWS Directory Service API and interface Amazon VPC endpoints using AWS PrivateLink +# Directory Service API and interface Amazon VPC endpoints using AWS PrivateLink @@ -9 +9 @@ ConsiderationsAvailabilityCreate an interface Amazon VPC endpointCreate an endpo -You can use AWS PrivateLink to create a private connection between your VPC and AWS Directory Service and Directory Service Data APIs. This allows you to access AWS Directory Service and Directory Service Data APIs like they were in your VPC and without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your Amazon VPC don't require public IP addresses to access AWS Directory Service and Directory Service Data APIs. +You can use AWS PrivateLink to create a private connection between your VPC and Directory Service and Directory Service Data APIs. This allows you to access Directory Service and Directory Service Data APIs like they were in your VPC and without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your Amazon VPC don't require public IP addresses to access Directory Service and Directory Service Data APIs. @@ -15 +15 @@ For more information, see [Access AWS services through AWS PrivateLink](https:// -## Considerations for AWS Directory Service and Directory Service Data +## Considerations for Directory Service and Directory Service Data @@ -17 +17 @@ For more information, see [Access AWS services through AWS PrivateLink](https:// -With AWS Directory Service and Directory Service Data, you can call API actions through interface endpoints. For information about the prerequisites you will need to consider before creating an interface endpoint, see [Access an AWS service using an interface Amazon VPC endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#considerations-interface-endpoints) in the _AWS PrivateLink Guide_. +With Directory Service and Directory Service Data, you can call API actions through interface endpoints. For information about the prerequisites you will need to consider before creating an interface endpoint, see [Access an AWS service using an interface Amazon VPC endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#considerations-interface-endpoints) in the _AWS PrivateLink Guide_. @@ -19 +19 @@ With AWS Directory Service and Directory Service Data, you can call API actions -## AWS Directory Service and Directory Service Data Availability +## Directory Service and Directory Service Data Availability @@ -21 +21 @@ With AWS Directory Service and Directory Service Data, you can call API actions -AWS Directory Service and Directory Service Data supports interface endpoints in all AWS Regions where it's available. For information about the AWS Regions that support AWS Directory Service and Directory Service Data, see [Region availability for AWS Directory Service](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/regions.html). +Directory Service and Directory Service Data supports interface endpoints in all AWS Regions where it's available. For information about the AWS Regions that support Directory Service and Directory Service Data, see [Region availability for Directory Service](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/regions.html). @@ -23 +23 @@ AWS Directory Service and Directory Service Data supports interface endpoints in -## Create an interface Amazon VPC endpoint for AWS Directory Service and Directory Service Data +## Create an interface Amazon VPC endpoint for Directory Service and Directory Service Data @@ -25 +25 @@ AWS Directory Service and Directory Service Data supports interface endpoints in -You can create an interface endpoint for AWS Directory Service and Directory Service Data APIs using the Amazon VPC console or the AWS Command Line Interface (AWS CLI). +You can create an interface endpoint for Directory Service and Directory Service Data APIs using the Amazon VPC console or the AWS Command Line Interface (AWS CLI). @@ -27 +27 @@ You can create an interface endpoint for AWS Directory Service and Directory Ser -###### Example: AWS Directory Service +###### Example: Directory Service @@ -29 +29 @@ You can create an interface endpoint for AWS Directory Service and Directory Ser -Create an interface endpoint for AWS Directory Service APIs using the following service name: +Create an interface endpoint for Directory Service APIs using the following service name: @@ -66 +66 @@ You can control access to APIs from your Amazon VPC by attaching a custom endpoi -###### Example: Amazon VPC endpoint policy for AWS Directory Service API actions +###### Example: Amazon VPC endpoint policy for Directory Service API actions @@ -68 +68 @@ You can control access to APIs from your Amazon VPC by attaching a custom endpoi -The following is an example of a custom endpoint policy. When you attach this policy to your interface endpoint, it grants access to the listed AWS Directory Service actions for all principals on all resources. +The following is an example of a custom endpoint policy. When you attach this policy to your interface endpoint, it grants access to the listed Directory Service actions for all principals on all resources. @@ -70 +70 @@ The following is an example of a custom endpoint policy. When you attach this po -Replace `action-1`, `action-2`, and `action-3` with the required permissions for the AWS Directory Service APIs that you want to include in your policy. For a full list, see [AWS Directory Service API permissions: Actions, resources, and conditions reference](./UsingWithDS_IAM_ResourcePermissions.html). +Replace `action-1`, `action-2`, and `action-3` with the required permissions for the Directory Service APIs that you want to include in your policy. For a full list, see [Directory Service API permissions: Actions, resources, and conditions reference](./UsingWithDS_IAM_ResourcePermissions.html). @@ -92 +92 @@ The following is an example of a custom endpoint policy. When you attach this po -Replace `action-1`, `action-2`, and `action-3` with the required permissions for the Directory Service Data APIs that you want to include in your policy. For a full list, see [AWS Directory Service API permissions: Actions, resources, and conditions reference](./UsingWithDS_IAM_ResourcePermissions.html). +Replace `action-1`, `action-2`, and `action-3` with the required permissions for the Directory Service Data APIs that you want to include in your policy. For a full list, see [Directory Service API permissions: Actions, resources, and conditions reference](./UsingWithDS_IAM_ResourcePermissions.html).