This is the simplest of the setups, where a VPC is created with a single public subnet along with an internet gateway that is configured to allow communication to the external networks or the internet. This scenario is ideal for simple applications such as a public facing website or a blog hosted on a standalone instance.   

The following diagram illustrates this configuration:

The previous setup provides a VPC with 65,536 usable private IP addresses (CIDR: 10.0.0.0/ 16) along with a subnet that provides 256 usable IP addresses (10.0.0.0/24).  An internet gateway is also attached to the VPC, which connects the instances of the VPC to the external networks, that is, the internet or other AWS products such as S3 storage and so on. The instance running the VPC is provided with a private IP address in the subnet range, that is, 10.0.0.2, which enables the instance to communicate with other instances in the VPC. An Elastic IP address is also assigned to the instance so that it is accessible from the external networks or the internet. 

A routing table should be configured to allow the instances within the VPC to be able to communicate with each other and also the external networks, that is, the internet. As discussed in the previous section, this scenario can also be configured with a NAT instance.