Basically: Are SSH/HTTPS values for AWS NACL rule protocol not supported?
I’m deploying an AWS VPC with a NACL, and for this I want to write rules as restrictive as possible, which means locking down both port and protocol. Problem is when I try to Apply the NACL rules with protocol values of SSH/HTTPS I’m getting thrown an error.
Using TCP/-1 works as values and all documentation on these elements I’ve found are using either of TCP/-1, so it looks like no other protocol values are supported, but I wish I could confirm that but nothing is mentioned about such a restriction in the documentation as far as I can see.
Using the AWS Console I can without issue edit the NACLs protocol to SSH or HTTPS, so those values are definitely supported from AWS side.