AWS ec2 documentation change
Summary
Added PowerShell V5 example for creating network ACL entry allowing DNS traffic
Security assessment
Demonstrates network ACL configuration but doesn't highlight security implications of open DNS access (0.0.0.0/0)
Diff
diff --git a/ec2/latest/devguide/example_ec2_CreateNetworkAclEntry_section.md b/ec2/latest/devguide/example_ec2_CreateNetworkAclEntry_section.md index 1c69ccf0b..dda8dfccc 100644 --- a//ec2/latest/devguide/example_ec2_CreateNetworkAclEntry_section.md +++ b//ec2/latest/devguide/example_ec2_CreateNetworkAclEntry_section.md @@ -54,0 +55,14 @@ PowerShell +**Tools for PowerShell V5** + + +**Example 1: This example creates an entry for the specified network ACL. The rule allows inbound traffic from anywhere (0.0.0.0/0) on UDP port 53 (DNS) into any associated subnet.** + + + New-EC2NetworkAclEntry -NetworkAclId acl-12345678 -Egress $false -RuleNumber 100 -Protocol 17 -PortRange_From 53 -PortRange_To 53 -CidrBlock 0.0.0.0/0 -RuleAction allow + + + * For API details, see [CreateNetworkAclEntry](https://docs.aws.amazon.com/powershell/v5/reference) in _AWS Tools for PowerShell Cmdlet Reference (V5)_. + + + +