DEV Community: Harinivas. M

AWS 101 Workshop

Harinivas. M — Mon, 31 Mar 2025 15:58:04 +0000

My AWS 101 Workshop Experience

I recently attended the AWS 101 Workshop, which provided a hands-on introduction to Amazon Web Services (AWS) and cloud computing. It was a great opportunity to explore core services like EC2, S3, and RDS, and understand how AWS offers scalable and secure solutions.

Workshop Overview

The session covered cloud computing basics, demonstrating how AWS helps businesses reduce costs and scale globally. Through real-world examples and hands-on labs, I learned how to launch servers, manage storage, and simplify databases using AWS services.

Key Takeaways

Practical Experience: Hands-on labs enhanced my understanding of AWS services.
Cloud Infrastructure: Gained insight into AWS's scalable infrastructure.
Storage Management: Learned secure data management using Amazon S3.
Database Management: Explored simplified database management with Amazon RDS.
Networking and Security: Understood AWS security with VPCs and IAM policies.

Interactive Learning Environment

The instructors were supportive, making complex topics accessible. The collaborative setup fostered discussions and networking, offering opportunities to learn from peers and AWS professionals.

Why You Should Attend

The AWS 101 Workshop boosted my confidence in using AWS for projects and inspired me to pursue further certifications. For anyone interested in cloud computing, this workshop provides essential knowledge and practical experience to get started.

AWS - 3 tier Architecture implementation

Harinivas. M — Mon, 31 Mar 2025 14:28:11 +0000

1. Clone GitHub Repository:

git clone https://github.com/Naveen3251/AWS_3Tier.git

2. Create an S3 Bucket:

Go to the AWS Console → S3 → Create Bucket.
Provide a unique name and choose a region.

3. Create an IAM Role:

AWS Console → IAM → Roles → Create Role.
Select EC2 as the trusted entity.
Add policies: AmazonSSMManagedInstanceCore, AmazonS3ReadOnlyAccess.

4. Create a VPC and Subnets:

AWS Console → VPC → Your VPCs → Create VPC.
Create 6 subnets (2 public, 2 app layer private, 2 database private) across different availability zones.

5. Set Up Networking:

Internet Gateway: Create and attach to the VPC for public access.
NAT Gateway: Deploy in each public subnet for private subnet access.
Route Tables: Configure routes to link subnets to the appropriate gateways.

6. Configure Security Groups:

Public Load Balancer: Allow HTTP from your IP.
Web Tier Instances: Allow HTTP from the load balancer and your IP.
Internal Load Balancer: Allow HTTP from web tier instances.
App Layer: Allow TCP on port 4000 from the internal load balancer.
Database: Allow MySQL traffic (port 3306) from app layer instances.

7. Create a Subnet Group for RDS:

AWS Console → RDS → Subnet Groups → Create.
Add the database subnets.

8. Deploy RDS:

AWS Console → RDS → Databases → Create Database.
Choose Amazon Aurora (MySQL-Compatible) → Dev/Test.
Select the VPC, subnet group, and database security group.
Enable Multi-AZ for high availability.
Save the writer endpoint for database connection.

9. Deploy App Instance:

Navigate to AWS Console → EC2 → Instances → Launch Instances.
Choose Amazon Linux 2 AMI and select the t2.micro instance type.
Configure instance details:
- Select the appropriate VPC and private subnet for the app layer.
- Assign the IAM role created earlier.
- Attach the security group designated for the app layer.
Launch the instance without a key pair, as EC2 Instance Connect will be used.

10. Connect to the Instance:

In the EC2 dashboard, select the running instance.
Click 'Connect' and choose the 'Session Manager' tab to initiate a session.
Switch to the ec2-user:

  sudo -su ec2-user

Verify internet connectivity through the NAT gateway:

  ping 8.8.8.8

11. Configure the Database:

Install the MySQL client:

  sudo yum install mysql -y

If issues arise, refer to alternative installation commands in the source article.

Connect to the Aurora RDS writer endpoint:

  mysql -h [RDS_ENDPOINT] -u [USERNAME] -p

Create the webappdb database and transactions table:

  CREATE DATABASE webappdb;
  USE webappdb;
  CREATE TABLE IF NOT EXISTS transactions(
      id INT NOT NULL AUTO_INCREMENT,
      amount DECIMAL(10,2),
      description VARCHAR(100),
      PRIMARY KEY(id)
  );
  INSERT INTO transactions (amount, description) VALUES ('400', 'groceries');
  SELECT * FROM transactions;

Exit the MySQL client:

  exit

12. Configure the App Instance:

Update the DbConfig.js file in the app-tier directory with database credentials.
Upload the app-tier folder to the previously created S3 bucket.
Install Node Version Manager (NVM):

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

Install Node.js and set it as the active version:

  nvm install 16
  nvm use 16

Install PM2 globally:

  npm install -g pm2

Download the application code from S3:

  aws s3 cp s3://[BUCKET_NAME]/app-tier/ ~/app-tier --recursive

