AWS ebs documentation change
Summary
Updated documentation to replace 'Amazon EBS' with 'EBS direct APIs' terminology and added FIPS-compliant VPC endpoint configuration details
Security assessment
The changes introduce documentation for FIPS-compliant VPC endpoints (ebs-fips service name) which enhances security compliance but do not address a specific vulnerability. The updates focus on proper terminology and compliance standards rather than patching a security flaw.
Diff
diff --git a/ebs/latest/userguide/ebs-apis-vpc-endpoints.md b/ebs/latest/userguide/ebs-apis-vpc-endpoints.md index 6f5324387..5143ac408 100644 --- a//ebs/latest/userguide/ebs-apis-vpc-endpoints.md +++ b//ebs/latest/userguide/ebs-apis-vpc-endpoints.md @@ -5 +5 @@ -Considerations for Amazon EBS VPC endpointsCreate an interface VPC endpoint for Amazon EBS +Considerations for EBS direct APIs VPC endpointsCreate an interface VPC endpoint for EBS direct APIs @@ -9 +9 @@ Considerations for Amazon EBS VPC endpointsCreate an interface VPC endpoint for -You can establish a private connection between your VPC and Amazon EBS by creating an _interface VPC endpoint_ , powered by [AWS PrivateLink](https://aws.amazon.com/privatelink/). You can access Amazon EBS as if it were in your VPC, without using an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with Amazon EBS. +You can establish a private connection between your VPC and EBS direct APIs by creating an _interface VPC endpoint_ , powered by [AWS PrivateLink](https://aws.amazon.com/privatelink/). You can access EBS direct APIs as if it were in your VPC, without using an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with EBS direct APIs. @@ -15 +15 @@ For more information, see [Access AWS services through AWS PrivateLink](https:// -## Considerations for Amazon EBS VPC endpoints +## Considerations for EBS direct APIs VPC endpoints @@ -17 +17 @@ For more information, see [Access AWS services through AWS PrivateLink](https:// -Before you set up an interface VPC endpoint for Amazon EBS, review [Considerations](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#considerations-interface-endpoints) in the _AWS PrivateLink Guide_. +Before you set up an interface VPC endpoint for EBS direct APIs, review [Considerations](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#considerations-interface-endpoints) in the _AWS PrivateLink Guide_. @@ -19 +19 @@ Before you set up an interface VPC endpoint for Amazon EBS, review [Consideratio -By default, full access to Amazon EBS is allowed through the endpoint. You can control access to the interface endpoint using VPC endpoint policies. You can attach an endpoint policy to your VPC endpoint that controls access to Amazon EBS. The policy specifies the following information: +By default, full access to EBS direct APIs is allowed through the endpoint. You can control access to the interface endpoint using VPC endpoint policies. You can attach an endpoint policy to your VPC endpoint that controls access to EBS direct APIs. The policy specifies the following information: @@ -32 +32 @@ For more information, see [ Controlling access to services with VPC endpoints](h -The following is an example of an endpoint policy for Amazon EBS. When attached to an endpoint, this policy grants access to all Amazon EBS actions on all resources, except snapshots that are tagged with key `Environment` and value `Test`. +The following is an example of an endpoint policy for EBS direct APIs. When attached to an endpoint, this policy grants access to all EBS direct APIs actions on all resources, except snapshots that are tagged with key `Environment` and value `Test`. @@ -57 +57 @@ The following is an example of an endpoint policy for Amazon EBS. When attached -## Create an interface VPC endpoint for Amazon EBS +## Create an interface VPC endpoint for EBS direct APIs @@ -59 +59 @@ The following is an example of an endpoint policy for Amazon EBS. When attached -You can create a VPC endpoint for Amazon EBS using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [ Create a VPC endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#create-interface-endpoint-aws) in the _AWS PrivateLink Guide_. +You can create a VPC endpoint for EBS direct APIs using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [ Create a VPC endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#create-interface-endpoint-aws) in the _AWS PrivateLink Guide_. @@ -61 +61 @@ You can create a VPC endpoint for Amazon EBS using either the Amazon VPC console -Create a VPC endpoint for Amazon EBS using the following service name: +Create a VPC endpoint for EBS direct APIs using one of the following service names: @@ -64,0 +65 @@ Create a VPC endpoint for Amazon EBS using the following service name: + * `com.amazonaws.`region`.ebs-fips` — To create an interface VPC endpoint that complies with the Federal Information Processing Standard (FIPS) Publication 140-2 US government standard. @@ -65,0 +67 @@ Create a VPC endpoint for Amazon EBS using the following service name: +###### Note @@ -66,0 +69 @@ Create a VPC endpoint for Amazon EBS using the following service name: +FIPS-compliant interface VPC endpoints can be created for the following Regions: `us-east-1` | `us-east-2` | `us-west-1` | `us-west-2` | `ca-central-1` | `ca-west-1`. FIPS-compliant interface VPC endpoints support both IPv4 and IPv6 traffic. @@ -68 +71,4 @@ Create a VPC endpoint for Amazon EBS using the following service name: -If you enable private DNS for the endpoint, you can make API requests to Amazon EBS using its default DNS name for the Region, for example, `ebs.us-east-1.amazonaws.com`. + + + +If you enable private DNS for the endpoint, you can make API requests to EBS direct APIs using its default DNS name for the Region, for example, `ebs.us-east-1.amazonaws.com`.