AWS storagegateway: Add FIPS 140-3 compliance for VPC endpoints
Summary
Updated documentation to specify FIPS 140-3 validation and added a checkbox for FIPS-enabled VPC endpoints.
Security assessment
The change promotes cryptographic compliance by documenting FIPS 140-3 usage for VPC endpoints, enhancing data protection.
Evidence
Similar to publicly accessible endpoints, use the **FIPS enabled endpoint** check box to specify whether the connection must comply with Federal Information Processing Standards (FIPS).
Diff
diff --git a/storagegateway/latest/tgw/create-gateway-vtl.md b/storagegateway/latest/tgw/create-gateway-vtl.md index db2b192ed..af3f9d104 100644 --- a//storagegateway/latest/tgw/create-gateway-vtl.md +++ b//storagegateway/latest/tgw/create-gateway-vtl.md @@ -79 +79 @@ Now that your gateway is set up, you need to choose how you want it to connect a -If you require FIPS 140-2 validated cryptographic modules when accessing AWS through a command line interface or an API, use a FIPS-compliant endpoint. For more information, see [Federal Information Processing Standard (FIPS) 140-2](https://aws.amazon.com/compliance/fips/). +If you require FIPS 140-3 validated cryptographic modules when accessing AWS through a command line interface or an API, use a FIPS-compliant endpoint. For more information, see [Federal Information Processing Standard (FIPS) 140-3](https://aws.amazon.com/compliance/fips/). @@ -83 +83,7 @@ The FIPS service endpoint is only available in some AWS Regions. For more inform - * **VPC hosted** \- Your gateway communicates with AWS through a private connection with your VPC, allowing you to control your network settings. If you select this option, you must specify an existing VPC endpoint by choosing its VPC endpoint ID from the drop-down menu, or by providing its VPC endpoint DNS name or IP address. For more information, see [Activating your gateway in a virtual private cloud](https://docs.aws.amazon.com/storagegateway/latest/tgw/gateway-private-link.html). + * **VPC hosted** \- Your gateway communicates with AWS through a private connection with your VPC, allowing you to control your network settings. If you select this option, you must specify an existing VPC endpoint by choosing its VPC endpoint ID from the drop-down menu, or by providing its VPC endpoint DNS name or IP address. Similar to publicly accessible endpoints, use the **FIPS enabled endpoint** check box to specify whether the connection must comply with Federal Information Processing Standards (FIPS). For more information, see [Activating your gateway in a virtual private cloud](https://docs.aws.amazon.com/storagegateway/latest/tgw/gateway-private-link.html). + +###### Note + +If you require FIPS 140-3 validated cryptographic modules when accessing AWS through a VPC endpoint, use a FIPS-compliant VPC endpoint. For more information, see [Federal Information Processing Standard (FIPS) 140-3](https://aws.amazon.com/compliance/fips/). + +The FIPS service endpoint is only available in some AWS Regions. For more information, see [Storage Gateway endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/sg.html) in the _AWS General Reference_.