VPC

Last updated: Nov 3, 2026

Rationale

Fluid Attacks uses AWS VPC (Virtual Private Cloud) to host its private network in the cloud. With it, Fluid Attacks manages network configurations, for example, subnets, IP addressing, Internet gateways, Routing tables, and Security groups.

These are the primary reasons why Fluid Attacks selected it:

It is a core AWS service. Other AWS services that use networking require VPC.
It integrates with services that use networking infrastructure, for example, EC2 and Elastic Load Balancing.
It complies with many certifications from ISO and CSA. Many of these certifications are about the best practices that the entity must use for secure cloud-based environments and information security.
It supports Subnets. With subnets, Fluid Attacks can have more than one network segment, each in a different availability zone. This gives network redundancy.
It supports Security groups with inbound and outbound rules for network interfaces. These rules can use other security groups, IP segments, and communication protocols.
It supports Internet gateways that give NAT to machines with Internet access.
It supports NAT gateways. Thus, the Lambda functions in the VPC, which do not have public IP addresses, have Internet access. The other machines use the Internet gateways.
It supports Routing tables. Thus, Fluid Attacks can customize the routing in the network.
It supports DHCP. Thus, new machines get private IP addresses easily as they are created.
Fluid Attacks can write its resources as code with Terraform.

Google Virtual Private Cloud (VPC): Its approach to networking is more similar to SaaS. Network configuration is easier, but it has fewer parameters.
Azure Virtual Network: It did not exist when Fluid Attacks moved to the cloud. Its review is pending.

Fluid Attacks uses VPC to set the networking and security configurations of these resources: