AWS Hands on Labs: Step-by-step for Beginners *NEW*

Build two web servers in us-east-1 across two availability zones in public subnets of a VPC, and load balance internet traffic with an application load balancer to improve fault tolerance.

Learn to create a custom VPC in AWS by configuring a 10.0.0.0/16 CIDR block, understanding regions and availability zones, and enabling DNS hostnames for resources.

Create and attach an internet gateway to a custom VPC to enable IPv4 and IPv6 internet access for instances, and update the route table to forward 0.0.0.0/0 to the gateway.

Create public subnets in a VPC across two availability zones with IPv4 CIDR blocks 10.0.1.0/24 and 10.0.2.0/24. These subnets auto-associate with default route table and default network ACL.

Launch two EC2 instances in separate availability zones using an amazon linux image, enable public ip addresses, and run a bash script to install apache and serve a basic index.html.

Create an application load balancer to evenly distribute http traffic across two EC2 instances in two availability zones, register them to a target group, and verify health checks and failover.

Delete the load balancer, then delete the target group, terminate the two web server instances, and verify on the EC2 dashboard that no instances or load balancers remain.

Prepare for lab two by reviewing your VPC resources and updating EC2 security group rules for ALB HTTP traffic, adding SSH access, and enabling auto-assign IP on public subnet 1a.

Design and validate a VPC with two public subnets and default NACL and route table, then create an application load balancer and a target group for HTTP traffic, internet facing.

Create a standard SNS topic named MyTopic, configure an email subscription, and confirm it to receive notifications, illustrating topics, subscriptions, and common endpoints in AWS.

Create an EC2 auto-scaling group using a launch template to deploy two web servers behind an application load balancer, with target tracking at 40% CPU and SNS alerts.

Learn to log into an AWS EC2 instance via SSH with PuTTY, convert PEM to PPK, install EPEL, run stress to simulate CPU load, and prepare for auto scaling tests.

Learn how Amazon CloudWatch monitors EC2 instances, auto scaling groups, and load balancers, configure alarms, and test dynamic scaling from two to three instances with a CPU stress scenario.

Delete the auto scaling group, launch template, and load balancer in the aws ec2 console, then remove the target group and sns topic and subscription, verifying all instances are terminated.

Design a secure, fault-tolerant architecture with web servers in two private subnets across two availability zones, using NAT gateway, Bastion host, an application load balancer, and an S3 gateway endpoint.

Prepare for lab 3 by reviewing and reusing existing resources from lab 2, including a custom VPC, two public subnets, default route table, and SSH key pair in AWS console.

Create private subnets in both availability zones and configure a private route table. Associate private subnets with the private route table and connect public subnets to the public route table.

Deploy a bastion host to securely access Linux instances in private subnets via a jump box, using security groups that permit ssh from the internet to the bastion.

Learn to create an internet-facing application load balancer across two availability zones to route HTTP traffic to two private subnets Apache web servers, with a target group and health checks.

Create an S3 bucket, an IAM role for EC2, and a VPC gateway endpoint for S3 to enable private access; test uploading and downloading files via the endpoint.

Review the preexisting VPC setup, including two public and two private subnets, route tables, and internet gateway. Verify EC2 and ALB security groups and the SSH key for lab 4.

Launch a MySQL RDS instance in a VPC, configure a DB subnet group across private subnets, set up security groups and automated backups, and explore multi-AZ and read replicas.

Log into a web server, download a php app from git, configure rds endpoint and db name, and create an ami to deploy a second web server in another az.

Create an application load balancer and a target group to distribute traffic between two web server instances, ensure healthy Apache servers, and test PHP application via the load balancer DNS.

Enable multi-az deployment by snapshotting the primary to us east 1b with synchronous replication, and verify failover by rebooting the primary while the endpoint remains the same.

Clean up aws resources by deleting the rds db instance and subnet group, terminating ec2 instances, deregistering the ami, and removing the load balancer, target group, security groups, and vpc.

Conclude this beginner AWS hands-on labs course and reflect on your learning. Share feedback and future topic ideas to guide upcoming courses, and pursue AWS certification with ample hands-on practice.