Navigate to the application directory, install dependencies, and start the application:

  cd ~/app-tier
  npm install
  pm2 start index.js

Configure PM2 to start on system boot:

  pm2 startup
  # Execute the command output by the above command
  pm2 save

13.Create an App Tier AMI:

AWS Console → EC2 → Instances.
Select the configured app instance → Actions → Image and templates → Create Image.
Provide a name and description, then create the image.

14.Set Up a Target Group:

AWS Console → EC2 → Target Groups → Create Target Group.
Select "Instances" as the target type, name the group, set protocol to HTTP and port to 4000.
Choose the appropriate VPC and set the health check path to /health.

15.Deploy an Internal Load Balancer:

AWS Console → EC2 → Load Balancers → Create Load Balancer.
Choose "Application Load Balancer," name it, and select "Internal."
Configure the network settings, assign the appropriate security group, and link it to the previously created target group.

16.Create a Launch Template:

AWS Console → EC2 → Launch Templates → Create Launch Template.
Name the template and select the App Tier AMI.
Choose the instance type, assign the appropriate security group, and specify the IAM instance profile.

17.Configure Auto Scaling:

AWS Console → EC2 → Auto Scaling Groups → Create Auto Scaling group.
Name the group, select the launch template, and configure the VPC and subnets.
Attach the Auto Scaling group to the internal load balancer's target group.
Set the desired, minimum, and maximum capacities, then create the Auto Scaling group.

18.Update NGINX Configuration:

Edit the nginx.conf file from the application-code directory.
Replace [INTERNAL-LOADBALANCER-DNS] with your internal load balancer's DNS name.
Upload the updated nginx.conf and the web-tier folder to your S3 bucket.

19.Deploy Web Instances:

Launch a new EC2 instance using the Amazon Linux 2 AMI.
Assign it to the appropriate VPC and public subnet, enabling auto-assign public IP.
Attach the previously created IAM role and security group for the web tier.

20.Configure the Web Instance:

Connect to the instance via the AWS Console's Session Manager.
Install Node Version Manager (NVM) and Node.js:

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

Download the web-tier code from your S3 bucket:

  aws s3 cp s3://YOUR_BUCKET_NAME/web-tier/ ~/web-tier --recursive

Navigate to the web-tier directory, install dependencies, and build the React app:

  cd ~/web-tier
  npm install
  npm run build

Install and configure NGINX:

  sudo amazon-linux-extras install nginx1 -y
  sudo rm /etc/nginx/nginx.conf
  sudo aws s3 cp s3://YOUR_BUCKET_NAME/nginx.conf /etc/nginx/
  sudo service nginx restart
  chmod -R 755 /home/ec2-user
  sudo chkconfig nginx on

21.Create a Web Tier AMI:

Navigate to EC2 Dashboard → Instances.
Select your web tier instance, then Actions → Image and templates → Create Image
Provide a name and description, then click Create image. Monitor the creation status under AMIs.

22.Set Up a Target Group:

Go to EC2 Dashboard → Target Groups under Load Balancing. Click Create Target Group.
Choose Instances as the target type, assign a name, set the protocol to HTTP and port to 80.
Select your VPC and set the health check path to /health. Click Next, then Create target group without registering any targets.

23.Deploy an Internet-Facing Load Balancer:

Navigate to EC2 Dashboard → Load Balancers. Click Create Load Balancer.
Select Application Load Balancer, provide a name, and choose Internet-facing.
Configure the network settings with your VPC and public subnets.
Assign the appropriate security group.
Set the listener to HTTP on port 80, forward to the previously created target group, and click Create load balancer.

24.Create a Launch Template:

Go to EC2 Dashboard → Launch Templates. Click Create Launch Template.
Name the template, select the web tier AMI, and choose the instance type (e.g., t2.micro).
Assign the web tier security group and specify the IAM instance profile used for EC2 instances.

25.Configure Auto Scaling:

Navigate to EC2 Dashboard → Auto Scaling Groups. Click Create Auto Scaling group.
Name the group, select the launch template, and configure the VPC and public subnets for the web tier.
Attach the Auto Scaling group to the previously created target group.
Set the desired, minimum, and maximum capacity to 2.
Review and create the Auto Scaling group.

Final Conclusion

AWS 3-tier architecture ensures a scalable, secure, and efficient application deployment using S3, EC2, and RDS. It enhances security with proper VPC segmentation, NAT, and Internet Gateways. Load balancers and Auto Scaling provide high availability and fault tolerance. IAM roles and security groups ensure controlled access. This setup is ideal for managing applications with dynamic workloads.

Final Output

AWS - HealthLake

Harinivas. M — Mon, 31 Mar 2025 12:59:53 +0000

AWS HealthLake: Transforming Healthcare Data Management

AWS HealthLake is a HIPAA-eligible service that empowers healthcare organizations to store, analyze, and extract insights from structured and unstructured health data. It offers seamless data management using the Fast Healthcare Interoperability Resources (FHIR) standard.

