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.

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

AWS Security Group created with rules open to the world #643

Open
techietav opened this issue Feb 26, 2024 · 1 comment
Open

AWS Security Group created with rules open to the world #643

techietav opened this issue Feb 26, 2024 · 1 comment

Comments

@techietav
Copy link

When deploying CP4D onto AWS and creating the OpenShift cluster a Security Group is created with 'rules open to the world' This violates the AWS client security enforcement policy and is immediately removed, as well as triggering an email to the account owner informing them of the incident.

Security Groups MUST be created with least privileged principles so only the require ports and hosts are specified.

This requires an immediate fix.

@fketelaars
Copy link
Collaborator

For OpenShift deployments, Cloud Pak Deployer follows the standard steps for IPI installations in the OpenShift documentation.

If the customer has specific guidelines on how security groups must be created, they can create the AWS resources and deploy OpenShift using their own standards. Once created, Cloud Pak Deployer can be used to deploy the Cloud Pak software.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants