Skip to content

Latest commit

 

History

History
134 lines (113 loc) · 5.12 KB

README.md

File metadata and controls

134 lines (113 loc) · 5.12 KB
Directory

Tech Portfolio Home / AWS Projects & Labs

Multi Availability Zone EC2 Deployment

Description

Scenario: The island's stabilization system is failing and needs increased reliability and availability for its computational modules.

Solution: To increase the reliability and availability of the island's stabilization system, Amazon EC2 instances will be deployed across multiple Availability Zones, ensuring fault tolerance and minimizing downtime in case of localized failures.

Program walk-through:

Navigated to the EC2 Section within AWS and reviewed the selected region, making sure its set to N. Virginia (us-east-1):
Disk Sanitization Steps

Lauching a new EC2 instance:
Disk Sanitization Steps

Named this EC2 instance webserver01 & choose Amazon Linux as its operating system.
Disk Sanitization Steps

Clicked the Amazon Machine Image (AMI) dropdown menu & choose Amazon Linux 2 AMI (HVM). For Instance type I choose t2.micro:
Disk Sanitization Steps

For Key pair name, choose Proceed without a key pair:
Disk Sanitization Steps

Network Settings:
- For VPC, choose ...LabVpc.
- For Subnet, choose the subnet in the us-east-1a Availability Zone
- Made a new Security group and named it "Security-Group-Lab"
- Typed "HTTP Security Group" in the description
- Choose "HTTP" for the type to allow inbound HTTP traffic to the webserver
Disk Sanitization Steps Disk Sanitization Steps

In the Configure storage section, for Root volume, choose gp2 from the dropdown menu.
Disk Sanitization Steps

This user data script launches a web server, using port 80, to display internal information about the instance. I uploaded this script in the user data field to automate webserver configuration. (The screenshot of the script doesn't show its entirety).
Disk Sanitization Steps
Disk Sanitization Steps

Instance is successfully launched!
Disk Sanitization Steps

Selected “view all instances” to view the instance I just created & copied the IPv4 DNS (ec2-54-86-74-204.compute-1.amazonaws.com) to load this:
Disk Sanitization Steps Disk Sanitization Steps

Launched the 2nd instance from using an image of the one I previously made:
Disk Sanitization Steps

Only a few changes are made. I changed the name of this server to seperate it by name from the other. I changed the subnet to us-east-1b to give the client the availability and reliability they were looking for by launching new webserver in the cloud.
Disk Sanitization Steps Disk Sanitization Steps

Completed launch of the 2nd EC2 instance and verified that it was up and running.
Disk Sanitization Steps Disk Sanitization Steps Disk Sanitization Steps

Now the Island's stabilization system is more reliable and avaible than ever before!