What Is SCP?

SCP (Secure Copy Protocol) allows you to copy files or directories from one host to another securely.
It uses SSH for data transfer, authentication, and encryption, making it much safer than traditional methods like FTP or rcp.

In short:

SCP = Secure + Copy (through SSH)

Basic Syntax

scp [options] [source] [destination]

Example 1: Copy file from local to remote

scp file.txt user@remote_host:/home/user/

Example 2: Copy file from remote to local

scp user@remote_host:/home/user/file.txt /local/directory/

Example 3: Copy an entire directory

scp -r /local/folder user@remote_host:/home/user/

Example 4: Copy between two remote hosts

scp user1@host1:/path/file.txt user2@host2:/path/

Why Use SCP?

Security: Data is encrypted using SSH — safe from eavesdropping.
Simplicity: Single command for copy operations.
Cross-Platform: Works on Linux, macOS, and even Windows (via tools like PuTTY or PowerShell SSH).
Automation: Ideal for scripts or cron jobs for secure backups and data syncs.

Real-World Use Cases

• Deploying code to a remote server securely.
• Backing up files from remote systems.
• Copying configuration files between development and production servers.
• Automating secure file transfer in scripts or cron jobs.

What is a Cron Job?

A cron job is a scheduled task that runs automatically at a specific time or interval on Linux systems.

It’s managed by a background process called cron daemon (crond).
The cron daemon checks the crontab (cron table) file every minute to see if there are any scheduled tasks to execute.

In simple words:

Cron = Time-based job scheduler in Linux.

What is Crontab?

Crontab stands for cron table. It’s a file that contains the schedule of cron jobs for a specific user.
Each user on a Linux system can have their own crontab file.

To manage crontab:

# View existing cron jobs
crontab -l

# Edit your cron jobs
crontab -e

# Remove all cron jobs
crontab -r

Cron Job Format

A cron job follows a specific time format consisting of five fields and a command:

* * * * * command_to_execute
│ │ │ │ │
│ │ │ │ └── Day of the week (0 - 6) [Sunday=0]
│ │ │ └──── Month (1 - 12)
│ │ └────── Day of month (1 - 31)
│ └──────── Hour (0 - 23)
└────────── Minute (0 - 59)

Cron Job Examples

Example: Automating a Backup Script

Let’s say you have a script that backs up your files — /home/user/backup.sh

You can schedule it daily at 2 AM:

0 2 * * * /home/user/backup.sh

This means:

• Minute: 0
• Hour: 2
• Day: every day
• Month: every month
• Weekday: every day

What is SSH?

SSH (Secure Shell) is a network protocol that enables encrypted communication between your local machine and a remote server.
It’s mainly used by developers, system administrators, and cloud engineers to:

• Log in securely to remote systems
• Execute commands
• Transfer files
• Manage configurations

In AWS, SSH is the most common way to connect to Linux-based EC2 instances.

Why SSH is Important in EC2

When you launch a Linux EC2 instance, AWS doesn’t provide a username-password login.
Instead, it uses public-key cryptography — this ensures higher security and avoids password-based attacks.

Key Benefits:

• Strong Security: Uses encrypted keys instead of passwords.
• Direct Access: Gives full control of the instance’s command line.
• Remote Management: Access from anywhere with your private key.
• Automation Support: Works well with scripts and configuration tools (like Ansible or Terraform).

How SSH Works in EC2

SSH in EC2 uses a key pair for authentication:

ComponentDescriptionPublic Key (.pem)Stored on the EC2 instance by AWS.Private Key (.pem)Downloaded by you; used to connect securely.

Only someone with the private key can access the instance.

️ Steps to Connect to an EC2 Instance using SSH

Here’s how you can connect step-by-step:

Step 1: Launch an EC2 Instance

• Go to AWS Management Console → EC2 → Launch Instance
• Choose an Amazon Machine Image (AMI), like Amazon Linux 2
• Select an instance type (e.g., t2.micro)
• Create or select a key pair (.pem file)
• Configure security group — make sure port 22 (SSH) is open

Step 2: Download Your Key Pair

• AWS gives you a .pem file (example: mykey.pem)
• Save it securely on your local machine

Change its permissions:

chmod 400 mykey.pem

Step 3: Connect via SSH

Use the EC2 instance’s Public IPv4 DNS or IP address.

Run this command in your terminal:

ssh -i "mykey.pem" ec2-user@<public-ip-address>

For example:

ssh -i "mykey.pem" ec2-user@3.110.245.98

Note: The default username depends on your AMI:

• Amazon Linux: ec2-user
• Ubuntu: ubuntu
• CentOS: centos
• RHEL: ec2-user or root

Step 4: You’re In!

Once connected, you can:

• Update packages
• Install software
• Configure web servers
• Deploy applications

Example:

sudo yum update -y

In this blog, we’ll explore some of the most important port numbers in networking, their associated protocols, and the services they are used for. This knowledge is essential for IT students, network administrators, and anyone preparing for technical interviews or certifications.

Introduction

In computer networking, port numbers play a vital role in how devices communicate with each other. Every service or application running on a network uses a specific port number to send and receive data. Think of it like the “doorway” through which information enters or leaves a device.

For example, when you browse a website, your browser typically communicates over Port 80 (HTTP) or Port 443 (HTTPS). Similarly, when you send an email, it might use Port 25 (SMTP) or Port 587. Without port numbers, it would be impossible to know which application or service the data should reach.

Introduction

When browsing the internet, you may have noticed that some websites start with http:// while others begin with https://. At first glance, this may seem like a small difference, but it actually has a big impact on security, trust, and data protection. Let’s break down what these two mean and how they differ.

What is HTTP?

HTTP stands for HyperText Transfer Protocol. It is the foundation of data communication on the web. Whenever you open a website, HTTP defines how data (like text, images, or videos) is transferred between your browser and the web server.

• Introduced: 1991
• Port Used: 80
• Function: Transfers information in plain text between client (browser) and server.

Drawback:
Since HTTP transfers data in plain text, it is vulnerable to eavesdropping, data theft, and attacks like man-in-the-middle (MITM).

What is HTTPS?

HTTPS stands for HyperText Transfer Protocol Secure. It is the secure version of HTTP. The “S” in HTTPS means that all communication between your browser and the server is encrypted using SSL/TLS (Secure Socket Layer / Transport Layer Security).

• Introduced: 1994
• Port Used: 443
• Function: Ensures secure communication by encrypting the data.
• Authentication: Uses SSL/TLS certificates to verify the website’s identity.

Benefits:

• Protects against data theft.
• Builds trust with users (browsers show a padlock symbol 🔒).
• Essential for online transactions, banking, and login systems.

Service Models Provided by AWS

Amazon Web Services (AWS) is the world’s leading cloud service provider. It offers a wide range of services that allow businesses and individuals to build, deploy, and scale applications without investing in heavy physical infrastructure. These services are broadly categorized into cloud service models.

In this blog, we’ll explore the main service models provided by AWS, with examples and use cases.

1. Infrastructure as a Service (IaaS)

IaaS provides basic computing resources such as servers, storage, and networking. It gives customers more control over their IT resources, while AWS manages the physical infrastructure.

AWS IaaS Services

• Amazon EC2 (Elastic Compute Cloud): Virtual servers for running applications.
• Amazon S3 (Simple Storage Service): Scalable storage for data backup, websites, and big data.
• Amazon VPC (Virtual Private Cloud): Secure networking in the cloud.

Use Case: A startup can quickly launch virtual servers and storage without buying costly hardware.

2. Platform as a Service (PaaS)

PaaS offers a managed environment for application development. Developers focus only on coding, while AWS handles servers, storage, and scaling.

AWS PaaS Services

• AWS Elastic Beanstalk: Deploy web applications without managing servers.
• AWS Lambda: Run code without provisioning servers (serverless computing).
• Amazon RDS (Relational Database Service): Managed databases (MySQL, PostgreSQL, Oracle, SQL Server).

Use Case: Developers can deploy apps faster without worrying about infrastructure management.

3. Software as a Service (SaaS)

SaaS delivers ready-to-use software applications over the internet. Users don’t manage servers or apps; they simply use the software.

AWS SaaS Offerings

• Amazon Chime: Video conferencing and communication tool.
• AWS WorkSpaces: Virtual desktop service.
• Amazon Connect: Cloud-based contact center service.

Use Case: Businesses can use tools like Amazon Chime for meetings without installing or maintaining software.

Difference Between IaaS, PaaS, and SaaS

Deployment Models of the Cloud

Cloud computing has become the backbone of modern technology. But before organizations adopt the cloud, they need to decide how they want to deploy it. That’s where cloud deployment models come in.

Deployment models define who owns the infrastructure, who manages it, and how resources are shared. Each model has its pros, cons, and best-fit scenarios.

Let’s explore the 4 main cloud deployment models:

1. Public Cloud

• Definition: The cloud infrastructure is owned and managed by third-party providers (like AWS, Microsoft Azure, or Google Cloud).
• Access: Available to the general public or a large group of users.
• Cost: Pay-as-you-go pricing model.

Advantages

• No upfront infrastructure cost
• High scalability and flexibility
• Easy to set up and use

Disadvantages

• Less control over infrastructure
• Security concerns for sensitive data

Best for: Startups, small-to-medium businesses, and projects that need quick scalability.

2. Private Cloud

• Definition: The cloud infrastructure is dedicated to a single organization. It can be hosted on-premises or by a third-party provider.
• Access: Exclusive to one business or organization.
• Cost: Higher than public cloud because it requires dedicated resources.

Advantages

• Greater control over infrastructure
• Enhanced security and privacy
• Customizable according to business needs

