DEV Community

Harshad D
Harshad D

Posted on

AWS Three-Tier Architecture

Introduction

A 3-Tier Architecture is a widely used architectural pattern that separates an application into three layers:

  1. Web Tier (Presentation Layer) – Handles user requests
  2. App Tier (Business Logic Layer) – Processes data and logic
  3. Database Tier (Data Layer) – Stores and retrieves data

This architecture enhances scalability, security, and maintainability. In this guide, we will set up a highly available 3-tier architecture on AWS using Amazon EC2, Elastic Load Balancer (ELB), and Amazon RDS (Aurora).

Part - 1

Architecture

Image description

Download Code from Github Repository

   - git clone https://github.com/Naveen3251/AWS_3Tier.git
Enter fullscreen mode Exit fullscreen mode

S3 Bucket Creation

  1. Navigate to the S3 service in the AWS console and create a new S3 bucket.

  2. Give it a unique name, and then leave all the defaults as in. Make sure to select the region that you intend to run this whole lab in. This bucket is where we will upload our code later.

Image description

IAM EC2 Instance Role Creation

  1. Navigate to the IAM dashboard in the AWS console and create an EC2 role.

  2. Select EC2 as the trusted entity.

  3. When adding permissions, include the following AWS managed policies. You can search for them and select them. These policies will allow our instances to download our code from S3 and use Systems Manager Session Manager to securely connect to our instances without SSH keys through the AWS console.

     - AmazonSSMManagedInstanceCore
 - AmazonS3ReadOnlyAccess

Image description

  • Give your role a name, and then click Create Role.

Image description

Part - 2

Networking and Security

VPC Creation

  1. Navigate to the VPC dashboard in the AWS console and navigate to Your VPCs on the left hand side.

Make sure VPC only is selected, and fill out the VPC Settings with a Name tag and a CIDR range of your choice.

NOTE: Make sure you pay attention to the region you’re deploying all your resources in. You’ll want to stay consistent for this entier project.

NOTE: Choose a CIDR range that will allow you to create at least 6 subnets.

Image description

Subnet Creation

  1. Next, create your subnets by navigating to Subnets on the left side of the dashboard and clicking Create subnet.

  2. We will need six subnets across two availability zones. That means that three subnets will be in one availability zone, and three subnets will be in another zone. Each subnet in one availability zone will correspond to one layer of our three tier architecture. Create each of the 6 subnets by specifying the VPC we created in part 1 and then choose a name, availability zone, and appropriate CIDR range for each of the subnets.

NOTE: It may be helpful to have a naming convention that will help you remember what each subnet is for. For example in one AZ you might have the following:Public-Web-Subnet-AZ-1, Private-App-Subnet-AZ-1, Private-DB-Subnet-AZ-1.

NOTE: Remember, your CIDR range for the subnets will be subsets of your VPC CIDR range.

Image description

Image description

Your final subnet setup should be similar to this. Verify that you have 3 subnets across 2 different availability zones.

Image description

Internet Connectivity

Internet Gateway

  • In order to give the public subnets in our VPC internet access we will have to create and attach an Internet Gateway. On the left hand side of the VPC dashboard, select Internet Gateway.
  • Create your internet gateway by simply giving it a name and clicking Create internet gateway.

Image description

  • After creating the internet gateway, attach it to your VPC that you create in the VPC and Subnet Creation step of the workshop. You have a couple options on how to do this, either with the creation success message or the Actions drop down.

Image description

  • Then, select the correct VPC and click Attach internet gateway.

Image description

NAT Gateway

  • In order for our instances in the app layer private subnet to be able to access the internet they will need to go through a NAT Gateway. For high availability, you’ll deploy one NAT gateway in each of your public subnets. Navigate to NAT Gateways on the left side of the current dashboard and click Create NAT Gateway.

  • Fill in the Name, choose one of the public subnets you created in part 2, and then allocate an Elastic IP. Click Create NAT gateway.

Image description

Image description

  • Repeat step 1 and 2 for the other subnet.

Image description

Routing Configuration

  • Navigate to Route Tables on the left side of the VPC dashboard and click Create route table First, let’s create one route table for the web layer public subnets and name it accordingly.

Image description

  • After creating the route table, you'll automatically be taken to the details page. Scroll down and click on the Routes tab and Edit routes.

Image description

  • Add a route that directs traffic from the VPC to the internet gateway. In other words, for all traffic destined for IPs outside the VPC CDIR range, add an entry that directs it to the internet gateway as a target. Save the changes.

  • Edit the Explicit Subnet Associations of the route table by navigating to the route table details again. Select Subnet Associations and click Edit subnet associations.

Image description

  • Select the two web layer public subnets you created eariler and click Save associations.

  • Now create 2 more route tables, one for each app layer private subnet in each availability zone. These route tables will route app layer traffic destined for outside the VPC to the NAT gateway in the respective availability zone, so add the appropriate routes for that.

  • Once the route tables are created and routes added, add the appropriate subnet associations for each of the app layer private subnets.

Security Groups

  • Security groups will tighten the rules around which traffic will be allowed to our Elastic Load Balancers and EC2 instances. Navigate to Security Groups on the left side of the VPC dashboard, under Security.

  • The first security group you’ll create is for the public, internet facing load balancer. After typing a name and description, add an inbound rule to allow HTTP type traffic for your IP.

Image description

  • The second security group you’ll create is for the public instances in the web tier. After typing a name and description, add an inbound rule that allows HTTP type traffic from your internet facing load balancer security group you created in the previous step. This will allow traffic from your public facing load balancer to hit your instances. Then, add an additional rule that will allow HTTP type traffic for your IP. This will allow you to access your instance when we test.

Image description

  • The third security group will be for our internal load balancer. Create this new security group and add an inbound rule that allows HTTP type traffic from your public instance security group. This will allow traffic from your web tier instances to hit your internal load balancer.

Image description

  • The fourth security group we’ll configure is for our private instances. After typing a name and description, add an inbound rule that will allow TCP type traffic on port 4000 from the internal load balancer security group you created in the previous step. This is the port our app tier application is running on and allows our internal load balancer to forward traffic on this port to our private instances. You should also add another route for port 4000 that allows your IP for testing.

Image description

  • The fifth security group we’ll configure protects our private database instances. For this security group, add an inbound rule that will allow traffic from the private instance security group to the MYSQL/Aurora port (3306).

Image description

Part - 3

Database Deployement

Subnet Groups

  • Navigate to the RDS dashboard in the AWS console and click on Subnet groups on the left hand side. Click Create DB subnet group.

Image description

  • Give your subnet group a name, description, and choose the VPC we created.

Image description

  • When adding subnets, make sure to add the subnets we created in each availability zone specificaly for our database layer. You may have to navigate back to the VPC dashboard and check to make sure you're selecting the correct subnet IDs.

Image description

Database Deployement

  • Navigate to Databases on the left hand side of the RDS dashboard and click Create database.

  • We'll now go through several configuration steps. Start with a Standard create for this MySQL-Compatible Amazon Aurora database. Leave the rest of the defaults in the Engine options as default.

Image description

  • Under the Templates section choose Dev/Test since this isn't being used for production at the moment. Under Settings set a username and password of your choice and note them down since we'll be using password authentication to access our database.

Image description

  • Next, under Availability and durability change the option to create an Aurora Replica or reader node in a different availability zone. Under Connectivity, set the VPC, choose the subnet group we created earlier, and select no for public access.

Image description

Image description

Image description

  • Set the security group we created for the database layer, make sure password authentication is selected as our authentication choice, and create the database.

Image description

  • When your database is provisioned, you should see a reader and writer instance in the database subnets of each availability zone. Note down the writer endpoint for your database for later use.

Image description

Part - 4

App Instance Deployment

Navigate to the EC2 service dashboard and click on Instances on the left hand side. Then, click Launch Instances.

Image description

  1. Select the first Amazon Linux 2 AMI.

  2. We'll be using the free tier eligible T.2 micro instance type. Select that and click Next: Configure Instance Details.

  3. Proceed without key-pair because we going to use ec2-instance login.

