DEV Community: deepika n

AWS 101 Workshop

deepika n — Mon, 31 Mar 2025 16:56:31 +0000

AWS 101 Workshop: A Beginner’s Guide to Cloud Computing

Introduction

In today’s digital era, cloud computing is revolutionizing the way businesses and individuals store, manage, and process data. Amazon Web Services (AWS) is one of the leading cloud platforms, offering a wide range of services to help users build scalable and secure applications. In this AWS 101 Workshop, we will explore the fundamentals of AWS, its core services, and how to get started with cloud computing.

What is AWS?

AWS (Amazon Web Services) is a cloud computing platform that provides on-demand computing resources, storage, and networking capabilities. It eliminates the need for physical infrastructure, offering cost-effective and scalable solutions for businesses of all sizes.

Why Learn AWS?

High Demand: AWS skills are in high demand in the IT industry.
Cost-Effective: Pay-as-you-go pricing reduces upfront investment.
Scalability: Easily scale applications as per business needs.
Security: AWS provides robust security features to protect data.

Core AWS Services Covered in This Workshop

1. Compute Services

Amazon EC2 (Elastic Compute Cloud): Virtual servers in the cloud.
AWS Lambda: Serverless computing for running code without provisioning servers.

2. Storage Services

Amazon S3 (Simple Storage Service): Scalable object storage.
Amazon EBS (Elastic Block Store): Persistent block storage for EC2.

3. Database Services

Amazon RDS (Relational Database Service): Managed relational databases.
Amazon DynamoDB: NoSQL database for high-speed applications.

4. Networking & Security

Amazon VPC (Virtual Private Cloud): Securely isolates AWS resources.
AWS IAM (Identity and Access Management): Controls user access.

Hands-on Activities

Setting up an AWS free-tier account.
Launching and managing an EC2 instance.
Hosting a static website on Amazon S3.
Configuring IAM roles and permissions.

Best Practices for AWS Beginners

Understand the Shared Responsibility Model: AWS secures the infrastructure, while users must manage data security and compliance.
Use IAM Roles: Grant only necessary permissions to users and applications.
Leverage Auto Scaling: Automatically adjust resources based on demand.
Monitor with AWS CloudWatch: Track application performance and security.

Conclusion

AWS is a powerful cloud platform that enables businesses and developers to build scalable and secure applications. By participating in this AWS 101 Workshop, you will gain a foundational understanding of AWS services and hands-on experience with cloud computing. Start your cloud journey today and explore the endless possibilities AWS offers!

3 Tire Architecture

deepika n — Fri, 24 Jan 2025 17:24:04 +0000

*****Here is the 3 tire archietecture diagram*

Components

Internet Gateway (Iaas): Enables the VPC to communicate with the internet, facilitating public access to resources in the Web Tier.

Elastic Load Balancer (ELB) (Iaas): Distributes incoming traffic across multiple EC2 instances in the Web Tier for fault tolerance and scalability.

Web Tier (Amazon EC2 - Public Subnet): Hosts web servers accessible over the internet, providing the first layer for user interaction.

App Tier (Amazon EC2 - Private Subnet): Runs the business logic and processes data securely, isolated from direct internet access.

Database Tier (Amazon Aurora Primary DB - Private Subnet): Manages the primary relational database in a secure environment, handling read/write operations.

Aurora Read Replica - Private Subnet: Provides read-only replicas to offload traffic from the primary database, ensuring high availability.

AZ1 & AZ2: Represent Availability Zones for high availability and redundancy across isolated data centers.

VPC (Virtual Private Cloud): Isolates and organizes the resources into subnets for security and control.

Public Subnet: Subnet exposed to the internet, hosting resources like web servers that need public access.

Private Subnet: Subnet restricted from internet access, used for resources like app servers and databases for enhanced security.

Part-1:

Step1: Create a S3 bucket

go to github and download the aws 3 tire archietecture zip file

Step2: Create IAM Role

Attach the following policies

AmazonS3ReadOnlyAccess
AmazonSSMManagedInstanceCore

Part-2

Step3: Create a new VPC

Step 4: Create Subnets
You have to create 6 subnets in total.. 2 public subnets for 2 AZs and 2 private subnets 2 AZs and 2 DB subnets for 2 AZs

each with 10.0.0.0/24 , 10.0.1.0/24 , 10.0.2.0/24 ,...10.0.5.0/24

Step 5: Create a Internet Gateway
In order to give internet access to Public subnets Create internet gateway and attach the created VPC to the internet gateway

Step 6: Create 2 NAT gateway for each availability zones
In order to provide our instances in app layer private subnet to access the internet, Create a NAT gateway

Step 7: Create separate route table for Public subnets, and 2 Private subnets in each availability zones and connect it to the internet gateway

Step 8: After connecting the internet gateway with the route table for the AZs1 then connect the public subnet with the route table.

After completing this create the same for private subnet..

Step 9: Go to security groups and create 5 security groups
SG1: create this for the public, internet facing load balancer.(HTTP, MyIP)
SG2: create this for the public instances(web tier) in the web tier. (HTTP, Internet facing load balancer)
SG3: Create this for internal load balancer.(HTTP,web tier)
SG4: Configure this for the private instances (TCP-port 4000 MyIP , Internal load balancer)
SG5: Configure this for private database table (MYSQL / Aurora

Step 10: Create DataBase
Go to RDS -> Create DB Subnet group with the VPC we have created -> select the chosen Subnet and the AZs -> Create DB Subnet

Now navigate to create database and select the following options

Standard Create
Amazon MySQL Compatible
Dev/Test
Credentials - self managed
Aurora Standard
db.t3.medium
Select the Vpc
Select DBSG from existing security group

Now Select Create Database

After creating the Database Select view credentials in the pop up and copy the username, password and endpoint in the notepad

Part 4

Create an EC2 instance

Connect -> Session manager -> Connect

A page like this will be shown

Run the following command in the connected session
sudo -su ec2-user
ping 8.8.8.8
sudo yum install mysql -y
mysql -h CHANGE-TO-YOUR-RDS-ENDPOINT -u CHANGE-TO-USER-NAME -p
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 INTO transactions (amount,description) VALUES ('400','groceries');
SELECT * FROM transactions;
Then terminate mysql by "exit" command

DOWNLOAD THE ENTIRE CODE FROM THE GITHUB REPO AND UPLOAD THE FILES INTO YOUR S3 BUCKET AND CLICK UPLOAD
Again go back to your SSM Manager Session and run the following commands
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
cd ~/
aws s3 cp s3://BUCKET_NAME/app-tier/ app-tier --recursive
cd ~/app-tier
npm install
pm2 start index.js
pm2 list
pm2 logs
pm2 startup
pm2 save
curl http://localhost:4000/health
"This is the health check"
curl http://localhost:4000/transaction
{"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"}]}

Part 5

Go to ec2 instance dash board in that select the web tier instance that we have created earlier now,
Click the instance
Actions
select images and templates
Create image

Create Target group for the same

Now go to the load balancer page and click create load balancer. This is a internal load balancer for 2 private subnets in 2 AZ

And create the launch template

Create Auto scaling group with maximum minimum and desires capacities as 2,2,2 respectively

Part - 6

Modify the nginx.conf file by replacing the placeholder [INTERNAL-LOADBALANCER-DNS] with your internal load balancer's DNS name.
DEV Community

Upload the updated nginx.conf and the web-tier folder to your designated S3 bucket.

