Prepare for your exams
Get points
Guidelines and tips

Prepare for your exams

Study with the several resources on Docsity

Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips

Sell on Docsity

Log in Sign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search Store documents

The best documents sold by students who completed their studies

Search through all study resources

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents

20 Points

For each uploaded document

Answer questions

5 Points

For each given answer (max 1 per day)

All the ways to get free points

Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

University Rankings

Discover the best universities in your country according to Docsity users

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

From our blog

Exams and Study

Go to the blog

Cloud Computing: Load Balancers, Auto-Scaling, and Route 53, Assignments of Web Application Development

Avantika University Web Application Development

A comprehensive overview of cloud computing concepts, focusing on load balancing, auto-scaling, and route 53. It explains the differences between classic load balancers and application load balancers, highlighting their benefits and use cases. The document also delves into amazon auto scaling, explaining its role in managing ec2 instances and ensuring application availability. Finally, it explores route 53, a dns web service for domain registration, dns routing, and health checking.

Typology: Assignments

2020/2021

Available from 02/02/2025

the-manku-store 🇮🇳

8 documents

1 / 21

This page cannot be seen from the preview

Don't miss anything!

1

CLOUD COMPUTING: ASSIGNMENT 3

MAYANK SONI, AU17B1007

Task-1: Create a Classic Load Balancer

Problem Statement: Load Balancing, Auto-Scaling, and Route 53 to manage traffic

• What is a Classic Load Balancer?

• Benefits Classic Load Balance.

Elastic Load Balancing supports three types of load balancers: Application Load Balancers, Network Load

Balancers, and Classic Load Balancers.

A Classic load balancer distributes incoming application traffic across multiple EC2 instances in multiple

Availability Zones. This increases the fault tolerance of your applications. Elastic Load Balancing detects

unhealthy instances and routes traffic only to healthy instances.

Classic load balancer serves as a single point of contact for clients. This increases the availability of the

application. User can add and remove instances from the load balancer as per the needs change, without

disrupting the overall flow of requests to the application. Elastic Load Balancing scales the load balancer as

traffic to the application changes over time. Elastic Load Balancing can scale to the vast majority of workloads

automatically.

Using a Classic Load Balancer instead of an Application Load Balancer has the following benefits:

• Support for EC2-Classic

• Support for TCP and SSL listeners

• Support for sticky sessions using application-generated cookies

• Demonstration

- Under services navigate to EC2 Under EC2 go to Load balancers.

Partial preview of the text

Download Cloud Computing: Load Balancers, Auto-Scaling, and Route 53 and more Assignments Web Application Development in PDF only on Docsity!

CLOUD COMPUTING: ASSIGNMENT 3

MAYANK SONI, AU17B

Task-1: Create a Classic Load Balancer Problem Statement: Load Balancing, Auto-Scaling, and Route 53 to manage traffic

**- What is a Classic Load Balancer?

Benefits Classic Load Balance.** Elastic Load Balancing supports three types of load balancers: Application Load Balancers, Network Load Balancers, and Classic Load Balancers. A Classic load balancer distributes incoming application traffic across multiple EC2 instances in multiple Availability Zones. This increases the fault tolerance of your applications. Elastic Load Balancing detects unhealthy instances and routes traffic only to healthy instances. Classic load balancer serves as a single point of contact for clients. This increases the availability of the application. User can add and remove instances from the load balancer as per the needs change, without disrupting the overall flow of requests to the application. Elastic Load Balancing scales the load balancer as traffic to the application changes over time. Elastic Load Balancing can scale to the vast majority of workloads automatically. Using a Classic Load Balancer instead of an Application Load Balancer has the following benefits:
Support for EC2-Classic
Support for TCP and SSL listeners
Support for sticky sessions using application-generated cookies - Demonstration
Under services navigate to EC2 Under EC2 go to Load balancers.

Assign security groups to the load balancer.
Select a load balancer type.
Define the load balancer.

Under permissions go to bucket policy.
Create and verify the load balancer.
Successfully created.

To check go to public DNS names for the load balancer

Under services navigate to EC2 Under EC2 go to Load balancers.
Select a load balancer type.
Configure the load balancer.

Register targets with the target group.
Configure a security group.
Configure the target group.

**- What is Amazon Auto Scaling?