Image description

  • When configuring the instance details, make sure to select to correct Network, subnet, and IAM role we created. Note that this is the app layer, so use one of the private subnets we created for this layer.

Below we using already created VPC and Private Subnet AZ-1
Below we using already created private instance security group
Image description

Below we using already created IAM role
Image description

  • Finally click "Launch Instance"

Image description

Connect to Instance

  1. Navigate to your list of running EC2 Instances by clicking on Instances on the left hand side of the EC2 dashboard. When the instance state is running, connect to your instance by clicking the checkmark box to the left of the instance, and click the connect button on the top right corner of the dashboard. Select the Session Manager tab, and click connect. This will open a new browser tab for you.

NOTE: If you get a message saying that you cannot connect via session manager, then check that your instances can route to your NAT gateways and verify that you gave the necessary permissions on the IAM role for the Ec2 instance.

Image description

When you first connect to your instance like this, you will be logged in as ssm-user which is the default user. Switch to ec2-user by executing the following command in the browser terminal:

        `sudo -su ec2-user`
Enter fullscreen mode Exit fullscreen mode

Let’s take this moment to make sure that we are able to reach the internet via our NAT gateways. If your network is configured correctly up till this point, you should be able to ping the google DNS servers:

          `ping 8.8.8.8`
Enter fullscreen mode Exit fullscreen mode

You should see a transmission of packets. Stop it by pressing cntrl c.

NOTE: If you can’t reach the internet then you need to double check your route tables and subnet associations to verify if traffic is being routed to your NAT gateway!

Configure Database

Start by downloading the MySQL CLI:

sudo yum install mysql -y
Enter fullscreen mode Exit fullscreen mode

if above one causing issue like,

try the below commands to install without any errors

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

Initiate your DB connection with your Aurora RDS writer endpoint. In the following command, replace the RDS writer endpoint and the username, and then execute it in the browser terminal:

 mysql -h CHANGE-TO-YOUR-RDS-ENDPOINT -u CHANGE-TO-USER-NAME -p
Enter fullscreen mode Exit fullscreen mode

You will then be prompted to type in your password. Once you input the password and hit enter, you should now be connected to your database.

Create a database called webappdb with the following command using the MySQL CLI:

 CREATE DATABASE webappdb;
Enter fullscreen mode Exit fullscreen mode

You can verify that it was created correctly with the following command:

 SHOW DATABASES;
Enter fullscreen mode Exit fullscreen mode

Create a data table by first navigating to the database we just created:

 USE webappdb;
Enter fullscreen mode Exit fullscreen mode

Then, create the following transactions table by executing this create table command:

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

Verify the table was created:

 SHOW TABLES;
Enter fullscreen mode Exit fullscreen mode

Insert data into table for use/testing later:

 INSERT INTO transactions (amount,description) VALUES ('400','groceries');
Enter fullscreen mode Exit fullscreen mode

Verify that your data was added by executing the following command:

 SELECT * FROM transactions;
Enter fullscreen mode Exit fullscreen mode

When finished, just type exit and hit enter to exit the MySQL client.

Configure App Instance

The first thing we will do is update our database credentials for the app tier. To do this, open the application-code/app-tier/DbConfig.js file from the github repo in your favorite text editor on your computer. You’ll see empty strings for the hostname, user, password and database. Fill this in with the credentials you configured for your database, the writer endpoint of your database as the hostname, and webappdb for the database. Save the file.

  • Upload the app-tier folder to the S3 bucket that you created in part 1.

Image description

Go back to your SSM session. Now we need to install all of the necessary components to run our backend application. Start by installing NVM (node version manager).

 curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
 source ~/.bashrc
Enter fullscreen mode Exit fullscreen mode

Next, install a compatible version of Node.js and make sure it's being used.

 nvm install 16
 nvm use 16
Enter fullscreen mode Exit fullscreen mode

PM2 is a daemon process manager that will keep our node.js app running when we exit the instance or if it is rebooted. Install that as well.

 npm install -g pm2
Enter fullscreen mode Exit fullscreen mode