Now launch a new instance and go to the session manager of the particular ec2 instance
execute the following commands
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
source ~/.bashrc
nvm install 16
nvm use 16
cd ~/
aws s3 cp s3://BUCKET_NAME/web-tier/ web-tier --recursive
cd ~/web-tier
npm install
npm run build
sudo amazon-linux-extras install nginx1 -y
cd /etc/nginx
sudo rm nginx.conf
sudo aws s3 cp s3://BUCKET_NAME/nginx.conf .
sudo service nginx restart
chmod -R 755 /home/ec2-user
sudo chkconfig nginx on

Part 7

After configuring your web tier instance:
Go to EC2 Dashboard → Instances.
Select your web instance → Actions → Image → Create Image.
Give it a name and description.
Click Create Image.

Go to Target Groups → Click Create target group.
Choose Target type: Instances.
Name your group (e.g., web-tier-tg).
Protocol: HTTP, Port: 80, VPC: Your VPC.
Health check path: /health or / depending on your app.
Skip registering targets for now.
Click Create.

Navigate to Load Balancers → Create Application Load Balancer.
Name: web-tier-lb.
Scheme: internet-facing.
Listener: HTTP (port 80).
Select VPC and public subnets.
Attach a security group that allows inbound HTTP (port 80).
Under Target group, choose the one you created in step 2.
Review and Create.

Go to Launch Templates → Click Create launch template.
Name: web-tier-template.
AMI ID: Choose the one created in Step 1.
Instance type: t2.micro (or your preferred).
Attach key pair, IAM role, and correct security group.

Go to Auto Scaling Groups → Create Auto Scaling group.
Use the launch template from step 4.
Name: web-tier-asg.
VPC: Select your VPC and public subnets.
Attach it to the target group from step 2.
Configure scaling policies:
Desired: 2
Min: 1
Max: 3
Skip notifications for now and Create.

Hit the DNS name of the load balancer. You will be able to see the output as follows

EC2 + S3 + IAM

deepika n — Thu, 23 Jan 2025 16:01:54 +0000

Create an EC2 Instance
Go to Ec2 in AWS Console
Click Instance
Launch Instance

Provide Instance name

Choose Amazon Linux

Select t2.micro as Instance type

Create a new key pair and download the pem file
Scroll to the bottom of the page and click launch instance

Now a page will show the available running instances
Select the instance
Go to security

Scroll down and there will be Inbound rules

Click on edit inbound rules and select Custom and that will show a dropdown and Select MyIP

Click on Save Changes

Now install Putty in your Laptop and open it

Follow these steps

Connection -> ssh -> Auth -> Credentiels

click on browse and paste the ppk file .

(if it is formated as pem convert it into ppk using puttygen.)

Select accept and the page will show "Login as" type "ec2-user"

Your Terminal gets opened in that just create a file and add some contents in it.

Command to create a file

cat < "file_name.txt"

To view the content in the file

cat "file_name.txt"

Now Go to AWS Console , IAM -> Roles -> Create Role

This role will have S3 full access

You can view your Roles as in the image below

Go to EC2 instance and select the instance

Actions -> security -> Modify IAM Role

Now select the created IAM role in the dropdown and update IAM role

Go to the terminal, we need to put the created file in the AWS S3 so enter the command

aws s3 cp "file_name.txt s3://"bucket_name"

If there is no bucket in the S3 then create it by using the command.

aws s3 mb s3://"bucket_name"

After creating it upload the created file in the bucket by using the command.

aws s3 cp "file_name.txt s3://"bucket_name"

After uploading the files go check your AWS console to verify

Completing every steps terminate all the services (EC2, S3, IAM role)

Static Webpage Hosting (S3 + Cloud front) - React app

deepika n — Thu, 23 Jan 2025 09:08:32 +0000

Check if the requirements like npm and node are installed in your system
if it is preinstalled check for the version as given below

Now run a command npm install -g create-react-app

Now run a command npm create vite@latest

Now run the following commands:

cd Deepika react

npm install

npm run dev

By following the link that has been generated we will be redirected to this page

Now create a S3 Bucket
Amazon S3 -> Bucket -> Create Bucket
Provide a unique bucket name as mentioned below

