1) Introduction to AWS & Cloud Computing
Fundamentals of Networking and Server Architecture
Client-Server Model Overview:
- Client: Desktop computers, mobile devices, or web browsers that request information or services across a network.
- Server: Specialized computer hardware or software dedicated to serving requests sent by clients.
- IP Addresses: Every client and server connected to a network has a unique Internet Protocol (IP) address that acts as its identifier. Communication occurs when clients send request packets to a server's IP address and receive data packets back.
- Analogy to Postal Mail: Requesting web content operates similarly to sending physical postal mail, where data packets require explicit destination and return IP addresses to reach their targets.
Core Server Components:
- Compute: The Central Processing Unit (CPU) performs calculation, logic processing, and execution of applications.
- Memory: Random Access Memory (RAM) provides short-term, temporary storage for high-speed data access during processing tasks.
- Storage: Hard Disk Drives (HDD) or Solid State Drives (SSD) store permanent data files.
- Database: Specialized systems designed to store, query, and manage structured data.
- Network: Physical and logical infrastructure (cables, routers, switches, and DNS servers) that facilitates data interchange.
Key Network Terminology:
- Network: A collection of interconnected devices (computers, servers, routers) capable of sharing data.
- Router: A networking hardware device responsible for routing and forwarding data packets between distinct computer networks by evaluating target IP addresses.
- Switch: A network device within a local network that receives data packets and forwards them directly to the specific target client or server.
Traditional IT Infrastructure vs. Cloud Computing
Traditional Infrastructure Environments:
- On-premises deployments traditionally occurred in home offices, garages, corporate offices, or dedicated physical data centers.
Challenges of Traditional Infrastructure:
- High Capital Expenditure (CAPEX): High upfront costs associated with purchasing physical server racks, real estate, and networking equipment.
- Facility Costs: Ongoing payments required for data center leases, continuous power supply, cooling infrastructure, and physical maintenance.
- Slow Hardware Procurement: Sourcing, purchasing, configuring, and deploying new servers or replacing failed hardware can take weeks or months.
- Scale Limits: Infrastructure is bounded by physical floor space and maximum hardware capacity, making rapid growth difficult.
- Operational Costs: Requires a dedicated, 24/7 technical operations team to manage and monitor physical systems.
- Disaster Vulnerability: Physical infrastructure is susceptible to site-level disasters such as fires, earthquakes, flooding, or major power grid failures.
Cloud Computing Principles and Characteristics
Definition of Cloud Computing:
- Cloud computing is the on-demand delivery of IT resources—including compute power, database storage, applications, and networking capabilities—via the internet with a pay-as-you-go pricing model.
- Infrastructure-connected hardware is owned, operated, and maintained by the cloud provider (e.g., Amazon Web Services), while end users provision and access resources dynamically via web interfaces or Application Programming Interfaces (APIs).
Five Essential Characteristics of Cloud Computing:
- On-Demand Self-Service: Users can provision computing capabilities (such as server time and network storage) automatically without requiring human interaction with the service provider.
- Broad Network Access: Capabilities are available over the network and accessed through standard mechanisms by heterogeneous client platforms (mobile phones, laptops, workstations).
- Multi-Tenancy and Resource Pooling: The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model. Physical and virtual resources are dynamically assigned and reassigned according to demand, maintaining strict security and isolation between tenant environments.
- Rapid Elasticity and Scalability: Resources can be elastically provisioned and released—in some cases automatically—to scale rapidly outward and inward with demand.
- Measured Service: Resource usage is automatically monitored, controlled, and reported, enabling transparent pay-per-use billing systems based on exact consumption metrics.
Cloud Deployment Models
Private Cloud:
- Cloud infrastructure operated solely for a single organization, hosted either on-premises or internally.
- Key Characteristics: Provides absolute infrastructure control, strict data privacy, and compliance customization, but retains higher maintenance costs.
Public Cloud:
- Infrastructure owned and operated by a third-party cloud service provider (e.g., Amazon Web Services, Microsoft Azure, Google Cloud Platform) rendered publicly over the internet.
- Key Characteristics: Provides maximum scalability, high availability, and dynamic pricing without physical hardware ownership.
Hybrid Cloud:
- An environment combining private infrastructure (on-premises data centers) with public cloud services.
- Key Characteristics: Allows organizations to keep sensitive datasets and core legacy applications within private infrastructure while leveraging the public cloud for operational scalability and flexible computing needs.
Advantages and Solved Problems of Cloud Computing
Six Major Advantages of Cloud Computing:
- Trade Capital Expense (CAPEX) for Operational Expense (OPEX): Eliminates upfront hardware investments in favor of paying on-demand for services consumed.
- Benefit from Massive Economies of Scale: Aggregate usage across hundreds of thousands of customers enables cloud providers to achieve higher efficiency and continuously pass savings onto users via lower pay-as-you-go pricing.
- Stop Guessing Capacity: Eliminates over-provisioning or under-provisioning by automatically scaling up or down based on real-time measured demand.
- Increase Speed and Agility: Reduces the time to deploy new resources to developers from weeks to mere minutes with simple API requests.
- Stop Spending Money Running and Maintaining Data Centers: Shifts focus away from managing power, cooling, and server racking to managing applications and core business logic.
- Go Global in Minutes: Deployment of applications in multiple geographic regions worldwide can be executed with a few clicks, reducing latency for end users globally.
Core Problems Solved by the Cloud:
- Flexibility: Dynamic reallocation and modification of resource specifications on demand.
- Cost-Effectiveness: Pay-as-you-go financial model ensures organizations pay strictly for what is actively utilized.
- Scalability: Handles increasing workloads by vertically upgrading node performance or horizontally adding infrastructure nodes.
- Elasticity: Automated real-time expansion (scale-out) and contraction (scale-in) dictated by operational demand spikes.
- High Availability & Fault Tolerance: Multi-data-center infrastructure designs prevent single points of physical failure.
- Agility: Streamlines rapid development, testing, and deployment cycles for digital applications.
Cloud Computing Service Models
Infrastructure as a Service (IaaS):
- Contains the basic building blocks for cloud IT, providing access to networking features, computers (virtual or hardware), and data storage space.
- Offers the highest level of administrative flexibility and control over architectural resources, mirroring traditional on-premises IT setups.
- Examples: Amazon EC2, Google Cloud Platform (GCP), Microsoft Azure, Rackspace, DigitalOcean, Linode.
Platform as a Service (PaaS):
- Removes the requirement for organizations to manage underlying infrastructure (hardware and operating systems), allowing full focus on application deployment, operational execution, and software code management.
- Examples: AWS Elastic Beanstalk, Heroku, Google App Engine, Windows Azure.
Software as a Service (SaaS):
- Delivers a complete, fully operational software application managed end-to-end by the cloud service provider.
- Users simply interact with the front-end software interface, eliminating maintenance obligations.
- Examples: Gmail, Dropbox, Zoom, AWS Rekognition.
Responsibility Breakdown Across Service Models:
- On-Premises: Customer manages Applications, Data, Runtime, Middleware, Operating System (O/S), Virtualization, Servers, Storage, and Networking.
- IaaS: Provider manages Virtualization, Servers, Storage, and Networking; Customer manages Applications, Data, Runtime, Middleware, and O/S.
- PaaS: Provider manages O/S, Middleware, Runtime, Virtualization, Servers, Storage, and Networking; Customer manages Applications and Data.
- SaaS: Provider manages all components (Applications, Data, Runtime, Middleware, O/S, Virtualization, Servers, Storage, and Networking).
Cloud Pricing Fundamentals and Application Examples
AWS Pricing Fundamentals:
- Compute: Billed per second or minute of active execution time.
- Storage: Billed based on the volume of data stored per gigabyte over time.
- Data Transfer OUT: Outbound data transfer leaving the cloud infrastructure is charged per gigabyte, whereas inbound data transfer INTO the cloud is free.
Real-World Cloud Implementations:
- Gmail: Cloud-native email application where billing scales strictly by stored content capacity without end-user server management.
- Dropbox: Cloud storage service originally architected directly on top of AWS infrastructure.
- Netflix: On-demand video streaming platform operating entirely on AWS cloud infrastructure.
Amazon Web Services (AWS) Overview and History
AWS Corporate History Timeline:
- 2002: Launched internally within Amazon to standardise internal infrastructure.
- 2003: Recognized internal infrastructure systems as a core commercial strength; formulated market offering.
- 2004: First public service launched (Simple Queue Service - SQS).
- 2006: Official public relaunch featuring SQS, Simple Storage Service (S3), and Elastic Compute Cloud (EC2).
- 2007: Regional launch in Europe.
AWS Market Scale and Dominance:
- Generated $90 billion in annual revenue in 2023.
- Maintained 31% global cloud infrastructure market share in Q1 2024 (Microsoft second at 25%).
- Named a Leader in the Gartner Magic Quadrant for Strategic Cloud Platform Services for 13 consecutive years.
- Supports over 1,000,000 active users globally across diverse commercial verticals (e.g., Netflix, Activision, McDonald's, 21st Century Fox, Airbnb, NASA).

AWS Global Infrastructure
Infrastructure Components:
- AWS Regions: Physical geographic locations around the world hosting isolated clusters of data centers (e.g.,
us-east-1,eu-west-3). - Selection Criteria for AWS Regions:
- Governance and Legal Compliance: Guarantees data residency; data never leaves a specified region without explicit administrative configuration.
- Proximity to Customers: Reduces latency by hosting services geographically close to user populations.
- Service Availability: Specific novel services or feature sets may initially launch in select regions.
- Pricing Transparency: Cost per service varies across regions due to local operational overhead.
- AWS Regions: Physical geographic locations around the world hosting isolated clusters of data centers (e.g.,
AWS Availability Zones (AZs):
- Each AWS Region contains multiple isolated Availability Zones (typically 3, ranging between a minimum of 3 and maximum of 6 per region).
- Formatted as region identifiers followed by a letter (e.g.,
ap-southeast-2a,ap-southeast-2b,ap-southeast-2c). - An AZ consists of one or more physically discrete data centers equipped with independent, redundant power, cooling, and network connections.
- Interconnected within a region via high-bandwidth, ultra-low latency networking infrastructure.
AWS Points of Presence (Edge Locations):
- Comprises over 400 Points of Presence (400+ Edge Locations and 10+ Regional Edge Caches) spanned across 90+ cities in 40+ countries.
- Utilized by services such as Amazon CloudFront to deliver static and dynamic web content to global end users with minimal network latency.

AWS Service Scope and Governance
Global Services vs. Region-Scoped Services:
- Global Services: Configured globally without individual regional boundaries.
- Identity and Access Management (IAM): User identity and access control.
- Amazon Route 53: Domain Name System (DNS) web service.
- Amazon CloudFront: Global Content Delivery Network (CDN).
- AWS WAF: Web Application Firewall filtering global traffic.
- Region-Scoped Services: Tied to specific regional deployments.
- Amazon EC2: Virtual compute servers (IaaS).
- AWS Elastic Beanstalk: Managed deployment platform (PaaS).
- AWS Lambda: Serverless execution functions (FaaS).
- Amazon Rekognition: Machine learning computer vision (SaaS).
AWS Shared Responsibility Model:
- Defines the division of security obligations between AWS and the customer.
- AWS Responsibility (Security OF the Cloud):
- Protecting physical facilities hosting AWS services (data center buildings, power, environmental management).
- Hardware management (physical servers, hard drives, network cables).
- Software stack running physical virtualization systems, storage infrastructure, databases, and core networking across Regions, Availability Zones, and Edge Locations.
- Customer Responsibility (Security IN the Cloud):
- Guest operating system maintenance (updates, patches, firewall settings).
- Application software configuration and user access credentials.
- Platform settings, Identity and Access Management (IAM) controls.
- Firewall and network configurations.
- Data encryption practices: Client-side data encryption, server-side data encryption options, and network traffic protection mechanisms.

- AWS Acceptable Use Policy (AUP):
- Mandates explicit rules for platform usage:
- Prohibits illegal, harmful, or offensive content and activity.
- Prohibits security breaches, vulnerability probes, and unauthorized network penetration testing.
- Prohibits network abuse, distributed denial-of-service (DDoS) simulations, or unauthorized packet sniffing.
- Prohibits email or messaging abuse (unsolicited mass communications or spam).