Now we need to download our code from our s3 buckets onto our instance. In the command below, replace BUCKET_NAME with the name of the bucket you uploaded the app-tier folder to:

 cd ~/
 aws s3 cp s3://BUCKET_NAME/app-tier/ app-tier --recursive
Enter fullscreen mode Exit fullscreen mode

Navigate to the app directory, install dependencies, and start the app with pm2.

 cd ~/app-tier
 npm install
 pm2 start index.js
Enter fullscreen mode Exit fullscreen mode

To make sure the app is running correctly run the following:

 pm2 list
Enter fullscreen mode Exit fullscreen mode

If you see a status of online, the app is running. If you see errored, then you need to do some troubleshooting. To look at the latest errors, use this command:

 pm2 logs
Enter fullscreen mode Exit fullscreen mode

NOTE: If you’re having issues, check your configuration file for any typos, and double check that you have followed all installation commands till now.

Right now, pm2 is just making sure our app stays running when we leave the SSM session. However, if the server is interrupted for some reason, we still want the app to start and keep running. This is also important for the AMI we will create:

 pm2 startup
Enter fullscreen mode Exit fullscreen mode

After running this you will see a message similar to this.

 [PM2] To setup the Startup Script, copy/paste the following command: sudo env PATH=$PATH:/home/ec2-user/.nvm/versions/node/v16.0.0/bin /home/ec2-user/.nvm/versions/node/v16.0.0/lib/node_modules/pm2/bin/pm2 startup systemd -u ec2-user —hp /home/ec2-user
Enter fullscreen mode Exit fullscreen mode

DO NOT run the above command, rather you should copy and past the command in the output you see in your own terminal. After you run it, save the current list of node processes with the following command:

 pm2 save
Enter fullscreen mode Exit fullscreen mode

Test App Tier

Now let's run a couple tests to see if our app is configured correctly and can retrieve data from the database.

To hit out health check endpoint, copy this command into your SSM terminal. This is our simple health check endpoint that tells us if the app is simply running.

 curl http://localhost:4000/health
Enter fullscreen mode Exit fullscreen mode

The response should looks like the following:

 "This is the health check"
Enter fullscreen mode Exit fullscreen mode

Next, test your database connection. You can do that by hitting the following endpoint locally:

 curl http://localhost:4000/transaction
Enter fullscreen mode Exit fullscreen mode

You should see a response containing the test data we added earlier:

 {"result":[{"id":1,"amount":400,"description":"groceries"},{"id":2,"amount":100,"description":"class"},{"id":3,"amount":200,"description":"other groceries"},{"id":4,"amount":10,"description":"brownies"}]}
Enter fullscreen mode Exit fullscreen mode

If you see both of these responses, then your networking, security, database and app configurations are correct.

Your app layer is fully configured and ready to go.

Part - 5

Internal Load Balancing and Auto Scaling

App Tier AMI

  1. Navigate to Instances on the left hand side of the EC2 dashboard. Select the app tier instance we created and under Actions select Image and templates. Click Create Image.

  2. Give the image a name and description and then click Create image. This will take a few minutes, but if you want to monitor the status of image creation you can see it by clicking AMIs under Images on the left hand navigation panel of the EC2 dashboard.

Image description

Target Group

  1. While the AMI is being created, we can go ahead and create our target group to use with the load balancer. On the EC2 dashboard navigate to Target Groups under Load Balancing on the left hand side. Click on Create Target Group.

  2. The purpose of forming this target group is to use with our load blancer so it may balance traffic across our private app tier instances. Select Instances as the target type and give it a name.

Image description

Then, set the protocol to HTTP and the port to 4000. Remember that this is the port our Node.ja app is running on. Select the VPC we've been using thus far, and then change the health check path to be /health. This is the health check endpoint of our app. Click Next.

Image description

Image description

We are NOT going to register any targets for now, so just skip that step and create the target group.

Image description

Image description

Internal Load Balancer

  1. On the left hand side of the EC2 dashboard select Load Balancers under Load Balancing and click Create Load Balancer.

  2. We'll be using an Application Load Balancer for our HTTP traffic so click the create button for that option.

Image description

After giving the load balancer a name, be sure to select internal since this one will not be public facing, but rather it will route traffic from our web tier to the app tier.

