-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ECR FIPS Compliance #2
Comments
Just a note to say that we have FIPS support in Amazon s2n (https://github.com/awslabs/s2n). |
Does this refer to running the ECR software (used to terminate TLS) in FIPS-compliant mode? If so, the issue title could be revised. Achieving FIPS compliance for ECR, which the issue title reads as-is, could be misleading to customers as that is an extensive process (independent validation of crypto modules in use within a service) we follow for KMS and CloudHSM. |
Would be awesome if this was rolled out to Canada as well. |
ecr-fips.us-east-1.amazonaws.com Docs (e.g. https://aws.amazon.com/compliance/fips/) are being updated. We will create a separate issue to track the Canada work. |
Created #501 |
Use FIPS compliant software to terminate TLS. If we don't do this, then we should expect limited adoption in GovCloud regions.
The text was updated successfully, but these errors were encountered: