A security administrator wants to automate the implementation of network-based ACLs for services deployed within the company VPC. The security administrator is mostly concerned with intra-VPN…

Including firewall rules in an orchestration script targets traditional firewall infrastructure rather than the cloud-native ACL mechanisms designed to govern communication between services inside a VPC.

Deploying anti-malware services via the cloud API addresses host-based threats and malicious software, not the network-layer access controls required to segment services within a VPC.

Cloud provider portals expose native security rule engines - such as security groups and network ACLs - that operate at the VPC level to control traffic between deployed services. Configuring these rules through the portal directly targets intra-VPC lateral traffic, enforcing separation between cloud-deployed services without requiring custom infrastructure or scripts that could introduce errors or drift from the cloud's built-in policy enforcement.

Writing scripts to deploy a network ACL between the VPC and the company's network addresses the perimeter boundary of the VPC, not the intra-VPC separation between cloud-deployed services.