Forem: Sudarshan Yadav

📅 Day 22 | AWS DynamoDB — Serverless NoSQL Database in AWS ⚡☁️

Sudarshan Yadav — Thu, 25 Dec 2025 07:59:10 +0000

# 📅 Day 22 | AWS DynamoDB — Serverless NoSQL Database in AWS ⚡☁️

Today, I learned about AWS DynamoDB, a fully managed, serverless, NoSQL database service designed to provide fast and predictable performance with seamless scalability.

DynamoDB is a key-value and document database that delivers single-digit millisecond performance at any scale. It’s a favorite for DevOps and Cloud Engineers because it removes the administrative burden of operating and scaling distributed databases.

⚡ AWS DynamoDB – DevOps Explanation

What is AWS DynamoDB?

AWS DynamoDB is a Serverless NoSQL Database that allows you to store and retrieve any amount of data and serve any level of request traffic.

Unlike relational databases (RDS), DynamoDB is non-relational, meaning it doesn't use fixed schemas or complex joins. AWS handles the:

Hardware provisioning
Setup and configuration
Replication and software patching
Cluster scaling

Why DevOps Engineers Use DynamoDB

DynamoDB is the go-to choice when:

You need extreme scale (millions of requests per second)
You require consistent low latency (single-digit milliseconds)
You want a serverless architecture (no instances to manage)
You need global availability (Global Tables)

Core Concepts (The Fundamentals)

Tables: Similar to a table in SQL, but with no fixed schema.
Items: Similar to a "row." Each item is a collection of attributes.
Attributes: Similar to a "column." Can be strings, numbers, binaries, or even JSON (Maps/Lists).
Primary Key: Must be defined at creation. It consists of:
- Partition Key (PK): Used for internal data distribution.
- Sort Key (SK): (Optional) Used to sort data within a partition.

DynamoDB Features & Architecture

High Availability: Data is automatically replicated across three Availability Zones (AZs) within a region.
Read Consistency: * Eventually Consistent (Default) – Best performance, lowest cost.
- Strongly Consistent – Returns the most up-to-date data.
DynamoDB Streams: Captures item-level changes (Insert/Update/Delete) and triggers AWS Lambda—perfect for event-driven apps.
TTL (Time to Live): Automatically deletes expired items to reduce storage costs.

Capacity Modes (How you pay)

On-Demand: You pay per request. Best for unpredictable workloads or new apps.
Provisioned: You specify RCU (Read Capacity Units) and WCU (Write Capacity Units). Best for predictable traffic and cost control (supports Auto Scaling).

Indexing for Performance

Since you can only query by Primary Key, you use Indexes to query other attributes:

Local Secondary Index (LSI): Same Partition Key, different Sort Key. (Must be created with the table).
Global Secondary Index (GSI): Different Partition Key AND different Sort Key. (Can be created anytime).

Security in DynamoDB

IAM: Control who can read/write to specific tables.
Encryption at Rest: All data is encrypted by default using AWS KMS.
VPC Endpoints: Keep traffic within the AWS network (Gateway Endpoint).
Fine-Grained Access Control: Using IAM policies to restrict access to specific items or attributes.

Common Use Cases

Serverless Apps: Paired with AWS Lambda and API Gateway.
Session Management: Storing user sessions for web applications.
Gaming: Storing leaderboards and player profiles.
IoT: Ingesting massive amounts of sensor data.

Advantages

No Servers to Manage: Zero operational overhead.
Auto-Scaling: Grows and shrinks based on traffic.
Enterprise Grade: Supports ACID transactions and 99.999% availability with Global Tables.
Performance at Scale: Latency does not increase as the database grows.

Limitations

No Joins: You must model data to avoid needing joins.
Query Limitations: You cannot perform complex SQL-like queries easily.
Item Size: Maximum size per item is 400 KB.

Interview One-Line Answer

AWS DynamoDB is a fully managed, serverless NoSQL database that provides consistent, single-digit millisecond latency at any scale. It supports both document and key-value data models, offers built-in security, backup/restore, and multi-region replication via Global Tables.

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity

⭐ If you like this guide, don’t forget to star the repo!

📅 Day 21 | AWS Elastic Beanstalk — Platform as a Service (PaaS) in AWS 🌱☁️

Sudarshan Yadav — Mon, 22 Dec 2025 16:47:11 +0000

📅 Day 21 | AWS Elastic Beanstalk — Platform as a Service (PaaS) in AWS 🌱☁️

Today, I learned about AWS Elastic Beanstalk, which is a fully managed Platform as a Service (PaaS) provided by AWS to deploy, manage, and scale applications automatically.

Elastic Beanstalk allows developers and DevOps engineers to focus only on application code, while AWS handles the infrastructure provisioning, scaling, load balancing, monitoring, and updates.

With Elastic Beanstalk, you can deploy applications quickly and reliably, making it a powerful service for DevOps workflows and cloud-native architectures.

🌱 AWS Elastic Beanstalk – DevOps Explanation

What is AWS Elastic Beanstalk?

AWS Elastic Beanstalk is a Platform as a Service (PaaS) that helps you deploy, manage, and scale applications automatically without worrying about the underlying infrastructure.

You just upload your application code, and Elastic Beanstalk automatically handles:

EC2 instances
Load Balancer
Auto Scaling
Monitoring
Application updates

Why DevOps Engineers Use Elastic Beanstalk

Elastic Beanstalk is useful when:

You want fast deployment
You don’t want to manage infrastructure manually
You need auto scaling + high availability
You want CI/CD friendly deployments

Elastic Beanstalk Architecture (Behind the Scenes)

When you deploy an app, Elastic Beanstalk automatically creates:

EC2 – runs your application
Auto Scaling Group – handles scaling
Elastic Load Balancer (ALB) – distributes traffic
Security Groups – network security
CloudWatch – logs & monitoring
S3 – stores application versions

You control everything, but AWS manages it for you.

How Elastic Beanstalk Works (Step-by-Step)

1. Create an Application

Logical container for your app

2. Choose Platform

Supported platforms include:

Java
Python
Node.js
.NET
PHP
Docker

3. Upload Code

ZIP file
WAR file
Docker image

4. Environment Created

Web Server Environment (most common)
Worker Environment (background jobs)

5. Application Runs

User → Load Balancer → EC2 Instances → Application

Deployment Options in Elastic Beanstalk

Important for interviews:

All at Once – Fastest, but downtime possible
Rolling – Updates instances in batches
Rolling with Additional Batch – Safer than rolling
Immutable – Zero downtime, safest
Blue/Green Deployment – Best practice for production

Configuration Options

You can customize:

Instance type
Auto Scaling rules
Environment variables
Load balancer settings
Health checks

Configuration methods:

AWS Console
AWS CLI
.ebextensions (YAML configuration files)

CI/CD with Elastic Beanstalk

Typical DevOps pipeline:

Git → Jenkins / GitHub Actions → Build → Deploy to Elastic Beanstalk

Features:

Application versioning
Rollback support
Automated deployments

Monitoring & Logs

CloudWatch metrics
Application logs
Environment health dashboard (Green / Yellow / Red)

Security in Elastic Beanstalk

IAM roles & policies
Security Groups
VPC support
SSL/TLS using ACM
Environment-level isolation

Advantages

Easy to use
Automatic scaling
Built-in load balancing
Supports multiple languages
Reduced operational overhead

Limitations

Less control than raw EC2
Not ideal for complex microservices
Slightly higher cost than manual EC2 setup

Interview One-Line Answer

AWS Elastic Beanstalk is a PaaS service that allows developers and DevOps engineers to deploy and manage applications without managing infrastructure. It automatically handles EC2, load balancing, auto scaling, monitoring, and supports multiple deployment strategies.

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity

⭐ If you like this guide, don’t forget to star the repo!

📅 Day 20 | AWS Lambda — Serverless Compute in AWS ⚡☁️

Sudarshan Yadav — Sat, 20 Dec 2025 15:51:39 +0000

📅 Day 20 | AWS Lambda — Serverless Compute in AWS ⚡☁️

Today, I learned about AWS Lambda, a serverless compute service provided by AWS that lets you run code without provisioning or managing servers.

With Lambda, you only focus on writing code, and AWS automatically handles infrastructure, scaling, and availability. You pay only for the execution time, making it highly cost-effective and scalable.

AWS Lambda is a core service in modern DevOps and cloud-native architectures.

🔹 What is AWS Lambda?

AWS Lambda allows you to run code in response to events.

You can use Lambda to:

Process files
Handle API requests
Automate tasks
Build serverless backends

Supported languages:

Python
Node.js
Java
Go
C#

🔹 Why AWS Lambda is Important in DevOps?

Lambda helps DevOps teams by:

Eliminating server management
Automatically scaling applications
Reducing infrastructure costs
Integrating easily with CI/CD pipelines
Enabling event-driven architectures

🔹 How AWS Lambda Works (Step-by-Step)

Developer writes Lambda function code
Code is uploaded to AWS Lambda
An event triggers the function (S3, API Gateway, SNS, SQS, EventBridge, etc.)
AWS creates an execution environment
Lambda runs the function
Output is returned
Logs & metrics are sent to CloudWatch

🔹 Common Lambda Triggers

Amazon S3 – file upload events
API Gateway – REST & HTTP APIs
Amazon SNS – notifications
Amazon SQS – message processing
EventBridge – scheduled jobs (cron)
DynamoDB Streams – data changes

🔹 AWS Lambda in CI/CD (DevOps Use Case)

Typical flow:

Code pushed to GitHub
CI/CD pipeline builds & tests
Lambda function deployed
Event triggers Lambda
Application executes automatically

🔹 Real-World Use Cases

Serverless APIs
Image resizing & file processing
Automation scripts
Background jobs
Microservices
Monitoring & alerts

🔹 Interview Quick Answers

What is AWS Lambda?
A serverless compute service that runs code in response to events.

Do we manage servers in Lambda?
No, AWS fully manages the infrastructure.

How does Lambda scale?
Automatically scales based on the number of requests.

How is Lambda billed?
Based on number of executions and execution time.

🔹 Summary

AWS Lambda:

Is serverless and event-driven
Scales automatically
Reduces operational overhead

* Fits perfectly into DevOps workflows

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity

⭐ If you like this post, don’t forget to react & share 🙌

Day 19 | Amazon CloudFront — Content Delivery Network (CDN) in AWS 🌍⚡

Sudarshan Yadav — Fri, 19 Dec 2025 13:18:04 +0000

📅 Day 19 | Amazon CloudFront — Content Delivery Network (CDN) in AWS 🌍⚡

Today, I learned about Amazon CloudFront, which is a fast, secure, and scalable Content Delivery Network (CDN) service provided by AWS.

CloudFront delivers web content, images, videos, APIs, and static files to users from edge locations (servers closest to users), reducing latency and improving performance.

CloudFront helps in building highly available, low-latency, and secure applications, making it an essential service in DevOps and cloud-native architectures.

Amazon CloudFront in AWS DevOps – Step-by-Step Guide

1. What is Amazon CloudFront?

Amazon CloudFront is a Content Delivery Network (CDN) service provided by AWS.

It delivers content like:

HTML
CSS
JavaScript
Images
Videos
APIs

from edge locations (servers near users) to provide low latency and high speed.

Main Goal:

Faster website performance
Reduced load on backend servers
Secure and scalable content delivery

2. Why CloudFront is Important in DevOps?

In DevOps, applications are deployed frequently and accessed globally.

CloudFront helps by:

Caching content
Improving performance
Reducing server load
Integrating with CI/CD pipelines
Providing security (HTTPS, WAF)

3. How CloudFront Works (Architecture Flow)

Request Flow:

User requests www.example.com
Request goes to the nearest CloudFront Edge Location
CloudFront checks cache:
- If content exists → serve immediately
- If not → request goes to Origin
Origin sends data to CloudFront
CloudFront caches the data and delivers it to the user
Next users get cached content faster

4. What is an Origin?

Origin is the source of original content.

Common origins:

Amazon S3
EC2 Instance
Application Load Balancer (ALB)
API Gateway

5. Key Components of CloudFront

Component	Description
Distribution	CloudFront configuration
Origin	Source of content
Edge Location	CDN server near users
Cache Behavior	Rules for caching
TTL	Cache duration
Invalidation	Clear cached content

6. Step-by-Step: Using CloudFront with S3

Step 1: Create an S3 Bucket

Create bucket (example: my-static-site)
Upload files: index.html, style.css
Enable Static Website Hosting
Configure permissions or OAC

Step 2: Create CloudFront Distribution

Go to CloudFront
Click Create Distribution
Select S3 bucket as Origin
Enable Origin Access Control (OAC)
Set Default Root Object: index.html
Redirect HTTP → HTTPS
Create distribution

Step 3: Access Website

CloudFront provides a domain like:

Your website is now faster and globally accessible.

7. Cache Behavior Explained

CloudFront caches content based on:

URL path
Headers
Cookies
Query strings

Example:

