Skip to content

Commit 9582a1a

Browse files
Readme updates
1 parent 6181397 commit 9582a1a

File tree

1 file changed

+27
-3
lines changed

1 file changed

+27
-3
lines changed

README.md

Lines changed: 27 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,11 @@ Terraform AWS VPC Module by Source4Learn(An Opensource Community to learn and sh
33
![Source4Learn](https://github.com/opensource4learn/terraform-aws-vpc/blob/main/s4l.png?raw=true)
44

55
## AWS VPC Module
6-
This AWS VPC Module will create following resources:
7-
- Subnets ["Public", "Private", "Storage"]
8-
- Route Tables ["Public", "Private", "Storage"]
6+
This AWS VPC module is designed to implement the common AWS infrastructure patterns such as single or multi-tier. The multi-tier patterns allow users to create infrastructure in separate layers as per the needs of modern applications.
7+
8+
AWS VPC Module will create following resources:
9+
- VPC and Subnets
10+
- Route Tables
911
- Security Gruoups
1012
- Internet Gateway
1113
- NAT Gateway
@@ -31,6 +33,28 @@ module "vpc" {
3133
}
3234
```
3335

36+
# AWS VPC multi-tier architecture
37+
The AWS resources created in the public layers can be accessed publicly(i.e. - frontend servers, load-balancers, bastion instances, etc) but backed resources such as application servers, database, caching servers will remain in private sections. The AWS infrastructure patterns can be categories as follows:
38+
39+
40+
- **Public Layer:** This layer consists of public subnets and has one subnet on each availability zone for high availability.
41+
- **Application Layer:** This layer of AWS infrastructure contains the private subnets and one on each Availability Zone.
42+
- **Database Layer:** The third layer consists of 3 private subnets and the same subnet on each availability zone.
43+
44+
Let's take a brief overview of multi-layers or multi-tier architecture. It basically divides the AWS infrastructure into layers like - Public, Private, and Storage(Isolated database) layers. The reason behind this implementation is to protect and isolate private layers from any unwanted public access. In other words, the Public layer provides a shield to internal layers of architecture.
45+
46+
AWS allows users to create the multi-tier infrastructure and distribute it across the availability zones of the current region to achieve the high availability of resources.
47+
48+
## 3-tier architecture
49+
To split the AWS infrastructure into multiple tiers and availability zones, please refer to below architectural diagram:</br>
50+
**Information yet to be added.
51+
52+
## 2-tier architecture
53+
**Information yet to be added.
54+
55+
## 1-tier architecture
56+
**Information yet to be added.
57+
3458
## Requirements
3559

3660
| Name | Version |

0 commit comments

Comments
 (0)