Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ECR FIPS Compliance #2

Closed
abby-fuller opened this issue Nov 28, 2018 · 5 comments
Closed

ECR FIPS Compliance #2

abby-fuller opened this issue Nov 28, 2018 · 5 comments
Labels
ECR Amazon Elastic Container Registry
Projects
containers-roadmap

Comments

@abby-fuller
Copy link
Contributor

Use FIPS compliant software to terminate TLS. If we don't do this, then we should expect limited adoption in GovCloud regions.
@abby-fuller abby-fuller created this issue from a note in containers-roadmap (We're Working On It) Nov 28, 2018
@abby-fuller abby-fuller added the ECR Amazon Elastic Container Registry label Nov 28, 2018
@abby-fuller abby-fuller moved this from We're Working On It to Coming Soon in containers-roadmap Nov 28, 2018
@colmmacc
Copy link
Contributor

Just a note to say that we have FIPS support in Amazon s2n (https://github.com/awslabs/s2n).

@paavan98pm
Copy link

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.

@geekdave geekdave mentioned this issue Jan 14, 2019
Closed
@qthuy qthuy mentioned this issue May 9, 2019
Closed
@coultn coultn mentioned this issue Jun 29, 2019
Closed
@wico wico mentioned this issue Jul 2, 2019
Closed
@willfarrell
Copy link

Would be awesome if this was rolled out to Canada as well.

@jtoberon
Copy link

jtoberon commented Sep 27, 2019 •
edited
Loading

ecr-fips.us-east-1.amazonaws.com
ecr-fips.us-east-2.amazonaws.com
ecr-fips.us-west-1.amazonaws.com
ecr-fips.us-west-2.amazonaws.com
ecr-fips.us-gov-east-1.amazonaws.com
ecr-fips.us-gov-west-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.

@jtoberon
Copy link

Created #501

@jtoberon jtoberon moved this from Coming Soon to Just Shipped in containers-roadmap Oct 1, 2019
@ezra-freedman ezra-freedman mentioned this issue Dec 17, 2019
Closed
@ghost ghost mentioned this issue Jul 30, 2020
Open
@dahu33 dahu33 mentioned this issue Oct 29, 2020
Open
@AletaMP AletaMP mentioned this issue Nov 10, 2020
Open
@mreferre mreferre mentioned this issue Apr 20, 2022
Open
@PettitWesley PettitWesley mentioned this issue Aug 17, 2022
Open
@ellistarn ellistarn mentioned this issue Feb 28, 2023
Open
@kshivaz kshivaz mentioned this issue May 16, 2024
Open
@tdalbo92 tdalbo92 mentioned this issue May 21, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ECR Amazon Elastic Container Registry
Projects
containers-roadmap
  
Shipped
Milestone
No milestone
Development

No branches or pull requests
5 participants
@colmmacc @jtoberon @willfarrell @abby-fuller @paavan98pm