By default, which type of VPC does AWS create?

When AWS creates a Virtual Private Cloud (VPC) by default, it provisions a public VPC. This means that the VPC includes a public subnet that is equipped with an internet gateway, allowing instances launched in this public subnet to access the internet directly. This setup is convenient for use cases where resources need internet exposure, such as web servers or applications that need to be publicly accessible.

In a public VPC, resources such as Amazon EC2 instances can communicate with the internet without requiring additional configuration. This foundational design enables users to start deploying applications quickly without having to set up complex networking environments from scratch.

Other types of VPC configurations, such as private VPCs, hybrid VPCs, or custom VPCs, involve additional configurations or specific design choices made by users to accommodate their particular networking requirements. Private VPCs would not allow direct internet access from instances by default, while hybrid VPCs involve integrations with on-premises resources. Custom VPCs require defined subnets and settings to meet specific needs. Hence, these options do not reflect the default configuration provided by AWS.