Build AWS Security Group and Azure NSG firewall rules visually. Add SSH, HTTPS, RDP presets or custom ports. Get CLI, Terraform, and JSON output instantly.
| Description | Protocol | Port From | Port To | IPv4 CIDR | IPv6 CIDR | |
|---|---|---|---|---|---|---|
aws ec2 authorize-security-group-ingress \
--group-id sg-XXXXXXXXXXXXXXXXX \
--ip-permissions '[
{
"IpProtocol": "tcp",
"FromPort": 443,
"ToPort": 443,
"IpRanges": [
{
"CidrIp": "0.0.0.0/0",
"Description": "allow-https"
}
]
},
{
"IpProtocol": "tcp",
"FromPort": 443,
"ToPort": 443,
"Ipv6Ranges": [
{
"CidrIpv6": "::/0",
"Description": "allow-https"
}
]
}
]'
aws ec2 authorize-security-group-ingress \
--group-id sg-XXXXXXXXXXXXXXXXX \
--ip-permissions '[
{
"IpProtocol": "tcp",
"FromPort": 22,
"ToPort": 22,
"IpRanges": [
{
"CidrIp": "0.0.0.0/0",
"Description": "allow-ssh"
}
]
}
]'The Firewall Rule Builder generates AWS Security Group and Azure Network Security Group (NSG) rules from a visual table editor. Security groups and NSGs control inbound and outbound traffic at the instance or subnet level and are the primary network defense layer in both clouds. Getting the rule format right matters: AWS uses a separate IPv4 CidrIp and IPv6 CidrIpv6 field in the same rule, while Azure uses a priority number and separate allow/deny action.
Select your provider (AWS or Azure), choose Inbound or Outbound, then build your rule table using the preset buttons (SSH, HTTPS, RDP) or by entering custom protocol, port, and CIDR values. Each rule accepts separate IPv4 and IPv6 CIDR fields. Switch between the CLI, Terraform, and Raw JSON tabs to get the output format your workflow needs.
AWS CLI output uses the --ip-permissions JSON format, which supports both IPv4 (CidrIp) and IPv6 (CidrIpv6) in the same rule. Azure NSG rules require a numeric priority (100-4096); lower numbers take precedence. Azure rules with both IPv4 and IPv6 CIDRs use the plural source_address_prefixes attribute in Terraform.