AWS Key Management Service now supports FIPS 140-2 enabled interface VPC endpoint
Starting today, AWS Key Management Service (AWS KMS) lets you add a VPC endpoint using AWS PrivateLink that connects through the AWS KMS Regional endpoint that has been validated under the Federal Information Processing Standard (FIPS) 140-2 program. With this new launch, you can easily use AWS PrivateLink with AWS KMS for those regulated workloads that require a secure connection using a FIPS 140-2 validated cryptographic module.
Starting today, AWS Key Management Service (AWS KMS) lets you add a VPC endpoint using AWS PrivateLink that connects through the AWS KMS Regional endpoint that has been validated under the Federal Information Processing Standard (FIPS) 140-2 program. With this new launch, you can easily use AWS PrivateLink with AWS KMS for those regulated workloads that require a secure connection using a FIPS 140-2 validated cryptographic module.
To create an interface VPC endpoint that connects to an AWS KMS FIPS endpoint, see creating a VPC endpoint for AWS KMS the AWS KMS Developer Guide.
This new capability is available in all AWS Regions, including the AWS GovCloud (US) Regions. To learn more about AWS PrivateLink, see accessing AWS services through AWS PrivateLink. To learn more about FIPS 140-2 at AWS, visit FIPS 140-2 Compliance.