DEV Community: Sibi S

Creating 3-Tier Architecture Using AWS

Sibi S — Fri, 24 Jan 2025 05:59:52 +0000

This diagram represents a typical three-tier architecture implemented in AWS. It includes the Web Tier, App Tier, and Database Tier, each with various AWS services. Let me break down the components:

VPC (Virtual Private Cloud) The entire architecture is hosted in a VPC, which provides an isolated network environment.
Subnets Public Subnets (Web Tier): These subnets are accessible from the internet and host the web servers. Private Subnets (App Tier and Database Tier): These are not directly accessible from the internet, providing added security for the application and database layers.
Internet Gateway Connects the VPC to the internet, allowing resources in the public subnet to send/receive traffic.
Elastic Load Balancer (ELB) Distributes incoming traffic across multiple Amazon EC2 instances in the Web Tier, ensuring high availability and fault tolerance.
Amazon EC2 Instances Web Tier (Public Subnet): Hosts web servers that handle incoming HTTP/HTTPS requests from users. App Tier (Private Subnet): Hosts application servers where the core business logic and API processing happen.
Amazon Aurora (Database Tier) Aurora Primary DB: A managed relational database service optimized for performance and availability. Aurora Read Replica: Used for load balancing read-heavy database workloads, improving performance and scalability.
Security Communication between tiers occurs over private subnets, enhancing security. The use of private subnets ensures that sensitive resources (like databases) are not exposed to the internet.
Multi-AZ Deployment The architecture is deployed across two Availability Zones (AZ1 and AZ2) for high availability and disaster recovery.

Flow of Traffic:

Internet Gateway allows traffic to the public subnet.
Elastic Load Balancer routes requests to web servers in the Web Tier.
Web servers in the Web Tier communicate with application servers in the App Tier (private subnets).
Application servers interact with the Aurora Database in the Database Tier for data storage/retrieval.
This design ensures scalability, fault tolerance, and security, adhering to AWS best practices for a three-tier architecture.

PART - 0
Step 1: Create S3 bucket
Step 2: Create IAM User
Give permission for AmazonS3ReadOnlyAccess, AmazonSSMManagedInstanceCore to the IAM role

EC2+S3+IAM

Sibi S — Thu, 23 Jan 2025 10:51:36 +0000

Step 1: Create a EC2 instance

Step 2: Create a key pair

Step 3: Verify the instance in running state or not

Step 4: Edit the inbound rule in the security group of the instance
Assign your ip address by searching in website: https://whatismyipaddress.com/

Step 5: Check the modified inbound rule

Step 6: Install PuTTY from the website: https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

Step 7: Open ec2 instance in puTTy

Step 8: Create a file in ec2 instance

Step 8: Create a role for IAM for allowing S3 full access
Give permission for S3 full access

Give entity type and use case

Give role detail

Step 9: Upload the file to instance

Step 10: Delete and terminate the instance and IAM role

React Application Hosting Using S3 and CloudFront

Sibi S — Thu, 23 Jan 2025 10:17:51 +0000

Step 1: Download node.js from official website https://nodejs.org/en

Step 2: Open command prompt and check the versions
Using this command
node -v
npm -v

Step 3: Create a simple react application

Step 4: Create S3 bucket
In properties, enable static web hosting
In permission, Edit bucket policy
Bucket policy
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "PublicReadGetObject",
"Effect": "Allow",
"Principal": "",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::1214214-sibibucket/"
}
]
}

Step 5: Upload files and folders

Step 6: Click the index file to see the output

Step 7: Access S3 using cloudfront for deploying cloudfront

Step 8: Delete S3 and CloudFront