Image description

Select the correct network configuration for VPC and private subnets.

Select the security group we created for this internal ALB. Now, this ALB will be listening for HTTP traffic on port 80. It will be forwarding the traffic to our target group that we just created, so select it from the dropdown, and create the load balancer.

Image description

Image description

Launch Template

  1. Before we configure Auto Scaling, we need to create a Launch template with the AMI we created earlier. On the left side of the EC2 dashboard navigate to Launch Template under Instances and click Create Launch Template.

  2. Name the Launch Template, and then under Application and OS Images include the app tier AMI you created.

Image description

Image description

Under Instance Type select t2.micro. For Key pair and Network Settings don't include it in the template. We don't need a key pair to access our instances and we'll be setting the network information in the autoscaling group.

Image description

Set the correct security group for our app tier, and then under Advanced details use the same IAM instance profile we have been using for our EC2 instances.

Image description

Auto Scaling

  1. We will now create the Auto Scaling Group for our app instances. On the left side of the EC2 dashboard navigate to Auto Scaling Groups under Auto Scaling and click Create Auto Scaling group.

  2. Give your Auto Scaling group a name, and then select the Launch Template we just created and click next.

Image description
On the Choose instance launch options page set your VPC, and the private instance subnets for the app tier.

Image description

For this next step, attach this Auto Scaling Group to the Load Balancer we just created by selecting the existing load balancer's target group from the dropdown. Then, click next.

For Configure group size and scaling policies, set desired, minimum and maximum capacity to 2. Click skip to review and then Create Auto Scaling Group.

Image description

After the above step Click next, next finally click "create autoscaling group"

Part - 6

Update Config File

Before we create and configure the web instances, open up the application-code/nginx.conf file from the repo we downloaded. Scroll down to line 58 and replace [INTERNAL-LOADBALANCER-DNS] with your internal load balancer’s DNS entry. You can find this by navigating to your internal load balancer's details page.

DNS Name is,

Image description

Copy the above DNS name and replace in your nginx.conf file

Image description

Then, upload this file and the application-code/web-tier folder to the s3 bucket you created for this lab.

Web Instance Deployment

  1. Navigate to the EC2 service dashboard and click on Instances on the left hand side. Then, click Launch Instances.

  2. Select the first Amazon Linux 2 AMI.

Image description

We'll be using the free tier eligible T.2 micro instance type. Select that and click Next: Configure Instance Details.

Proceed without key-pair because we going to use ec2-instance login.

When configuring the instance details, make sure to select to correct Network, subnet, and IAM role we created. Note that this is the app layer, so use one of the private subnets we created for this layer.

Below we using already created VPC and Public Subnet AZ-1 and Enable auto assign Public IP

Below we using already created web tier security group

Image description

Below we using already created IAM role

Finally click "Launch Instance"

Connect to Instance

Navigate to your list of running EC2 Instances by clicking on Instances on the left hand side of the EC2 dashboard. When the instance state is running, connect to your instance by clicking the checkmark box to the left of the instance, and click the connect button on the top right corner of the dashboard. Select the Session Manager tab, and click connect. This will open a new browser tab for you.

Image description

Test connectivity here via ping as well since this instance should have internet connectivity:

 sudo -su ec2-user 
 ping 8.8.8.8
Enter fullscreen mode Exit fullscreen mode

Configure Web Instance

We now need to install all of the necessary components needed to run our front-end application. Again, start by installing NVM and node :

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

Now we need to download our web tier code from our s3 bucket:

 cd ~/
 aws s3 cp s3://BUCKET_NAME/web-tier/ web-tier --recursive
Enter fullscreen mode Exit fullscreen mode

Navigate to the web-layer folder and create the build folder for the react app so we can serve our code:

 cd ~/web-tier
 npm install 
 npm run build
Enter fullscreen mode Exit fullscreen mode

NGINX can be used for different use cases like load balancing, content caching etc, but we will be using it as a web server that we will configure to serve our application on port 80, as well as help direct our API calls to the internal load balancer.

 sudo amazon-linux-extras install nginx1 -y
Enter fullscreen mode Exit fullscreen mode