/static/* → Cached
/api/* → Not cached

8. Cache Invalidation

When content changes, CloudFront may still serve old cached files.

To invalidate cache:

Open CloudFront Distribution
Go to Invalidations
Add paths:

9. CloudFront with EC2 / ALB

Flow:

User → CloudFront → ALB → EC2

Use cases:

Dynamic web applications
APIs
Microservices

Benefits:

Reduced latency
Reduced backend load
Better security

10. Security Features in CloudFront

Feature	Purpose
HTTPS	Secure data transfer
AWS WAF	Protect from attacks
Signed URLs	Restrict access
Geo Restriction	Country-based access
OAC	Secure S3 access

11. CloudFront in CI/CD (DevOps Use Case)

Typical Flow:

Developer pushes code to GitHub
CI/CD pipeline builds project
Files uploaded to S3
CloudFront cache invalidation triggered
Users see updated content instantly

12. Common Interview Questions

What is CloudFront?

A CDN service that delivers content with low latency using edge locations.

What is an Edge Location?

A server that caches and delivers content closer to users.

Difference between S3 and CloudFront?

S3 stores data
CloudFront delivers data faster using caching

Why use CloudFront in DevOps?

For speed, scalability, security, and CI/CD integration.

13. Real-Time Use Cases

Static websites (React, Angular)
Video streaming
API acceleration
E-commerce websites
Software downloads

14. Summary

Amazon CloudFront is a powerful CDN service that:

Improves performance
Enhances security
Reduces backend load
Fits perfectly into DevOps pipelines

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity

⭐ If you like this guide, don’t forget to star the repo!

📅 Day 18 | AWS CloudFormation — Infrastructure as Code (IaC) in AWS ☁️

Sudarshan Yadav — Tue, 16 Dec 2025 17:20:56 +0000

📅 Day 18 | AWS CloudFormation — Infrastructure as Code (IaC) in AWS ☁️

Today, I learned about AWS CloudFormation, which is an Infrastructure as Code (IaC) service that helps create, update, and delete AWS resources automatically using YAML or JSON templates.

CloudFormation is widely used in DevOps to deploy infrastructure in a repeatable, consistent, and automated way.

🏗️ AWS CloudFormation (DevOps – Infrastructure Automation)

🔹 Amazon CloudFormation

Service Type

Infrastructure as Code (IaC)

Template Format

YAML / JSON

Key Features

Automated infrastructure creation
Manages full lifecycle (Create, Update, Delete)
Consistent deployments
Automatic rollback on failure
Fully managed by AWS

🔹 Why We Use CloudFormation in DevOps

CloudFormation is used when we need:

✅ Automated infrastructure deployment
✅ Repeatable environments (Dev / Test / Prod)
✅ Version-controlled infrastructure
✅ Reduced manual errors
✅ Easy rollback and recovery

🔹 Real-World DevOps Use Cases

Use Case	Why CloudFormation
EC2 & VPC setup	One-click infrastructure
Auto Scaling	Consistent scaling
CI/CD pipelines	Infrastructure automation
Disaster recovery	Easy recreation
Multi-environment setup	Template reuse

🔹 How CloudFormation Works (Architecture)

User

↓

CloudFormation Template (YAML / JSON)

↓

CloudFormation Stack

↓

AWS Resources (EC2, S3, VPC, IAM, RDS)

🔹 Key CloudFormation Components

Template – Blueprint of infrastructure
Stack – Deployed version of template
Resources – AWS services defined
Parameters – Input values
Outputs – Results like IP, DNS

🔹 Step-by-Step: How to Use CloudFormation

🔹 Step 1: Create Template

Create a YAML or JSON file defining AWS resources.

Resources:
  MyS3Bucket:
    Type: AWS::S3::Bucket

🔹 Step 2: Create Stack

AWS Console → CloudFormation
Click Create Stack
Upload template
Enter stack name
Click Create

🔹 Step 3: Stack Creation

CloudFormation:

Creates resources automatically
Handles dependencies
Shows status: CREATE_COMPLETE

🔹 Step 4: Update Stack

Modify template
Click Update Stack
Resources update automatically

🔹 Step 5: Delete Stack

Delete stack
All resources are deleted safely

🔹 CloudFormation vs Terraform (Interview)

Feature	CloudFormation	Terraform
Provider	AWS only	Multi-cloud
Language	YAML / JSON	HCL
State	AWS managed	Local / Remote
Owner	AWS	HashiCorp

🔹 CloudFormation Usage in DevOps

Tool	Usage
Jenkins	Infra automation
CI/CD	Stack deployment
Git	Template versioning
CodePipeline	IaC workflow
DevOps Teams	Environment setup

🔹 Common Interview Questions

Q1: What is CloudFormation?

✔ Infrastructure as Code service in AWS.

Q2: Supported template formats?

✔ YAML and JSON.

Q3: What is a Stack?

✔ Deployed template.

Q4: Does CloudFormation support rollback?

✔ Yes.

🔹 One-Line Interview Answer

AWS CloudFormation is an Infrastructure as Code service used to automate AWS resources using YAML or JSON templates.

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity

⭐ If you like this guide, don’t forget to star the repo!

📅 Day 17 | AWS EFS (Elastic File System) — Shared Storage in AWS 🗂️☁️

Sudarshan Yadav — Mon, 15 Dec 2025 08:45:19 +0000

📅 Day 17 | AWS EFS (Elastic File System) — Shared Storage in AWS 🗂️☁️

Today, I learned about Amazon EFS (Elastic File System), which is a fully managed, scalable, shared file system in AWS.

EFS allows multiple EC2 instances to read and write data simultaneously, making it ideal for DevOps and cloud-native architectures.

EFS helps in building highly available, scalable, and persistent storage solutions for applications running across multiple Availability Zones.

🗂️ AWS EFS (DevOps – Shared File System)

🔹 Amazon EFS (Elastic File System)

Service Type

File-based storage service
Uses NFS protocol (Port 2049)

Key Features

Shared storage across multiple EC2 instances
Automatically scales storage
Highly available (Multi-AZ)
Fully managed by AWS
Linux-based file system

Common DevOps Use Cases

Jenkins shared workspace
Kubernetes Persistent Volumes (PV/PVC)
Web application shared uploads
Centralized logs storage
WordPress media storage

One-Line Summary (Interview)

Amazon EFS is a fully managed shared file system that provides scalable and highly available storage for multiple EC2 instances across availability zones using NFS.

AWS EFS (Elastic File System) – Step by Step DevOps Guide

This guide explains Amazon EFS in a simple, fresher-friendly DevOps way, ready to upload on GitHub (Markdown format).

1️⃣ What is AWS EFS?

Amazon EFS (Elastic File System) is a fully managed, scalable, shared file system provided by AWS.

👉 Think of EFS like Google Drive for EC2 instances — multiple EC2 instances can read and write the same data at the same time.

2️⃣ Why We Use EFS in DevOps

EFS is used when we need:

✅ Shared storage between multiple EC2 instances
✅ Persistent data (data survives EC2 termination)
✅ High availability (multi-AZ)
✅ Linux-based file system (NFS)

3️⃣ Real-World DevOps Use Cases

Use Case	Why EFS
Web application uploads	Same files for all EC2
Jenkins shared workspace	Multiple Jenkins agents
Kubernetes persistent storage	Shared PVC
Centralized logs	Common log directory
WordPress media	Shared media files

4️⃣ How EFS Works (Architecture)

User
 ↓
Load Balancer
 ↓
EC2 (AZ-1) ─┐
EC2 (AZ-2) ─┼──> EFS (Shared File System)
EC2 (AZ-3) ─┘

EFS is regional
Uses NFS protocol (Port 2049)
Mounted like a folder inside EC2

5️⃣ EBS vs EFS vs S3 (Interview Comparison)

Feature	EBS	EFS	S3
Storage Type	Block	File	Object
Attach	Single EC2	Multiple EC2	Internet
OS Support	Linux/Windows	Linux only	Any
Mountable	Yes	Yes	No
Shared Access	❌	✅	✅

6️⃣ Step-by-Step: How to Create and Use EFS

🔹 Step 1: Create EFS

AWS Console → EFS
Click Create file system
Select VPC
Availability Zones → Auto selected
Click Create

🔹 Step 2: Configure Security Group

EFS needs NFS access.

Inbound Rule:

Type: NFS
Port: 2049
Source: EC2 Security Group

🔹 Step 3: Launch EC2 Instance

Amazon Linux 2
Same VPC as EFS
Attach same Security Group
SSH into the instance

🔹 Step 4: Install EFS Utilities

sudo yum install -y amazon-efs-utils

🔹 Step 5: Create Mount Directory

sudo mkdir /efs

🔹 Step 6: Mount EFS to EC2

sudo mount -t efs fs-xxxx:/ /efs

Check mount:

df -h

🔹 Step 7: Test Shared Storage

cd /efs
sudo touch devops.txt

Mount the same EFS on another EC2 → file will be visible ✅

7️⃣ Auto-Mount EFS on Reboot (Important)

Edit fstab file:

sudo nano /etc/fstab

Add entry:

fs-xxxx:/ /efs efs defaults,_netdev 0 0

8️⃣ EFS Performance Modes

Mode	Usage
General Purpose	Web apps, CMS
Max I/O	Big data, analytics

9️⃣ EFS Storage Classes

Class	Cost
Standard	Normal access
Infrequent Access (IA)	Lower cost
One Zone	Cheapest (single AZ)

🔟 EFS Usage in DevOps Tools

Tool	Usage
Jenkins	Shared workspace
Docker	Shared volume
Kubernetes	Persistent Volumes
Terraform	Infrastructure creation
Ansible	Auto mount configuration

1️⃣1️⃣ Common Interview Questions

Q1: Can EFS be mounted on multiple EC2 instances?
✔ Yes, simultaneously.

Q2: Is EFS AZ-specific?
✔ No, it is regional.

Q3: Which protocol does EFS use?
✔ NFS (Port 2049).

Q4: Can Windows use EFS?
✔ No, only Linux supports EFS.

1️⃣2️⃣ One-Line Interview Answer

Amazon EFS is a fully managed, scalable, shared file system that allows multiple EC2 instances across availability zones to access the same data using NFS.

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity

⭐ If you like this guide, don’t forget to star the repo!

📅 Day 16 | AWS RDS — Managed Database Service in AWS 🗄️☁️

Sudarshan Yadav — Sun, 14 Dec 2025 17:12:31 +0000

📅 Day 16 | AWS RDS — Managed Database Service in AWS 🗄️☁️

Today, I learned about AWS RDS (Relational Database Service), which is a fully managed database service provided by AWS to easily set up, operate, and scale relational databases in the cloud.

AWS RDS helps teams focus on application development by handling database provisioning, backups, patching, scaling, and maintenance automatically.

🗄️ What is AWS RDS?

AWS RDS (Relational Database Service) allows you to run relational databases in AWS without managing the underlying infrastructure.

Supported Database Engines:

MySQL
PostgreSQL
MariaDB
Oracle
SQL Server
Amazon Aurora

🚀 Why Use AWS RDS?

No manual database installation
Automated backups and snapshots
High availability with Multi-AZ
Easy scaling of compute and storage
Built-in monitoring using CloudWatch
Secure access using VPC, Security Groups, and IAM

⚙️ Key Features of AWS RDS

Multi-AZ Deployment → Automatic failover for high availability
Read Replicas → Improve read performance
Automated Backups → Point-in-time recovery
Snapshots → Manual backups
Encryption → Data at rest and in transit

🧩 AWS RDS in DevOps Workflow

Backend database for applications
Used in CI/CD pipelines
Supports production and non-production environments
Integrated with monitoring and alerting systems

🌍 Real-World Example

A web application running on EC2 / EKS uses AWS RDS to store application data.

The application scales automatically while RDS ensures data availability, security, and backups.

✅ Summary

AWS RDS is a core AWS service for building secure, scalable, and highly available applications and is widely used in production-level DevOps architectures.

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #RDS #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity

📅 Day 15 | AWS SNS & SQS — Messaging Services in AWS 🚀

Sudarshan Yadav — Sat, 13 Dec 2025 17:25:14 +0000

📅 Day 15 | AWS SNS & SQS — Messaging Services in AWS 🚀

Today, I learned about AWS SNS (Simple Notification Service) and AWS SQS (Simple Queue Service), which are core messaging services used in AWS & DevOps architectures for communication between applications and services.
These services help in building decoupled, scalable, and reliable systems.

🔔 AWS SNS & 📦 AWS SQS (DevOps – Point to Point)

🔔 AWS SNS (Simple Notification Service)

Service Type

Push-based messaging service

Main Purpose

Used to send notifications and alerts

Messaging Model

Publish / Subscribe (Pub-Sub)

Flow

Delivery

Message is pushed automatically to subscribers

Subscribers Can Be

Email
SMS
AWS Lambda
HTTP / HTTPS
SQS

Message Storage

SNS does not store messages
If the subscriber is unavailable, the message is lost

Use in DevOps

CloudWatch alarms
Deployment notifications
System failure alerts

Scalability

Fully managed and highly scalable

Interview One Line

SNS is used to send real-time notifications to multiple subscribers.

📦 AWS SQS (Simple Queue Service)

Service Type

Pull-based message queue service

Main Purpose

Used to decouple applications

Messaging Model

Queue-based

Flow

Message Retrieval

Consumer polls (pulls) messages from the queue

Message Storage

Messages are stored safely until processed

Visibility Timeout

Message is hidden while being processed

Types of Queues

Standard Queue
- High throughput
- At-least-once delivery
FIFO Queue
- Ordered processing
- Exactly-once delivery

Use in DevOps

Background jobs
Auto Scaling workloads
CI/CD task handling

Interview One Line

SQS is used to store messages and process them asynchronously.

🔄 SNS vs SQS – Point to Point Difference

Feature	SNS	SQS
Message Type	Push	Pull
Purpose	Send notifications	Store & process messages
Consumers	Multiple subscribers	One consumer per message
Storage	No	Yes
Use Case	Alerts & notifications	Task & job processing

🔁 SNS + SQS Together (DevOps Use Case)

Application sends message to SNS
SNS topic fans out the message
Multiple SQS queues receive the message
Each service processes independently

👉 Used in Microservices Architecture & CI/CD Pipelines

⭐ Final Interview Line

SNS is for sending messages, SQS is for queuing messages until they are processed.

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity

📅 Day 14 | AWS NACL — Subnet-Level Security in AWS 🔐

Sudarshan Yadav — Fri, 12 Dec 2025 17:56:43 +0000

📅 Day 14 | AWS NACL — Subnet-Level Security in AWS 🔐

NACL (Network Access Control List) is a subnet-level firewall in AWS VPC.

It controls what traffic is allowed in and out of each subnet, acting like a security gate at the subnet boundary.

If you’re learning AWS networking, mastering NACL is a key step in building secure cloud architectures.

🔥 Why NACL Is Important in AWS & DevOps

🛡️ Adds an extra layer of security at the subnet level
🔁 Controls inbound & outbound traffic (stateless)
🚫 Supports both ALLOW and DENY rules
📦 Protects private subnets (App Servers, Databases, EKS Nodes)
⚙️ Often used in secure DevOps infrastructure (EKS, EC2, CI/CD, Load Balancers)

🟧 What is NACL in AWS?

NACL (Network Access Control List) is a network-level firewall that controls traffic going in and out of a subnet in a VPC.

Think of it as a security gate for each subnet.

🔥 Why NACL is important in DevOps?

As a DevOps engineer, you work with:

VPC creation
Subnets (public/private)
EC2, Load balancers, NAT
Kubernetes clusters (EKS)
Terraform or CloudFormation

All of these use networking, and NACL helps control what traffic is allowed.

NACL ensures:

✔️ Traffic is restricted
✔️ Only safe ports are open
✔️ Subnet-to-subnet traffic is filtered
✔️ Security best practices are followed

This is important in DevOps pipelines, deployments, and infra automation.

🟦 Key Features of NACL (Easy to Remember)

1️⃣ Subnet-Level Firewall

A NACL is attached to a subnet, not an EC2 instance.

2️⃣ Stateless

➡️ Allow inbound traffic? Then you must allow outbound traffic also.

Example: Allow port 80 IN → must allow port 80 OUT.

3️⃣ Allows both:

ALLOW rules
DENY rules

4️⃣ Rule number order matters

Lowest number checked first (100 → 101 → 102…).

5️⃣ Default NACL = Allow everything

6️⃣ Custom NACL = Deny everything unless allowed

🟪 NACL Use Case in DevOps

Example 1: Public subnet

You deploy:

EC2 instance (web server)
ALB (load balancer)

NACL allows:

HTTP (80)
HTTPS (443)
SSH (22)

Example 2: Private subnet

You deploy:

App server
Database
EKS worker nodes

NACL allows only internal traffic:

App → DB (3306)
Node-to-node communication
No public internet access

💡 Difference Between NACL and Security Group (Interview)

Security Group	NACL
Instance level	Subnet level
Stateful	Stateless
Return traffic auto allowed	Must allow separately
Only ALLOW rules	ALLOW + DENY rules
Easier to manage	Used for high-level subnet control

🟩 Simple Example to Understand

Public Subnet NACL

Inbound Rules:

Allow HTTP (80)
Allow HTTPS (443)
Allow SSH (22)

Outbound Rules:

Allow ALL

Private Subnet NACL

Inbound:

Allow 3306 from app subnet

Outbound:

Allow 3306 back to app subnet
Deny internet traffic

✅ Example NACL Rule Table

Rule No	Type	Protocol	Port Range	Source / Destination	Action
100	Inbound	TCP	80	0.0.0.0/0	ALLOW
110	Inbound	TCP	443	0.0.0.0/0	ALLOW
120	Inbound	TCP	22	0.0.0.0/0	ALLOW
1000	Outbound	ALL	ALL	0.0.0.0/0	ALLOW
*	-	-	-	-	DENY (implicit)

🛠️ Terraform Example (minimal)

Use this as a starting point — update vpc_id, CIDRs and rule numbers as needed.

resource "aws_network_acl" "public_nacl" {
  vpc_id = aws_vpc.main.id
  tags = {
    Name = "public-nacl"
  }
}

resource "aws_network_acl_rule" "allow_http_in" {
  network_acl_id = aws_network_acl.public_nacl.id
  rule_number    = 100
  egress         = false
  protocol       = "6"       # TCP
  rule_action    = "allow"
  cidr_block     = "0.0.0.0/0"
  from_port      = 80
  to_port        = 80
}

resource "aws_network_acl_rule" "allow_https_in" {
  network_acl_id = aws_network_acl.public_nacl.id
  rule_number    = 110
  egress         = false
  protocol       = "6"
  rule_action    = "allow"
  cidr_block     = "0.0.0.0/0"
  from_port      = 443
  to_port        = 443
}

resource "aws_network_acl_rule" "allow_ssh_in" {
  network_acl_id = aws_network_acl.public_nacl.id
  rule_number    = 120
  egress         = false
  protocol       = "6"
  rule_action    = "allow"
  cidr_block     = "0.0.0.0/0"
  from_port      = 22
  to_port        = 22
}

resource "aws_network_acl_rule" "allow_all_out" {
  network_acl_id = aws_network_acl.public_nacl.id
  rule_number    = 1000
  egress         = true
  protocol       = "-1"      # all protocols
  rule_action    = "allow"
  cidr_block     = "0.0.0.0/0"
  from_port      = 0
  to_port        = 0
}

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity

📅 Day 13 | AWS VPC — The Heart of AWS Networking 🌐

Sudarshan Yadav — Thu, 11 Dec 2025 17:18:30 +0000

📅 Day 13 | AWS VPC — The Heart of AWS Networking 🌐

AWS VPC (Virtual Private Cloud) is the foundation of all networking inside AWS.

Every EC2 instance, database, load balancer, or container service you deploy lives inside a VPC.

Understanding VPC = understanding how your entire cloud infrastructure communicates.

🔥 Why VPC Is Essential

🛡️ Designing secure architectures
🌐 Creating public & private networks
🚀 Enabling internet access with Internet Gateway (IGW) & NAT Gateway
🔗 Connecting environments using VPC Peering
⚙️ Building scalable DevOps deployments

🎯 Why You Must Master VPC

Mastering VPC gives you full control over:

Networking
Security boundaries
Traffic flow
Service-to-service connectivity

VPC is one of the most criti

AWS VPC, Subnets, IGW, NAT, Peering, SSH...

✅ Quick Summary (What You’ll Get)

Create VPCs (Mumbai & Delhi) + Subnets
Attach Internet Gateway (IGW) + Public Route Table
Create NAT Gateway + Private Route Table
Create VPC Peering + routing both sides
Delete resources in correct order
PuTTYgen steps to convert PEM ↔ PPK

1) Create a VPC (Example)

Step	Action
Console	VPC → Create VPC → VPC only
Name	`MyVPC01`
IPv4 CIDR	`10.0.0.0/24` (or `/16` for more IPs)
Result	VPC created

2) Create Subnets

Public Subnet (example)

Field	Value
VPC	MyVPC01
Name	`sub-public-1`
AZ	`ap-south-1a`
CIDR	`10.0.0.0/28`
Auto-assign public IPv4	Enable

Private Subnet (example)

Field	Value
VPC	MyVPC01
Name	`sub-private-1`
CIDR	`10.0.1.0/28`
Auto-assign public IPv4	Disable

3) Internet Gateway (IGW) + Public Route Table

Internet Gateway

Step	Action
Create	VPC → Internet Gateways → Create
Name	`igw-mumbai`
Attach	Attach to `MyVPC01`

Public Route Table

Step	Action
Create/Select	Route tables → `public-rt`
Add Route	`0.0.0.0/0` → Internet Gateway (`igw-mumbai`)
Associate	Public Subnet (`sub-public-1`)

4) NAT Gateway (Private → Outbound Internet)

Step	Action
Create	NAT Gateway in public subnet (`sub-public-1`)
EIP	Allocate new Elastic IP
Result	NAT Gateway created

Private Route Table

Route	Target
`0.0.0.0/0`	NAT Gateway

Associate this route table with the private subnet (sub-private-1).

Outcome:

Private EC2 → outbound internet OK, inbound blocked.

5) Security Groups (Recommended)

Public EC2 SG

Rule	Value
Inbound	SSH (22) from your IP
Inbound	HTTP/HTTPS (80/443) from `0.0.0.0/0` (if web)
Outbound	All allowed

Private EC2 SG

Rule	Value
Inbound	From Public EC2 SG or ALB
Outbound	All allowed

6) EC2 Deployment

Public EC2

Launch into sub-public-1
Use Public-SG
This can serve as a bastion/jump host

Private EC2

Launch into sub-private-1
Use Private-SG
SSH through bastion only

7) Create VPCs for Peering (Mumbai & Delhi)

Mumbai VPC

Item	Value
VPC Name	`vpc-mumbai`
CIDR	`10.0.0.0/16`
Subnet	`sub1-mumbai` → `10.0.0.0/28`
IGW	`igw-mumbai`
Public RT	Route → `0.0.0.0/0 → igw-mumbai`

Delhi VPC

Item	Value
VPC Name	`vpc-delhi`
CIDR	`172.16.0.0/16`
Subnet	`sub1-delhi` → `172.16.0.0/28`
IGW	`igw-delhi`
Public RT	Route → `0.0.0.0/0 → igw-delhi`

8) VPC Peering (Mumbai ↔ Delhi)

Create Peering

Step	Action
Create	VPC → Peering Connections
Name	`my-peering`
Requester	`vpc-mumbai`
Accepter	`vpc-delhi`

Accept request from the Delhi side.

Add Routes (Both Sides)

Mumbai Route Table

Destination	Target
`172.16.0.0/16`	Peering Connection

Delhi Route Table

Destination	Target
`10.0.0.0/16`	Peering Connection

Security Groups

Allow from peer CIDRs if required.

9) Deletion / Cleanup Order

Order	Delete
1	Peering connection
2	EC2 Instances
3	NAT Gateway (release EIP)
4	Detach/Delete IGW
5	Subnets
6	Route Tables
7	VPC

This avoids “resource in use” errors.

10) AWS Limits & Quotas

Resource	Default Limit
VPCs per Region	Usually 5
Subnets	Large (no issue normally)
NAT Gateways	Limited by region, costly

Request quota increase via AWS Service Quotas.

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity

📅 Day 12 | AWS IAM — The Backbone of AWS Security 🔐☁️

Sudarshan Yadav — Thu, 11 Dec 2025 16:39:05 +0000

📅 Day 12 | AWS IAM — The Backbone of AWS Security 🔐☁️

AWS IAM (Identity and Access Management) helps us securely control access to AWS services.

It is one of the FIRST things every DevOps engineer must master because almost all AWS services depend on IAM Users, Roles, Groups, and Policies.

IAM plays a crucial role in:

Secure access management
CI/CD automation
Service-to-service communication
DevOps workflows
Cloud security best practices

Mastering IAM means mastering security + automation + access control, which is the foundation of working in AWS and DevOps.

🔐 What is IAM?

IAM (Identity and Access Management) is the security system of AWS.

It decides who can access what in your AWS account.

Think of IAM like a security guard:

Users = People who need access
Roles = Permissions for AWS services (EC2, Lambda, GitHub Actions, Terraform)
Policies = Rules that say what actions are allowed
Groups = Team permissions

🧑‍💻 How to Use IAM (Step-by-Step Guide)

✅ 1. Create IAM Users (for people)

Use users for human access, not automation.

Steps:

Go to AWS Console → IAM → Users
Click Create user
Give name (e.g., devops-user)
Attach permissions (Admin or custom)
Create login credentials
Enable MFA (very important!)

Purpose: Logging into AWS as a person.

✅ 2. Create Groups (for teams)

Groups help give the same permissions to multiple users.

Examples:

DevOps-Team
Developers
Admin-Team

Steps:

IAM → User groups
Create group
Attach common policies
Add users to group

✅ 3. Create IAM Roles (for AWS services)

Roles are used by machines, not humans.

Examples:

EC2 instance role
Lambda execution role
GitHub Actions OIDC role
Jenkins role
Terraform role

Steps:

IAM → Roles → Create role
Choose Service (EC2, Lambda, etc.)
Attach policies (S3, EC2, CloudWatch)
Attach role to service

Use Examples:

EC2 can read S3 objects using a role
GitHub Actions deploys to AWS using a role (no access keys)

✅ 4. Attach Policies (Permissions)

A policy is a JSON document that defines allowed actions.

Example Policy:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::mybucket/*"
    }
  ]
}

✅ 4. Attach Policies (Permissions)

Steps:

IAM → Policies
Create policy
Attach to user / group / role

✅ 5. Enable MFA (for security)

MFA adds strong protection during login.

Steps:

IAM → Users → Your user → Security credentials
Click Assign MFA device
Scan QR code using Google Authenticator / Authy
Done

✅ 6. Use IAM Access Analyzer

IAM Access Analyzer identifies security risks like public S3 buckets or over-permissive policies.

Steps:

IAM → Access Analyzer
Enable analyzer
Check findings
Fix over-permissive policies

🧰 Where IAM is Used in DevOps?

Task	IAM Required?	Example
CI/CD (GitHub Actions)	Yes	Role with OIDC
Terraform	Yes	IAM Role with policies
EC2 Logging	Yes	CloudWatch role
S3 Artifacts	Yes	S3 access policy
EKS	Yes	IAM roles for Kubernetes
Jenkins Deployment	Yes	IAM user / role
Monitoring	Yes	CloudWatch permissions

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity

📅 Day 11 🚀 Amazon S3 | Simple & Secure Cloud Storage

Sudarshan Yadav — Tue, 09 Dec 2025 16:36:22 +0000

📅 Day 11 🚀 Amazon S3 | Simple & Secure Cloud Storage

In AWS DevOps projects, storing data safely and accessing it anytime is very important.
AWS provides Amazon S3 — a highly scalable object storage service used worldwide.

S3 helps us:
✔ Store any type of data (images, logs, code, backups, videos)
✔ Access data anytime from anywhere
✔ Host static websites like portfolios & landing pages
✔ Store CI/CD build artifacts
✔ Maintain backups & version control
✔ Reduce cost using storage classes & lifecycle rules

📌 S3 = Storage + Security + Scalability + Cost Optimization

It protects data with encryption, IAM policies & multi-AZ durability (11 9’s 🤯),
making it a must-know service for DevOps engineers! 🔥

🚀 How to Create an S3 Bucket

1️⃣ Login to AWS Console

2️⃣ Go to S3 service

3️⃣ Click Create bucket

4️⃣ Enter a unique bucket name (globally unique)

5️⃣ Choose Region (ex: ap-south-1)

6️⃣ Keep Block Public Access ON by default

7️⃣ Click Create Bucket

✔ Bucket created successfully 🎉

📤 How to Upload Files to S3

1️⃣ Open your bucket

2️⃣ Click Upload

3️⃣ Add files (Images, Zip, PDFs, etc.)

4️⃣ Click Upload

✔ Files stored in S3 🗂️

🔗 How to Connect & Access Files from S3

Method	Usage
URL / Public Access	Share files or host static websites
IAM Users / Roles	Secure internal access
AWS CLI	Upload / Download using terminal
SDKs (Python, Java, Node.js)	Application-level integration
CloudFront	Faster access via CDN

📌 Access File using URL

Go to your object → Copy Object URL
If file is Public → URL works
If Private → Access Denied ❌

👉 To make file public (only when required!)
Objects → Permissions → Enable Public Read Access

💻 How to Connect S3 Using AWS CLI

👉 First configure CLI:

aws configure

👉 Upload File:

aws s3 cp file.txt s3://mybucket/

👉 Download File:

aws s3 cp s3://mybucket/file.txt .

👉 List Buckets:

aws s3 ls

🌐 Host a Static Website on S3

1️⃣ Upload index.html

2️⃣ Go to Properties → Static website hosting → Enable

3️⃣ Select index.html as the default file

4️⃣ Make index.html public

5️⃣ Copy Website Endpoint URL

6️⃣ Open in browser → 🎉 Website is Live

(Optional) Use CloudFront for HTTPS + global performance

🔁 Lifecycle Policies (Cost Optimization)

Go to: Management → Lifecycle rules

Example Rules:

After 30 days → Move to Standard-IA
After 90 days → Move to Glacier

Thank You

🔗 Connect With Me

🌐 Platform	🔗 Link
🐙 GitHub	https://lnkd.in/d2F3JPa3
✍️ Dev.to Blog	https://lnkd.in/dNtgqAME
💼 LinkedIn	https://lnkd.in/d3NctxFT
📄 Resume (Google Drive)	https://lnkd.in/dHDNsd_D

🔖 Hashtags

AWS #DevOps #CloudComputing #AWSLearning #EBS #VolumeMounting #DataPersistence #LearningJourney #CareerGrowth #DevOpsEngineer #AWSCommunity