- how the necessary cloud infrastructure resources are deployed in the development mode
Virtual Private Clouds (VPCs) is a topic that requires some general networking knowledge and knowledge on AWS-specific concepts like regions, availability zones, different network gateways, and so on. Be sure to read about it before going through this section.
You can also check this Understanding the Default Virtual Private Cloud article. It clearly lays out a lot of useful information about AWS’s default VPC setup.
In development mode, your project is deployed into the default Virtual Private Cloud (VPC), which is automatically created for every AWS Account.In the diagram above, we can see that the default VPC setup consists of three subnets
We can also see that AWS Lambda functions are located in all three subnets. This is because, by default, AWS runs AWS Lambda functions in multiple AZs to ensure it is highly available in case of an AZ failure. The same cannot be said for the Amazon ElasticSearch Service
The Amazon ElasticSearch Service is only deployed with the Amazon DynamoDB + Amazon ElasticSearch Service setup.For more information, visit the Different Setups sections.
In the development mode, it is deployed into a single AZ, just for cost reasons. But yes, production workloads should use two or three AZs, hence the production mode. Check out the Amazon ElasticSearch Service’s FAQ page for more information.