DEV Community: Dharshinisri G

3-Tier Architecture (Part -7)

Dharshinisri G — Mon, 31 Mar 2025 08:24:19 +0000

External Load Balancer and Auto Scaling

Web Tier AMI
Target Group
Internet Facing Load Balancer
Launch Template
Auto Scaling
Conclusion

Web Tier AMI

Navigate to Instances on the left-hand side of the EC2 dashboard.
Select the web tier instance we created and under Actions, select Image and templates.
Click Create Image.
Provide a name and description for the image and then click Create image.
To monitor the status of the image creation, navigate to AMIs under Images on the left-hand panel of the EC2 dashboard.

Target Group

While the AMI is being created, let's set up our target group for the load balancer:

Navigate to Target Groups under Load Balancing in the EC2 dashboard.
Click Create Target Group.
Select Instances as the target type and provide a name.
Set the protocol to HTTP and port to 80 (as NGINX listens on this port).
Choose the VPC we've been using.
Change the health check path to /health.
Click Next.
Skip registering targets for now and create the target group.

Internet Facing Load Balancer

Navigate to Load Balancers under Load Balancing in the EC2 dashboard.
Click Create Load Balancer.
Select Application Load Balancer.
Provide a name and select Internet Facing.
Choose the correct network configuration for VPC and public subnets.
Select the security group created for this ALB.
Ensure that the ALB listens for HTTP traffic on port 80.
Set it to forward traffic to the target group created earlier.
Click Create Load Balancer.

Launch Template

Before configuring Auto Scaling, create a Launch Template:

Navigate to Launch Templates under Instances in the EC2 dashboard.
Click Create Launch Template.
Provide a name for the template.
Under Application and OS Images, select the AMI created earlier.
Choose t2.micro as the instance type.
Skip Key pair and Network Settings (we’ll configure these in Auto Scaling).
Select the correct security group for the web tier.
Under Advanced details, use the same IAM instance profile used for our EC2 instances.
Click Create Launch Template.

Auto Scaling

Now, we create the Auto Scaling Group:

Navigate to Auto Scaling Groups under Auto Scaling in the EC2 dashboard.
Click Create Auto Scaling Group.
Provide a name for the Auto Scaling group.
Select the Launch Template created earlier and click Next.
Choose the VPC and public subnets for the web tier.
Attach the Auto Scaling Group to the Load Balancer by selecting the existing web tier load balancer’s target group.
Click Next.
Set desired, minimum, and maximum capacity to 2.
Click Skip to review, then Create Auto Scaling Group.
After the above step, click Next, Next, and finally, Create Auto Scaling Group.

Now, our WebApp is successfully set up! 🎉

Conclusion

Congratulations on successfully implementing a three-tier architecture on AWS! This was a significant journey from Part 1 to Part 7, and you’ve gained essential skills in AWS infrastructure setup.

Before wrapping up, ensure that all services used for learning purposes are properly cleaned up to avoid unnecessary costs.

Thank You!

I hope you found this series informative and helpful. 🚀

3-Tier Architecture (Part-4)

Dharshinisri G — Mon, 31 Mar 2025 07:55:07 +0000

AWS Three-Tier Architecture: App Instance Deployment

App Instance Deployment
Connect to Instance
Configure Database
Configure App Instance
Test App Tier
Conclusion

App Instance Deployment

Navigate to the EC2 service dashboard and click on Instances on the left-hand side.
Click Launch Instances.

Select the Amazon Linux 2 AMI.

Choose t2.micro (Free Tier Eligible) and click Next: Configure Instance Details.
Proceed without key-pair since we will use EC2-instance login.
Configure the instance details:
- Select the correct Network (VPC) and Private Subnet (AZ-1).

Attach the IAM role created earlier.
Use the private instance security group created before.

Click Launch Instance.

Connect to Instance

Navigate to the Instances list in the EC2 dashboard.
Once the instance state is running, select it and click Connect.
Go to the Session Manager tab and click Connect (Opens a new browser tab).

Note: If you cannot connect via Session Manager, ensure:

Your instance can route to NAT Gateway.

The IAM role has the necessary permissions.

Once connected, switch to ec2-user:

   sudo -su ec2-user

Check if the instance can access the internet:

   ping 8.8.8.8

If you cannot reach the internet, check Route Tables and Subnet Associations for NAT Gateway routing.

Configure Database

Install MySQL CLI

sudo yum install mysql -y

If the above fails, try:

sudo wget https://dev.mysql.com/get/mysql57-community-release-e17-11.noarch.rpm
sudo rpm --import https://repo.mysql.com/RPM-GPG-KEY-mysql-2022
sudo yum install https://dev.mysql.com/get/mysql57-community-release-e17-11.noarch.rpm