Key Features

FHIR Support: AWS HealthLake automatically structures health data using the FHIR standard, ensuring interoperability.
Data Transformation: Easily import, store, and transform health data from various sources.
Advanced Analytics: Integrates with AWS AI/ML services to derive actionable insights from data.
Secure & Compliant: Designed for healthcare data, supporting HIPAA and other compliance regulations.
Real-time Search & Query: Provides robust search capabilities using Amazon OpenSearch Service.

Use Cases

Clinical Insights: Extract meaningful insights from patient data to enhance diagnostics and treatment plans.
Population Health Management: Analyze large datasets to identify trends and manage population health effectively.
Medical Research: Accelerate research with secure access to historical and real-time healthcare data.

Getting Started with AWS HealthLake

Create a HealthLake Data Store: Set up your FHIR-compatible data store using the AWS Management Console.
Import Data: Ingest data from various systems including EHRs, medical devices, and insurance providers.
Analyze Data: Leverage Amazon SageMaker and AWS AI/ML services to derive insights.
Visualize Results: Use Amazon QuickSight to create interactive dashboards and reports.

Final Thoughts

AWS HealthLake is a game-changer for healthcare providers, researchers, and insurers, offering a scalable and compliant platform to manage and analyze healthcare data efficiently.

Copying a file from Ec2 to S3 using PuTTy software

Harinivas. M — Thu, 23 Jan 2025 13:44:32 +0000

1.Download Putty software with proper version

2.Install the Putty software

3.Create a EC2 instances
Update the security group inbound rules.

4.Using puTTygen
key pair to convert .perm file to .ppk file

5. Create a S3 bucket

6. connect to PuTTy software and create a file called details.txt print the content in echo "helloworld" in details.txt.

7. Create roles in IAM and change the IAM role in instances, then the go to PuTTy and type aws s3 ls, it will show the S3 buckets.

8. We need to add previous details.txt file to s3 .so, we use aws s3 cp details.txt s3://(bucket name)/

9.Go and verify it, In s3 files is uploaded finally.

10. Cost Management
More amount of cost will be used at the time of roles and instances, so we can delete the created things.

Flowchart Diagram :

Deploying a Static website using AWS (S3+cloudfront)-React App

Harinivas. M — Thu, 23 Jan 2025 08:52:46 +0000

1. Install the react app

2. create the react app

i. open the terminal and check the all prerequisites are installed or not, if not installed make sure install it.
ii. check the version of the node.js and npm.
iii. npx create vite@latest
iv. create a project name.
v. then run commands like - cd (project name) -> npm install -> npm run dev.
vi. finally the normal static website hosted.

3. Create a S3 bucket in AWS console

i. then change the permission of static hosting into enable state.
ii. create a bucket policy using policy generator.
iii. add the objects like (files and folders) in S3.
iv. go to properties in last and link will be shown , click the link to host the file in S3.

Link for website : http://node-22.s3-website-us-east-1.amazonaws.com

4. Hosting a website in CloudFront

i. create a distribution
ii. select the origin
iii. select the WAF for the security purpose.
iv. finally the distribution is created.

v. Once the distribution is deployed, we can able to host it.
vi. copy the DNS and paste the DNS in New tab for hosting a website.
vii. Finally the website is hosted successfully.

5. Cost management

More amount of cost will be there for the CloudFront so we should delete the distribution after the final work done.

Flowchart Diagram:

AWS Honeycode

Harinivas. M — Wed, 22 Jan 2025 17:21:47 +0000

1. Service overview

Service Name : AWS Honeycode
Logo :

Tagline or One-Line Description: Build Web & Mobile Apps Without Writing Code.

2. Key Features

Top Features:

No code development.
Spreadsheet-Like Data Management.
Automation.
Multi-Platform Deployment.
Collaboration.

Technical Specifications:

AWS services like Amazon S3, which offers 11 nines (99.999999999%) of durability.
Honeycode supported integration with AWS services and third-party apps via APIs and Zapier connectors.

3. Use case

Real-Life Applications : Project Management

Project Management :Track tasks, milestones, and deadlines for team projects, allowing teams to stay organized and meet deadlines efficiently.

4. Pricing Model

Pricing Overview: Honeycode follows a tiered pricing model based on the number of users and the usage of app features.

Free Tier: Includes up to 20 users with limited features, ideal for small teams or personal use.

Paid Tier: Billed per user, with additional costs for premium features such as advanced automation, integration, and more extensive data storage.

Add-Ons: Charges for features like external integrations, increased storage, and higher API usage.

5. Comparison with Similar Services

Competitors or Alternatives: Honeycode stands out for its seamless AWS integration, while competitors like AppSheet, PowerApps, and Airtable offer similar functionality with different focuses.

6. Benefits and Challenges

Advantages & Limitations :Honeycode is easy to use and integrates well with AWS but has a learning curve and limited advanced features.

7. Case study

GoPro uses Honeycode to streamline workflows and enhance team collaboration.