Amazon Auto Scaling benefits** Amazon Auto Scaling helps you ensure that you have the correct number of Amazon EC2 instances available to handle the load for your application. Collections of EC2 instances, called Auto Scaling groups. User can specify the minimum number of instances in each Auto Scaling group, and Amazon EC2 Auto Scaling ensures that the group never goes below this size. User can specify the maximum number of instances in each Auto Scaling group, and Amazon EC2 Auto Scaling ensures that your the never goes above this size. If user specify the desired capacity, either when user create the group or at any time thereafter, Amazon EC Auto Scaling ensures that the group has this many instances. If user specify scaling policies, then Amazon EC2 Auto Scaling can launch or terminate instances as demand on the application increases or decreases. Adding Amazon Auto Scaling to the application architecture is one way to maximize the benefits of the AWS Cloud. When user use Amazon EC2 Auto Scaling, the applications gain the following benefits:
Better fault tolerance. Amazon Auto Scaling can detect when an instance is unhealthy, terminate it, and launch an instance to replace it. User can also configure Amazon Auto Scaling to use multiple Availability Zones. If one Availability Zone becomes unavailable, Amazon Auto Scaling can launch instances in another one to compensate.
Better availability. Amazon Auto Scaling helps ensure that the application always has the right amount of capacity to handle the current traffic demand.
Better cost management. Amazon Auto Scaling can dynamically increase and decrease capacity as needed. Because user pay for the EC2 instances use, User save money by launching instances when they are needed and terminating them when they aren’t. Task-4: Auto-Scaling and Scaling policy - Demonstration

Create a launch template.

Configure advance options
Configure group size and scaling polices

Review it.
Auto scaling group created.
Under details go to activity.

**- What is Amazon Route 53?

Routing traffic for subdomains
Demonstration** Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. You can use Route 53 to perform three main functions in any combination: domain registration, DNS routing, and health checking. If you choose to use Route 53 for all three functions, perform the steps in this order:

Register domain names Website needs a name, such as example.com. Route 53 lets you register a name for your website or web application, known as a domain name.
Route internet traffic to the resources for your domain When a user opens a web browser and enters your domain name (example.com) or subdomain name (acme.example.com) in the address bar, Route 53 helps connect the browser with your website or web application.
Check the health of your resources Route 53 sends automated requests over the internet to a resource, such as a web server, to verify that it’s reachable, available, and functional. You also can choose to receive notifications when a resource becomes unavailable and choose to route internet traffic away from unhealthy resources. Routing traffic for subdomains When you want to route traffic to your resources for a subdomain, such as acme.example.com or zenith. example.com, you have two options:

Create records in the hosted zone for the domain Typically, to route traffic for a subdomain, you create a record in the hosted zone that has the same name as the domain. For example, to route internet traffic for acme.example.com to a web server in your data center, you create a record named acme.example.com in the example.com hosted zone. For more information, see the topic Working with records and its subtopics.
Create a hosted zone for the subdomain, and create records in the new hosted zone You can also create a hosted zone for the subdomain. Using a separate hosted zone to route internet traffic for a subdomain is sometimes known as “delegating responsibility for a subdomain to a hosted zone” or “delegating a subdomain to other name servers” or some similar combination of terms. Here’s an overview of how it works:

You create a hosted zone that has the same name as the subdomain that you want to route traffic for, such as acme.example.com.
You create records in the new hosted zone that define how you want to route traffic for the subdomain (acme.example.com) and its subdomains, such as backend.acme.example.com.
You get the name servers that Route 53 assigned to the new hosted zone when you created it.
You create a new NS record in the hosted zone for the domain (example.com), and you specify the four name servers that you got in step 3. Task-4: Point a sub-domain to EC2 box in Route 53

Start with creating instance - Select AMI
Selecting instance type
Adding tags

Select Domain name
Click create record
Select simple routing

Define record name / value / record type and hit Define simple record
Mark the record and hit create records
Record successfully created

Cloud Computing: Load Balancers, Auto-Scaling, and Route 53, Assignments of Web Application Development

Related documents

Partial preview of the text

Download Cloud Computing: Load Balancers, Auto-Scaling, and Route 53 and more Assignments Web Application Development in PDF only on Docsity!

CLOUD COMPUTING: ASSIGNMENT 3

MAYANK SONI, AU17B