Connect to RDS Database

mysql -h YOUR-RDS-ENDPOINT -u YOUR-USERNAME -p

Enter your password when prompted.

Create a Database and Table

CREATE DATABASE webappdb;
SHOW DATABASES;
USE webappdb;

CREATE TABLE IF NOT EXISTS transactions (
    id INT NOT NULL AUTO_INCREMENT,
    amount DECIMAL(10,2),
    description VARCHAR(100),
    PRIMARY KEY(id)
);

SHOW TABLES;

Insert Test Data

INSERT INTO transactions (amount, description) VALUES ('400', 'groceries');
SELECT * FROM transactions;

Exit MySQL:

exit

Configure App Instance

Update Database Credentials

Open application-code/app-tier/DbConfig.js.
Update the hostname, user, password, and database.
Save the file.

Upload App Code to S3

Upload the app-tier folder to the S3 bucket created earlier.

Install Node.js and Dependencies

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
source ~/.bashrc
nvm install 16
nvm use 16
npm install -g pm2

Download and Run App

cd ~/
aws s3 cp s3://BUCKET_NAME/app-tier/ app-tier --recursive
cd ~/app-tier
npm install
pm2 start index.js

Check if App is Running

pm2 list

If the status is errored, check logs:

pm2 logs

Enable Auto-Start for PM2

pm2 startup

Copy the exact command from the output and run it.

Save the PM2 process list:

pm2 save

Test App Tier

Health Check Endpoint

curl http://localhost:4000/health

Expected response:

"This is the health check"

Database Connection Test

curl http://localhost:4000/transaction

Expected response:

{"result":[{"id":1,"amount":400,"description":"groceries"}]}

If both tests pass, the app layer is configured correctly.

Conclusion

This completes the App Tier setup for our AWS Three-Tier Architecture.

➡️ Proceed to Part 5 to continue the implementation:

Continue to the next Part AWS Three-Tier Architecture (Part-5)

3-Tier Architecture (Part-1)

Dharshinisri G — Mon, 31 Mar 2025 03:36:52 +0000

AWS Three-Tier Architecture Setup

📥 Clone the GitHub Repository

To begin, clone the GitHub repository that contains the necessary code:

git clone https://github.com/Naveen3251/AWS_3Tier.git

Architecture

☁️ S3 Bucket Creation

Navigate to the S3 service in the AWS Management Console.
Click on Create Bucket.
Enter a unique Bucket Name.
Select the AWS Region where you will be deploying the architecture.
Keep the default settings and click Create Bucket. This bucket will be used to store and manage the application code.

🔑 IAM Role for EC2 Instances

Open the IAM service in the AWS Management Console.
Navigate to Roles and click Create Role.
Choose EC2 as the Trusted Entity.
Click Next: Permissions and attach the following AWS Managed Policies:
- AmazonSSMManagedInstanceCore → Allows secure connection through AWS Systems Manager Session Manager.
- AmazonS3ReadOnlyAccess → Grants EC2 instances permission to read from S3.
Click Next, provide a suitable Role Name, and then click Create Role.

This role allows EC2 instances to securely access S3 and connect via AWS Systems Manager without needing SSH keys.

✅ Conclusion

You have successfully set up the initial components for the AWS Three-Tier Architecture. In the next part, we will proceed with further configurations and deployments.

✅ Continue to Part 2 🚀

🔗 Read Part 2: AWS Three-Tier Architecture - Next Steps

AWS 101 Workshop

Dharshinisri G — Sun, 30 Mar 2025 08:23:13 +0000

Architecture Overview

Our architecture will consist of:

Two Availability Zones for high availability
Public and private subnets in each AZ
NAT Gateways for outbound internet access from private subnets
An Internet Gateway for public internet access
Security groups for Application Load Balancer and Web Servers
VPC Endpoint for private S3 access

Step-by-Step Implementation

1. Create the Virtual Private Cloud (VPC)

First, we'll create the VPC that will contain all our resources:

Navigate to the AWS VPC console
Click "Create VPC"
Select "VPC only" (we'll create subnets separately)
Enter these details:
- Name tag: Production-VPC
- IPv4 CIDR block: 10.0.0.0/16
- Leave IPv6 disabled (unless you specifically need it)
- Tenancy: Default
Click "Create VPC"

2. Create Subnets in Availability Zone 1

Now let's create our first set of subnets in Availability Zone 1:

Public Subnet A:

In the VPC console, go to "Subnets"
Click "Create subnet"
Select your VPC from the dropdown
Enter:
- Subnet name: Public-Subnet-A
- Availability Zone: Choose your first AZ (e.g., us-east-1a)
- IPv4 CIDR block: 10.0.0.0/20
Click "Create subnet"

Private Subnet A:

Click "Create subnet" again
Select your VPC
Enter:
- Subnet name: Private-Subnet-A
- Availability Zone: Same AZ as above (us-east-1a)
- IPv4 CIDR block: 10.0.128.0/20
Click "Create subnet"

3. Create Subnets in Availability Zone 2

Repeat the process for the second Availability Zone:

Public Subnet B:

Click "Create subnet"
Select your VPC
Enter:
- Subnet name: Public-Subnet-B
- Availability Zone: Choose your second AZ (e.g., us-east-1b)
- IPv4 CIDR block: 10.0.16.0/20
Click "Create subnet"

Private Subnet B:

Click "Create subnet" again
Select your VPC
Enter:
- Subnet name: Private-Subnet-B
- Availability Zone: Same AZ as above (us-east-1b)
- IPv4 CIDR block: 10.0.144.0/20
Click "Create subnet"

4. Create Internet Gateway

For public internet access:

In the VPC console, go to "Internet Gateways"
Click "Create internet gateway"
Name it Production-IGW
Click "Create internet gateway"
Select the new IGW and click "Actions" > "Attach to VPC"
Select your VPC and click "Attach internet gateway"

5. Create NAT Gateways

We'll need one NAT Gateway in each AZ for private subnet internet access:

NAT Gateway in AZ 1:

Go to "NAT Gateways" in the VPC console
Click "Create NAT gateway"
Configure:
- Name: NAT-GW-AZ1
- Subnet: Select Public-Subnet-A
- Connectivity type: Public
- Allocate Elastic IP (click "Allocate Elastic IP")
Click "Create NAT gateway"

NAT Gateway in AZ 2:

Click "Create NAT gateway" again
Configure:
- Name: NAT-GW-AZ2
- Subnet: Select Public-Subnet-B
- Connectivity type: Public
- Allocate Elastic IP (click "Allocate Elastic IP")
Click "Create NAT gateway"

Note: Wait for both NAT Gateways to show status "Available" before proceeding.

6. Configure Route Tables

We'll need separate route tables for public and private subnets.

Public Route Table:

Go to "Route Tables" in the VPC console
Click "Create route table"
Name it Public-Route-Table and select your VPC
Click "Create"
Select the new route table, go to "Routes" tab, click "Edit routes"
Add a route:
- Destination: 0.0.0.0/0
- Target: Select the Internet Gateway you created
Click "Save changes"
Go to "Subnet associations" tab, click "Edit subnet associations"
Select both public subnets (Public-Subnet-A and Public-Subnet-B)
Click "Save associations"

Private Route Table for AZ 1:

Click "Create route table"
Name it Private-Route-Table-AZ1 and select your VPC
Click "Create"
Select the new route table, go to "Routes" tab, click "Edit routes"
Add a route:
- Destination: 0.0.0.0/0
- Target: Select the NAT Gateway in AZ 1 (NAT-GW-AZ1)
Click "Save changes"
Go to "Subnet associations" tab, click "Edit subnet associations"
Select Private-Subnet-A
Click "Save associations"

Private Route Table for AZ 2:

Click "Create route table"
Name it Private-Route-Table-AZ2 and select your VPC
Click "Create"
Select the new route table, go to "Routes" tab, click "Edit routes"
Add a route:
- Destination: 0.0.0.0/0
- Target: Select the NAT Gateway in AZ 2 (NAT-GW-AZ2)
Click "Save changes"
Go to "Subnet associations" tab, click "Edit subnet associations"
Select Private-Subnet-B
Click "Save associations"

7. Create Security Groups

Application Load Balancer Security Group:

Go to "Security Groups" in the VPC console
Click "Create security group"
Enter:
- Security group name: ALB-Security-Group
- Description: Security group for Application Load Balancer
- VPC: Select your VPC
Under "Inbound rules", add:
- Type: HTTP, Source: 0.0.0.0/0
- Type: HTTPS, Source: 0.0.0.0/0
Click "Create security group"

Web Server Security Group:

Click "Create security group"
Enter:
- Security group name: Web-Server-Security-Group
- Description: Security group for web servers in private subnets
- VPC: Select your VPC
Under "Inbound rules", add:
- Type: HTTP, Source: Select the ALB security group
- Type: HTTPS, Source: Select the ALB security group
- Type: SSH, Source: Your IP (for management)
Click "Create security group"

8. Create VPC Endpoint for S3

For private access to S3 without going through the internet:

Go to "Endpoints" in the VPC console
Click "Create endpoint"
Configure:
- Name tag: S3-VPC-Endpoint
- Service category: AWS services
- Service: Select com.amazonaws.[region].s3 (replace [region] with your region)
- VPC: Select your VPC
- Route tables: Select all private route tables
- Policy: Full access (or customize as needed)
Click "Create endpoint"

9. Create Application Load Balancer

Now let's set up the ALB to distribute traffic to our web servers:

Go to the EC2 console and navigate to "Load Balancers"
Click "Create Load Balancer"
Select "Application Load Balancer"
Configure:
- Name: Web-ALB
- Scheme: Internet-facing
- IP address type: IPv4
- VPC: Select your VPC
- Mappings: Select both AZs and their public subnets
Under "Security groups", select the ALB security group
Configure listeners for HTTP (80) and HTTPS (443)
For now, skip target group creation (we'll create EC2 instances later)
Click "Create load balancer"

Next Steps

With this infrastructure in place, you're ready to:

Launch EC2 instances in your private subnets (attach the Web Server Security Group)
Create a target group and register your instances with the ALB
Set up Auto Scaling for high availability
Configure Route 53 for DNS management
Set up monitoring with CloudWatch

Cost Considerations

Remember that NAT Gateways incur hourly charges and data processing fees. Consider these cost optimization strategies:

Use NAT Instances instead of NAT Gateways for development environments
Implement S3 Gateway Endpoints (which are free) instead of Interface Endpoints where possible
Monitor your data transfer costs

Conclusion

You've now set up a highly available, secure AWS architecture spanning multiple Availability Zones. This architecture provides:

Fault tolerance through multi-AZ deployment
Security through public/private subnet separation
Scalability through the Application Load Balancer
Private access to S3 via VPC endpoints

This foundation can support web applications, APIs, or other services while maintaining security and availability best practices.

3-Tier Architecture (Part-6)

Dharshinisri G — Fri, 28 Mar 2025 10:42:51 +0000

AWS Three-Tier Architecture - Part 6

Update Config File
Web Instance Deployment
Configure Web Instance
Conclusion

Update Config File

Before creating and configuring the web instances, open the application-code/nginx.conf file from the repository we downloaded.

Scroll down to line 58 and replace [INTERNAL-LOADBALANCER-DNS] with your internal load balancer’s DNS entry.
You can find this DNS by navigating to your internal load balancer's details page.
Copy the DNS Name and replace it in your nginx.conf file.
Upload this file and the application-code/web-tier folder to the S3 bucket you created for this lab.

Web Instance Deployment

Navigate to the EC2 service dashboard and click on Instances on the left-hand side.
Click Launch Instances.
Select the first Amazon Linux 2 AMI.
Choose the T2.micro instance type (free tier eligible) and click Next: Configure Instance Details.
Proceed without a key pair since we'll use EC2 Instance Connect.
Configure the instance details:
- Select the correct Network, Subnet, and IAM role.
- Use a private subnet for this app layer.
- Enable Auto-assign Public IP.
- Attach the Web Tier Security Group.
- Assign the pre-created IAM Role.
Click Launch Instance.

Connect to Instance

Navigate to EC2 Instances.
Once the instance state is running, select the instance and click Connect.
Select the Session Manager tab and click Connect.
A new browser tab will open.
Test internet connectivity by running:

   sudo -su ec2-user
   ping 8.8.8.8

Configure Web Instance

Install Node.js

Install NVM (Node Version Manager) and Node.js:

   curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
   source ~/.bashrc
   nvm install 16
   nvm use 16

Download Web Tier Code

Navigate to the home directory and download the web-tier code from the S3 bucket:

   cd ~/
   aws s3 cp s3://BUCKET_NAME/web-tier/ web-tier --recursive

Navigate to the web-tier folder and build the React app:

   cd ~/web-tier
   npm install
   npm run build

Install and Configure NGINX

Install NGINX:

   sudo amazon-linux-extras install nginx1 -y

Navigate to the NGINX configuration directory:

   cd /etc/nginx
   ls

Remove the existing nginx.conf file and replace it with the one from S3:

   sudo rm nginx.conf
   sudo aws s3 cp s3://BUCKET_NAME/nginx.conf .

Restart NGINX:

   sudo service nginx restart

Ensure NGINX has the necessary permissions:

   chmod -R 755 /home/ec2-user

Enable NGINX to start on boot:

   sudo chkconfig nginx on

Conclusion

I hope this guide helped you through the AWS three-tier architecture implementation! 🚀

Continue to the next Part 🔗 Access Part 7 here: AWS Three-Tier Architecture (Part-7)

3-Tier Architecture (Part - 5)

Dharshinisri G — Fri, 28 Mar 2025 10:22:41 +0000

AWS Three-Tier Architecture: Internal Load Balancing and Auto Scaling

App Tier AMI
Target Group
Internal Load Balancer
Launch Template
Auto Scaling
Conclusion

App Tier AMI

Navigate to Instances in the EC2 dashboard.
Select the app tier instance we created.
Under Actions, choose Image and templates > Create Image.
Give the image a name and description, then click Create Image.
Monitor the AMI creation status under AMIs in the EC2 dashboard.

Target Group

While the AMI is being created, navigate to Target Groups under Load Balancing in the EC2 dashboard.
Click Create Target Group.
Select Instances as the target type and provide a name.
Set:
- Protocol: HTTP
- Port: 4000 (port our Node.js app runs on)
- VPC: Select the existing one
- Health Check Path: /health
Click Next and skip target registration for now.
Click Create Target Group.

Internal Load Balancer

Navigate to Load Balancers under Load Balancing in the EC2 dashboard.
Click Create Load Balancer.
Select Application Load Balancer.
Set:
- Name: Enter a name
- Scheme: Internal (as this is not public-facing)
- Network Configuration: Select the correct VPC and private subnets
- Security Group: Use the one created for this internal ALB
- Listener: HTTP on port 80
- Target Group: Select the one created earlier
Click Create Load Balancer.

Launch Template

Navigate to Launch Template under Instances in the EC2 dashboard.
Click Create Launch Template.
Set:
- Name: Enter a name
- Application and OS Images: Select the created app tier AMI
- Instance Type: t2.micro
- Key Pair & Network Settings: Do not include (not needed for access)
- Security Group: Select the one for the app tier
- IAM Instance Profile: Use the same IAM role as previous EC2 instances
Click Create Launch Template.

Auto Scaling

Navigate to Auto Scaling Groups in the EC2 dashboard.
Click Create Auto Scaling Group.
Provide a name and select the created Launch Template.
Configure:
- VPC: Select the existing VPC
- Private Instance Subnets: Choose the app tier subnets
Attach the Auto Scaling Group to the Load Balancer:
- Select the existing Target Group
Set scaling policies:
- Desired Capacity: 2
- Minimum Capacity: 2
- Maximum Capacity: 2
Click Next, Next, then Create Auto Scaling Group.

Conclusion

This completes the internal load balancing and auto-scaling setup for the AWS three-tier architecture. Your app tier is now configured to scale automatically and distribute traffic efficiently.

Continue to the next Part AWS Three-Tier Architecture (Part-6)

Internal Load Balancing and Auto Scaling
App Tier AMI

Target Group

Internal LoadBalancer

Launch Template

Auto Scaling

3-Tier Architecture (Part-3)

Dharshinisri G — Fri, 24 Jan 2025 11:00:41 +0000

AWS Three-Tier Architecture - Part 3

📌 Table of Contents

Database Deployment
- Subnet Groups
- Database Deployment
Conclusion

📊 Database Deployment

🔹 Subnet Groups

Open the RDS Dashboard in the AWS Management Console.
On the left panel, navigate to Subnet Groups and click on Create DB Subnet Group.

Provide a Name and Description for your subnet group.
Select the VPC we created earlier.

Add the subnets that were specifically created for the database layer in each Availability Zone.

If needed, go back to the VPC Dashboard to verify the correct Subnet IDs.

🔹 Database Deployment

In the RDS Dashboard, navigate to Databases on the left panel and click Create Database.

Choose Standard Create for an Amazon Aurora MySQL-Compatible database.

Keep the Engine options as default.
Under Templates, select Dev/Test (since this is not for production).
In Settings, set a Master Username and Password.
- Important: Note down these credentials, as they will be needed for database authentication.

Under Availability and Durability, choose to create an Aurora Replica (reader node) in a different Availability Zone.

In Connectivity:
- Set the VPC.
- Choose the Subnet Group we created earlier.
- Set Public Access to No.

Select the Security Group we created for the database layer.
Ensure Password Authentication is selected.
Click Create Database.
Once the database is provisioned, you should see a Reader and Writer instance in the database subnets of each Availability Zone.

Note down the Writer Endpoint & Credential Details for future use.

✅ Conclusion

You have now successfully deployed the Database Layer of the AWS Three-Tier Architecture! 🎉

🔗 Continue to Part 4: AWS Three-Tier Architecture (Part 4)

----------------------------------------------------------------Database Deployment

Create DB Subnet Groups

Database Deployment
Create Database

View Connections details & Store the details.

Created Database:

Create Instance:

Launch Instance:

///After Finishing the AWS 3-Tier , Delete all the things created
Deleting DB

Delete NAT Gateway

Release Elastic IPs

Delete Internet Gateway

Delete Snapshots

3-Tier Architecture (Part-2)

Dharshinisri G — Fri, 24 Jan 2025 09:50:27 +0000

AWS Three-Tier Architecture - Part 2

📌 Table of Contents

Networking and Security
- VPC Creation
- Subnet Creation
- Internet Connectivity
- NAT Gateway
- Routing Configuration
- Security Groups
✅ Conclusion

🛠 Networking and Security

🌐 VPC Creation

Open the VPC dashboard in the AWS console.
Click on Your VPCs from the left sidebar.

Select VPC only and enter:
- A Name tag.
- A CIDR range (Ensure it supports at least 6 subnets).

Click Create VPC.

📌 Note: Stay consistent with the AWS region for all resources.

🏗️ Subnet Creation

Navigate to Subnets in the VPC dashboard.
Click Create Subnet.

Select VPC

Create six subnets across two Availability Zones:
- Three subnets in AZ-1.

Three subnets in AZ-2.

Assign each subnet a Name, Availability Zone, and CIDR range.

📌 Tip: Use a naming convention like:

Public-Web-Subnet-AZ-1
Private-App-Subnet-AZ-1
Private-DB-Subnet-AZ-1

Note: Each subnet’s CIDR range should be a subset of your VPC CIDR.

🌍 Internet Connectivity

🚀 Internet Gateway (IGW)

Go to Internet Gateways in the VPC dashboard.
Click Create Internet Gateway, give it a name, and confirm.

Attach it to your VPC by selecting the correct VPC and clicking Attach Internet Gateway.

📡 NAT Gateway

To allow private instances to access the internet:

Go to NAT Gateways in the VPC dashboard.

Click Create NAT Gateway and:
- Enter a Name.
- Select one of your public subnets.
- Allocate an Elastic IP.

Click Create NAT Gateway.

Repeat for the other public subnet to ensure high availability.

🚦 Routing Configuration

Go to Route Tables in the VPC dashboard.

Click Create Route Table and enter a name.

After creation:
- Go to Routes tab → Click Edit routes.

Add a route for all external traffic (0.0.0.0/0) to the Internet Gateway.

Save changes.
1. Go to Subnet Associations:
Edit and associate the two public subnets.

For Private Subnets:

Create two more route tables (one per availability zone).
Route external traffic (0.0.0.0/0) to NAT Gateway.
Associate with the app-layer private subnets. Private Route table az1

private route table az2

🔒 Security Groups

Security Groups control inbound and outbound traffic.

1️⃣ Public Load Balancer Security Group

Allows HTTP (port 80) traffic from your IP.

2️⃣ Web Tier Security Group

Allows HTTP (port 80) traffic from the public load balancer.
Allows your IP to access the instances.

3️⃣ Internal Load Balancer Security Group

Allows HTTP (port 80) traffic from the web-tier security group.

4️⃣ Private Instances Security Group

Allows TCP (port 4000) traffic from the internal load balancer.
Allows your IP for testing.

5️⃣ Database Security Group

Allows MySQL/Aurora (port 3306) traffic from the private instance security group.

✅ Conclusion

You have now successfully set up the networking and security configurations for your AWS Three-Tier Architecture.

In Part 3, we will proceed with further configurations and deployments.

🔗 Continue to Part 3: AWS Three-Tier Architecture (Part 3)

Create VPC

Create Subnet

For Avalability Zone-1
Create-public-Subnet-az1

private-subnet1-az1

private-subnet2-db-az1

For Availability Zone-2
public-subnet-az2

private-subnet1-az2

private-subnet2-db-az2

All the subnets are created Successfully.

Create Internet Gateway

Attach to VPC

Create NAT gateway
For Az 1

For Az 2

*Configure Routing *

Create public Route Table

Edit Routes

Edit Subnet Associations

Add Public Subnets

Create private Route Table for az1

Edit Routes

Edit Subnet Associations

Create private route table for Az2

Edit Routes

Edit Subnet Associations

Create Security Group

INternet Facing lb sg

Web Tier SG

Internal lb SG

Private Instance SG

Database SG

EC2(MobaXterm)+IAM+S3

Dharshinisri G — Thu, 23 Jan 2025 17:43:36 +0000

Install & Run MobaXterm

Create An AWS EC2 instance
Name the instance & Select OS

Select Keypair & Allow SSH

Launch an Instance & Copy public IP address

Connecting the instance to MobaXterm

Launch MobXterm

Select Session & Choose SSH
Enter Public Ip address in Remote Host
Specify Username - ec2-user
Choose advanced SSH settings
check Use Private Key & Browse the pem file
Click OK
Accept

MobaXterm will connect to the EC2 instance:
So the Bash will be visible

Install AWS CLI on the EC2 Bucket
Check if aws cli is installed or not

AWS EC2 + IAM + S3: Using putty

Dharshinisri G — Thu, 23 Jan 2025 09:43:51 +0000

🚀 AWS EC2 + IAM + S3: A Step-by-Step Guide

This guide will walk you through setting up an EC2 instance, configuring Putty, creating an IAM role, and uploading files to S3.

📌 Step 1: Launch an EC2 Instance

1️⃣ Open EC2 Dashboard

Navigate to the AWS Console → EC2 Dashboard.

2️⃣ Create an EC2 Instance

Click Launch Instance
Enter a name and select an OS

3️⃣ Create & Select a Key Pair

Generate a key pair for secure SSH access
Select the created key pair

Click Launch Instance 🚀

📌 Step 2: Configure Security Group & Connect

1️⃣ Configure Inbound Rules

Select your instance → Security → Security Groups
Edit Inbound Rules to allow SSH (Port 22)

2️⃣ Connect to Instance

Select the instance → Connect → SSH Client

📌 Step 3: Install & Use Putty

1️⃣ Install Putty

Download and install Putty from here.

2️⃣ Convert `.pem` to `.ppk`

Open PuttyGen
Click Load → Select .pem file
Save the private key (.ppk)

3️⃣ Connect to EC2 via Putty

Open Putty
Copy and paste Public IP in the Host field
Go to SSH → Auth → Credentials
Browse and select the .ppk file

Click Open and login as:

ec2-user

📌 Step 4: Create an IAM Role

1️⃣ Open IAM Dashboard

Navigate to AWS IAM Dashboard → Roles

2️⃣ Create a New IAM Role

Select Create Role
Attach AmazonS3FullAccess permission policy

Name and create the IAM Role

3️⃣ Attach IAM Role to EC2

Select Modify IAM Role → Attach the created IAM role

📌 Step 5: Upload a File to S3

1️⃣ Create a Text File in EC2

Run the following command in Putty:

echo "This is a test file" > testfile.txt

2️⃣ Upload File to S3

aws s3 cp testfile.txt s3://your-bucket-name/

3️⃣ Verify Upload in S3

Check your S3 bucket to confirm the file is uploaded successfully.

🎯 Conclusion

Congratulations! 🎉 You have successfully:
✅ Launched an EC2 instance
✅ Connected via Putty
✅ Created and attached an IAM role
✅ Uploaded a file to S3

This guide provides a simple yet comprehensive way to manage EC2, IAM, and S3 effectively.

💬 Got questions? Let me know in the comments! 🚀

Deploying a React App on AWS S3 with CloudFront

Dharshinisri G — Thu, 23 Jan 2025 08:55:55 +0000

Deploying a React App to AWS S3 with CloudFront

1️⃣ Log in to AWS Console

2️⃣ Check if npm and Node.js are installed

Run the following commands to check if npm and Node.js are installed:

npm -v
node -v

3️⃣ Create a React App

Run the following commands to set up a React project using Vite:

npm create vite@latest
cd Dharshinisrig
npm install
npm run dev

4️⃣ View Your React App

Follow the link displayed in the terminal to open the React app in the browser.

The React app should display like this:

5️⃣ Modify App.tsx

Open the App.tsx file and make necessary edits.

6️⃣ Build the React App

Run the following command to build the project:

npm run build

7️⃣ Create an S3 Bucket in AWS

Go to AWS S3 and create a new bucket.

7.1 Remove Blocked Public Access

Disable "Block all public access."

7.2 Enable Bucket Versioning and Add Tags

8️⃣ Enable Static Website Hosting

Enable Static Website Hosting from the bucket properties.

9️⃣ Configure Bucket Permissions

Edit the bucket policy to allow public access.

Copy the Bucket ARN:

Generate the Bucket Policy and save the changes:

🔟 Upload React Build Files

Upload all files from the dist folder to the S3 bucket.

1️⃣1️⃣ Access Your Website

Copy the index.html URL:

Or copy the Bucket Endpoint:

http://714022205024-dharshinisrig.s3-website-us-east-1.amazonaws.com

1️⃣2️⃣ Set Up CloudFront for Faster Access

Create a CloudFront distribution for the S3 bucket.

12.1 Disable WAF

12.2 Deploy CloudFront

After deploying, copy the CloudFront URL:

https://d2yop5uofve2kk.cloudfront.net

Visit the CloudFront URL to see your React app.

1️⃣3️⃣ Clean Up AWS Resources

13.1 Delete CloudFront Distribution

13.2 Delete S3 Objects

13.3 Delete the S3 Bucket

🎉 Conclusion

You have successfully deployed a React app on AWS S3 and served it via CloudFront! 🚀

Amazon Macie

Dharshinisri G — Thu, 23 Jan 2025 03:17:18 +0000

🚀 Understanding Amazon Macie: A Simple and Detailed Guide

🏷 Tagline

Amazon Macie automates data classification and protects sensitive information across your AWS workloads.

📌 What is Amazon Macie?

Amazon Macie is a fully managed data security and privacy service that uses machine learning (ML) and pattern matching to detect and protect sensitive data in AWS.

🔑 Key Features

🔥 Top Features:

✅ Automated Data Discovery – Scans and identifies sensitive data.
✅ Compliance Ready Reports – Helps meet regulatory requirements.
✅ Customizable Alerting – Define rules and receive tailored alerts.
✅ Integration with Other AWS Services – Works with AWS Security Hub, IAM, and more.
✅ Scalable Monitoring – Adapts to growing cloud environments.

⚙ Technical Specifications:

Regions Supported – Available in multiple AWS regions.
Data Classification – Uses ML to classify PII, financial, and credential data.
Durability – Ensures high availability and reliability.
Request Limits – API rate limits apply based on AWS service quotas.

🛠 How Amazon Macie Works

Data Scanning – Automatically scans Amazon S3 buckets.
Sensitive Data Identification – Detects personally identifiable information (PII), financial records, and credentials.
Data Classification – Categorizes data based on sensitivity levels.
Alert Generation – Issues alerts for risks like open access or unusual activity.
Mitigation and Response – Works with AWS Security Hub for remediation.

Suggested Image: A flowchart showing how Macie scans, identifies, and alerts users about sensitive data.

🎯 Why Use Amazon Macie?

Benefit	Description
🔍 Enhanced Visibility	Understand where sensitive data is stored in AWS.
🛡 Improved Security	Detects unauthorized access and misconfigured permissions.
⚙ Automated Compliance	Helps meet regulatory requirements (GDPR, HIPAA, etc.).
💰 Cost Optimization	Pay-as-you-go model with flexible pricing.

🔥 Use Cases

📌 Real-Life Applications

🔹 Amazon IAM: Securely manage access to AWS services and resources, ensuring that only authorized users have appropriate permissions.
🔹 AWS Security Hub: Automates security checks and centralizes security alerts, providing a comprehensive view of your security posture to facilitate swift incident response.

📌 Pricing Model

💰 Pricing Overview:

Amazon Macie uses a pay-as-you-go pricing model with costs based on:

Data Classification
Inventory Monitoring

Example Pricing:

Data Processed: $0.10 per GB
Inventory Monitoring: $0.20 per bucket per month

📌 Check the official pricing page for up-to-date details.

🔄 Comparison With Similar Services

🆚 Competitors or Alternatives:

Amazon Macie vs. Microsoft Purview

While both offer data classification, Purview focuses more on multi-cloud environments, whereas Macie specializes in S3 data.

🌟 Benefits and Challenges

✅ Advantages:

Highly Scalable – Adapts to growing data needs.
Enhanced Security – Identifies risks and alerts users.
Ease of Use – Fully managed service with minimal setup.

⚠ Limitations or Challenges:

AWS Exclusive – Works only within AWS.
Costs – Pay-as-you-go pricing may add up for large data sets.

📌 Real-World Example or Case Study

📊 Case Study:

A Financial Services Company Utilized Amazon Macie to Identify Sensitive PII Data Stored in Amazon S3, Ensuring Compliance with GDPR.

By leveraging Macie, the company detected misconfigured access permissions and took corrective actions, reducing compliance risks and improving security.

📚 Additional Resources

📖 Amazon Macie Documentation
🎥 AWS Macie Video Overview

📝 Conclusion

Amazon Macie is a powerful tool for data security in AWS. It helps organizations detect, classify, and protect sensitive data efficiently. Whether you are concerned about compliance, security risks, or data breaches, Macie is a valuable addition to your cloud security strategy.

💬 What do you think about Amazon Macie? Have you used it before? Let me know in the comments! 🚀