We will now have to configure NGINX. Navigate to the Nginx configuration file with the following commands and list the files in the directory:

 cd /etc/nginx
 ls
Enter fullscreen mode Exit fullscreen mode

You should see an nginx.conf file. We’re going to delete this file and use the one we uploaded to s3. Replace the bucket name in the command below with the one you created for this workshop:

 sudo rm nginx.conf
 sudo aws s3 cp s3://BUCKET_NAME/nginx.conf .
Enter fullscreen mode Exit fullscreen mode

Then, restart Nginx with the following command:

 sudo service nginx restart
Enter fullscreen mode Exit fullscreen mode

To make sure Nginx has permission to access our files execute this command:

 chmod -R 755 /home/ec2-user
Enter fullscreen mode Exit fullscreen mode

And then to make sure the service starts on boot, run this command:

 sudo chkconfig nginx on
Enter fullscreen mode Exit fullscreen mode

Part - 7

External Load Balancer and Auto Scaling

Web Tier AMI

  1. 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.

  2. Give the image a name and description and then click Create image. This will take a few minutes, but if you want to monitor the status of image creation you can see it by clicking AMIs under Images on the left hand navigation panel of the EC2 dashboard.

Image description

Target Group

While the AMI is being created, we can go ahead and create our target group to use with the load balancer. On the EC2 dashboard navigate to Target Groups under Load Balancing on the left hand side. Click on Create Target Group.

Image description

The purpose of forming this target group is to use with our load blancer so it may balance traffic across our public web tier instances. Select Instances as the target type and give it a name.

Image description

Then, set the protocol to HTTP and the port to 80. Remember this is the port NGINX is listening on. Select the VPC we've been using thus far, and then change the health check path to be /health. Click Next.

Image description

We are NOT going to register any targets for now, so just skip that step and create the target group.

Image description

Image description

Internet Facing Load Balancer

On the left hand side of the EC2 dashboard select Load Balancers under Load Balancing and click Create Load Balancer.

We'll be using an Application Load Balancer for our HTTP traffic so click the create button for that option.

Image description

After giving the load balancer a name, be sure to select internet facing since this one will not be public facing, but rather it will route traffic from our web tier to the app tier.

Image description

Select the correct network configuration for VPC and public subnets.

Select the security group we created for this internal ALB. Now, this ALB will be listening for HTTP traffic on port 80. It will be forwarding the traffic to our target group that we just created, so select it from the dropdown, and create the load balancer.

*Launch Template
*

Before we configure Auto Scaling, we need to create a Launch template with the AMI we created earlier. On the left side of the EC2 dashboard navigate to Launch Template under Instances and click Create Launch Template.

Name the Launch Template, and then under Application and OS Images include the app tier AMI you created.

Image description

Under Instance Type select t2.micro. For Key pair and Network Settings don't include it in the template. We don't need a key pair to access our instances and we'll be setting the network information in the autoscaling group.

Image description

Set the correct security group for our web tier, and then under Advanced details use the same IAM instance profile we have been using for our EC2 instances.

Image description

Auto Scaling

We will now create the Auto Scaling Group for our web instances. On the left side of the EC2 dashboard navigate to Auto Scaling Groups under Auto Scaling and click Create Auto Scaling group.

Give your Auto Scaling group a name, and then select the Launch Template we just created and click next.

On the Choose instance launch options page set your VPC, and the public subnets for the web tier.

For this next step, attach this Auto Scaling Group to the Load Balancer we just created by selecting the existing web tier load balancer's target group from the dropdown. Then, click next.

Image description

For Configure group size and scaling policies, set desired, minimum and maximum capacity to 2. Click skip to review and then Create Auto Scaling Group.

Finally we get our "WebApp"

Image description

Conclusion
Well done on successfully completing your three-tier architecture project on AWS! It's a significant accomplishment to have followed through from Part 1 to Part 7 of the blog series. Before wrapping up, it's essential to ensure that all the services you created for learning purposes are properly cleaned up to avoid any unnecessary costs or lingering resources.

_Thankyou !!!

Hope You have Learned !!!_

Top comments (0)