Warning
You're browsing the documentation for an old version of Webiny. Consider upgrading your project to Webiny 5.35.x.
What you’ll learn
  • how the necessary cloud infrastructure resources are deployed in the development mode

Diagram
anchor

Webiny Cloud Infrastructure - Modes - Development ModeWebiny Cloud Infrastructure - Modes - Development Mode
(click to enlarge)

Description
anchor

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 external link before going through this section.

You can also check this Understanding the Default Virtual Private Cloud external link 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 c d e that span across three availability zones (AZs). All of these subnets are public subnets, since they can both receive and send network traffic to the public internet. When it comes to availability zones, note that the number of zones may vary, depending on the region you’re deploying into (some regions only have two).

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 h, which is only deployed in a single AZ C.

The Amazon ElasticSearch Service is only deployed with the Amazon DynamoDB + Amazon ElasticSearch Service setup.

For more information, visit the Different Setups sections.
Development mode is a reasonable choice when it comes to development environments. But, for production, since some of the cloud infrastructure resources may require that they are not exposed to the public internet, the production may be a better solution.

FAQ
anchor

Is Amazon ElasticSearch Service Deployed Into Multiple AZs?
anchor

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 external link for more information.