-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
Currently, ccoctl creates a public S3 bucket to host OIDC endpoint that is accessible over the internet. Many customers have complained about this approach as their security policies do not allow creation of public S3 bucket. We have explored the option of making S3 bucket private and having public CloudFront URL to access OIDC configuration files in S3. We already have this tested and documented by SPLAT team. As part of this card, we need to transfer the content to CCO repo.
SPLAT document : https://drive.google.com/file/d/1z16Gi11Bt4ox-55YuRnvLSm65N9hV8a1/view
CCO document have content needs to be added: https://github.com/openshift/cloud-credential-operator/blob/master/docs/sts.md
- documents
-
RFE-2898 OCP on AWS with manual STS requires private S3 bucket to host OIDC endpoint
- Accepted
- is related to
-
RFE-3614 Define custom domain in CloudFront to host OIDC public URL
- Under Review
- relates to
-
CCO-219 Explore the option of creating private S3 bucket to host OIDC endpoint
- Closed
-
CCO-281 AWS STS Implement procedure for migrating from a public s3 bucket OIDC to a private s3 bucket OIDC with CloudFront Distribution
- To Do
- links to