alibabacloud-cfw-vpc-peering-firewall-protect
Installation
SKILL.md
Operation Routing
Identify the user's intent, then route to the matching execution path:
| User Intent | Execution Path |
|---|---|
| Query VPC firewall list / which peering pairs are protected | vpc-fw-switch.sh query with filters |
| Inspect one firewall (local/peer VPC, ENI, protected route tables) | vpc-fw-switch.sh detail --vpc-firewall-id <id> |
| Which peering pairs are unprotected, and how do I protect them? | vpc-fw-lifecycle.sh assess --region <id> (read-only inventory + blockers) |
| Can THIS peering pair be protected? Give me the enablement plan | vpc-fw-lifecycle.sh assess --local-vpc-id <id> --local-region <id> --peer-vpc-id <id> --peer-region <id> (adds the pre-check + route discovery + a ready-to-run plan) |
| Enable/disable protection for specific VPC firewalls | vpc-fw-switch.sh enable/disable --vpc-firewall-ids "..." (three-phase workflow below) |
| Check whether a peering pair can have a firewall created | vpc-fw-lifecycle.sh precheck |
| Create a VPC firewall for a peering pair | Creation workflow: assess -> vpc-fw-lifecycle.sh create |
| Rename a firewall / adjust the protected route (CIDR) tables | vpc-fw-lifecycle.sh update (built-in verification runs automatically) |
| Read or adjust the IPS defense configuration (defense mode, rule group, basic rules, virtual patching) | vpc-fw-engine.sh ips --vpc-firewall-id <id> - read-only with no write flag; see the Engine Settings workflow |
| Read or adjust the ACL engine mode (strict vs loose) | vpc-fw-engine.sh acl-engine --vpc-firewall-id <id> - read-only without --strict-mode; see the Engine Settings workflow |
| Delete / release a VPC firewall | NOT SUPPORTED - releasing the resource is the user's own action. Offer vpc-fw-switch.sh disable to stop protection, and point to the console (开关 -> VPC边界防火墙 -> 对等连接 -> 删除). vpc-fw-lifecycle.sh delete only prints this guidance plus a read-only impact report |
Key concept: one peering pair (a local VPC + a peer VPC connected by Express Connect or VPC peering) maps to exactly one VPC boundary firewall. The firewall must be created before its switch can be toggled. FirewallSwitchStatus opened means the switch is on (protecting); closed means off; notconfigured means no firewall exists for the pair yet.