Block Public Access

Now Click Create bucket

Click the bucket and Enable static webpage hosting

Edit the buckect policy

Now go to the dist folder and upload the filea and folders separately
and them one by one

Now you can view the index.html file and the output is as shown below

Link :
http://deepikan714022202017.s3-website-us-west-2.amazonaws.com

Open cloud front and create a Distribution

The Cloud front output is as shown blow

Cloudfront Link:
https://d9cod4fas679p.cloudfront.net/

AWS OpsWorks

deepika n — Wed, 22 Jan 2025 17:57:00 +0000

Overview: AWS OpsWorks

Logo:

One line Description: Simplify Configuration Management and Application Deployment with AWS OpsWorks

Key Features:

Managed Configuration Management:
Automate infrastructure and application configurations using Chef and Puppet, without managing the control servers yourself.

Customizable Deployment:
Tailor deployments to fit your exact requirements with stacks, layers, and lifecycle event hooks.

Integration with AWS Services:
Seamlessly integrate with Amazon EC2, RDS, and other AWS services to manage resources across your infrastructure.

Dynamic Scaling:
Automatically scale resources based on usage patterns, helping optimize costs and performance.

Built-in Monitoring:
Leverage Amazon CloudWatch integration to monitor instances and applications in real time.

Support for On-Premises Servers:
Extend OpsWorks to manage servers in on-premises data centers alongside your cloud resources.

Technical Specifications:

Regions Supported: Available in most AWS regions globally.

Data Durability: Ensures configurations are reliably applied with built-in Chef and Puppet capabilities.

Request Limits: Scalable to manage thousands of nodes and servers efficiently.

Use Cases:

Web Application Deployment: Automate the setup, deployment, and scaling of web applications on EC2 instances.

Server Configuration Management: Use Chef or Puppet to enforce configuration compliance across multiple environments.

Hybrid Cloud Management: Manage a mix of on-premises and cloud servers using a unified toolset.

Auto-Healing Systems: Automatically replace or reconfigure failed resources to maintain uptime.

Pricing Model:

AWS OpsWorks follows a pay-as-you-go pricing model based on:

Number of Nodes: Pricing varies based on the number of managed instances.

Data Transfer: No additional charge for data transferred within a region.

Control Server Costs: AWS covers the cost of running control servers for Chef Automate or Puppet Enterprise.

Comparison with Similar Services:

AWS Systems Manager:
OpsWorks: Focuses on Chef and Puppet for configuration management.
Systems Manager: Offers a broader suite for operational management, including patch management, compliance, and automation.
Ansible:
OpsWorks: Managed service requiring no setup of control nodes.
Ansible: Open-source, but requires users to manage their control servers and environments.

Benefits and Challenges:

Benefits:

Simplified Management: AWS handles the Chef/Puppet control servers, reducing operational overhead.
Flexibility: Supports custom Chef recipes and Puppet manifests.
Cost-Effective: Only pay for resources you use.

Challenges:

Learning Curve: Requires familiarity with Chef or Puppet scripting.
Limited Customization Beyond Supported Features: Users may face constraints when trying to integrate unsupported configurations.

Real-World Example:

Company: Pinterest
Challenge:
Pinterest, a popular visual discovery and social media platform, needed to manage a large-scale infrastructure to support millions of users and ensure a smooth experience for users across the globe. They required a solution to automate application deployments, scale resources efficiently, and ensure consistent server configurations.

Solution:
Pinterest adopted AWS OpsWorks to automate server configurations and manage application deployments. By using Chef, Pinterest streamlined their infrastructure management, enabling them to quickly deploy updates and scale their platform as needed.

AWS OpsWorks is an ideal choice for businesses looking to simplify infrastructure management while leveraging the power of Chef or Puppet for configuration automation. Whether managing a few servers or thousands of nodes, OpsWorks offers scalability, flexibility, and integration to streamline operations.