Disadvantages

• High setup and maintenance costs
• Limited scalability compared to public cloud

Best for: Banks, government agencies, and enterprises handling sensitive data.

3. Hybrid Cloud

• Definition: A combination of public and private clouds, connected to share data and applications.
• Access: Flexible — businesses can use private cloud for sensitive workloads and public cloud for less critical tasks.

Advantages

• Balanced cost and security
• Business continuity and disaster recovery support

Disadvantages

• Complex to manage and integrate
• Requires strong network connectivity

Best for: Businesses needing both security and scalability (e.g., healthcare, retail).

4. Community Cloud

• Definition: A cloud infrastructure shared by multiple organizations with similar interests or requirements (e.g., compliance, security, or policies).
• Access: Restricted to a specific group of organizations.
• Cost: Shared among the participants.

Advantages

• Cost-effective for organizations with similar needs
• Better security than public cloud

Disadvantages

• Costs higher than public cloud
• Limited scalability compared to public cloud

Best for: Research institutions, healthcare organizations, or government departments working on joint projects.

Quick Comparison Table

Introduction

When deploying applications on Amazon Web Services (AWS), web servers play a crucial role in serving content to users. Among the most common choices are Apache HTTP Server and Nginx.

Both can be installed on AWS EC2 instances, integrated with services like Elastic Load Balancer (ELB), and connected to Amazon RDS or S3 for storage. However, they work differently and offer unique advantages in cloud environments.

1. Deployment on AWS

• Apache → Installed on EC2 (Linux/Windows). Good for small apps needing custom settings.
• Nginx → Runs on EC2, often as a reverse proxy or load balancer. Works well with CloudFront for global delivery.

2. Performance in AWS

• Apache → Scales up (add more CPU/RAM). Best for small to medium workloads.
• Nginx → Scales out (handle many connections). Works great with Auto Scaling for traffic spikes.

3. Static and Dynamic Content

• Apache → Handles dynamic content directly (e.g., PHP + RDS).
• Nginx → Best for static files. For dynamic work, it connects with PHP-FPM, Lambda, or API Gateway.

4. Load Balancing and Reverse Proxy

• Apache → Can balance load, but AWS ELB is usually better.
• Nginx → Commonly used as reverse proxy. Works smoothly with ELB or can load balance itself.

Quick Comparison Table of Apache and Nginx in AWS:

What is Networking?

Networking means linking computers and devices together so they can talk to each other, share files, use the internet, and work together. It helps us do things like sending emails, watching videos online, storing data in the cloud, and connecting with people around the world.

Network Ownership Types

• Private Network: Owned by an individual or organization. Highly secure and controlled.
• Public Network: Open to general access (e.g., public Wi-Fi). Less secure.
• Hybrid Network: Combines private and public access with role-based controls.

Technologies Involved

• Ethernet: Wired LAN connections
• Wi-Fi: Wireless LAN
• Bluetooth: PAN connectivity
• Fiber Optics & Satellite: WAN infrastructure

Types of Computer Networks

Diagram: LAN(Local Area Network)

Diagram: MAN(Metropolitan Area Network)

Diagram: WAN(Wide Area Network)

What Is Deployment

Deployment is the process of moving or inserting application code from a development environment into a higher-configuration machine or cloud infrastructure (such as servers, containers, or serverless platforms), so that the application becomes available for end-users.

Deployment = Putting your code on powerful cloud machines (like AWS EC2, Beanstalk, Lambda, etc.) so that users can access and use it.

Example in AWS:

• You write code on your laptop → push it to AWS.
• AWS places (deploys) that code on an EC2 instance (virtual machine) or Elastic Beanstalk environment (higher configuration machine).
• Now your app runs live, accessible through the internet.

⚙ Deployment Tools in AWS

• CodeDeploy → Automates deployment to EC2, ECS, or Lambda.
• CodePipeline → CI/CD pipeline for continuous deployment.
• CloudFormation → Infrastructure deployment.
• Elastic Beanstalk → Application deployment with auto-scaling.

Example:

Let’s say you have a shopping website:

1. Your frontend is React (hosted on S3 + CloudFront).
2. Backend API runs on EC2 (or Lambda if serverless).
3. Database runs on RDS (MySQL/PostgreSQL).
4. Deployment is automated using CodePipeline + CodeDeploy → every time you push code to GitHub, AWS deploys it to your environment.

Types of Deployment

• In-Place Deployment: Updates existing servers directly. Fast but may cause downtime.
• Blue-Green Deployment: Two environments — switch traffic to the new one after testing. Zero downtime.
• Canary Deployment: Release to a small group first, then expand. Safer rollout.
• Rolling Deployment: Update servers in batches. Balanced and stable.
• Recreate Deployment: Stop old version, then deploy new one. Simple but risky.

Diagram: AWS Architecture with Amazon VPC Configuration