-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Security Groups do not allow ICMP #1313
Comments
I think I just sorted this out. As it happens, Amazon uses the same interface for CloudFormation and there is some documentation on how to use ICMP. The Here's an example of how to allow inbound echo requests:
|
That's... disappointing to hear... Network ACLs have an explicit Sounds like the solution for this issue then is to document this on the Security Group and Security Group Rules docs, agreed? |
@catsby I discovered after this that the Network ACL rules break when attempting to use this because of exactly what you're saying about the To be clear, ICMP works fine when creating Security Group Rules if you do what I described before, but not in Network ACL in terraform v0.51.0 (and presumably lower). This does appear to mirror the AWS API for Security Group Rules. |
For those out there who want to allow incoming ICMP echo ("ping") from any source via a security group, this does the trick:
|
The documentation has been updated to reflect ICMP. I am going to close this issue. If you feel that the documentation is not as clear as it can be, please let us know Thanks Paul |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
I was trying to create a security group with the following configuration:
and I get the following error:
While I understand why this error is happening, ICMP doesn't really have a port and if you try to specify one you get this error from amazon:
Is there a specific way to configure ICMP? From looking at resource_aws_security_group.go it didn't look that way so this may be a feature request, maybe a rule type or something so that way we could accomplish the ability to do "all tcp" or whatever without having to specify ports.
The text was updated successfully, but these errors were encountered: