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

Cannot treat Security Group egress in the same way as we do with ingress #164

Open
vale21 opened this issue Apr 24, 2023 · 0 comments · May be fixed by #165
Open

Cannot treat Security Group egress in the same way as we do with ingress #164

vale21 opened this issue Apr 24, 2023 · 0 comments · May be fixed by #165
Labels
bug 🐛 An issue with the system

Comments

@vale21
Copy link

vale21 commented Apr 24, 2023

Describe the Bug

When configuring security group ingress I can specify either a list of CIDR blocks, or an additional security group.
With egress, instead, I can only either disable it or have it fully open (any port, any protocol, 0.0.0.0/0)

Expected Behavior

Being able to specify CIDR and security groups for egress as well

Steps to Reproduce

N/A

Screenshots

No response

Environment

No response

Additional Context

No response
@vale21 vale21 added the bug 🐛 An issue with the system label Apr 24, 2023
@vale21 vale21 linked a pull request Apr 24, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug 🐛 An issue with the system
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Supporting more rules for egress vale21/terraform-aws-rds-cluster
1 participant
@vale21