MODULE-1

1. What is cloud What are needs of cloud What are use cases of cloud
What are the limitations of cloud (high speed internet , security low ,
all servers are charged (costly)) Lifecycle of cloud computing
What is the Cloud?
Simply put, the cloud refers to a global network of remote servers that are accessed
over the internet.1 Instead of storing and accessing data and programs from your
computer's hard drive, you access them online.2 Think of it like a massive, virtual storage
locker and computer that you can use anytime, anywhere, as long as you have an
internet connection.3
These servers are housed in massive data centers owned by cloud providers like Amazon
Web Services (AWS), Google Cloud, and Microsoft Azure. When you use a cloud service,
you're essentially renting computing power and storage from one of these providers.4
The Needs Met by the Cloud
The widespread adoption of cloud computing is driven by several compelling needs for
both individuals and businesses:
• Scalability and Flexibility: Businesses often have fluctuating needs for computing
resources. The cloud allows them to easily scale their usage up or down as needed,
paying only for what they use.5 This eliminates the need for expensive upfront
investments in hardware that might sit idle.6
• Cost-Effectiveness: By using the cloud, companies can avoid the high costs associated
with purchasing and maintaining their own IT infrastructure, including hardware,
software, and the staff to manage it.7
• Accessibility and Collaboration: Cloud services enable users to access their data and
applications from any device with an internet connection.8 This fosters seamless
collaboration among teams, as multiple users can work on the same documents and
projects in real-time.9
• Data Backup and Disaster Recovery: Storing data in the cloud provides a crucial layer
of protection against data loss due to hardware failure, theft, or natural disasters.
Cloud providers have robust backup and recovery systems in place.
• Automatic Software Updates: Cloud-based applications are typically updated
automatically by the provider, ensuring that users always have access to the latest
features and security patches without any manual effort.
Use Cases of the Cloud
The applications of cloud computing are vast and continue to expand. Here are some of
the most common use cases:
• Storage and File Sharing: Services like Google Drive, Dropbox, and OneDrive allow
users to store, access, and share files from anywhere.10
• Streaming Media: When you watch a movie on Netflix or listen to music on Spotify,
you are using the cloud to stream that content to your device.
• Software as a Service (SaaS): This includes a wide range of applications that are
accessed over the internet, such as email (Gmail, Outlook), customer relationship
management (Salesforce), and productivity suites (Google Workspace, Microsoft
365).
• Data Analytics and Big Data: The cloud provides the massive processing power
needed to analyze large datasets, enabling businesses to gain valuable insights and
make data-driven decisions.
• Web and Mobile App Hosting: Developers use the cloud to host websites and mobile
applications, taking advantage of its scalability to handle traffic spikes.11
• Gaming: Cloud gaming services like NVIDIA GeForce Now and Xbox Cloud Gaming
allow users to play graphics-intensive games on devices that wouldn't otherwise have
the necessary processing power.
Limitations of the Cloud
Despite its numerous advantages, cloud computing is not without its limitations:
• High-Speed Internet Dependency: A stable and fast internet connection is essential
to access cloud services. Without it, you can't get to your data or applications.
• Security Concerns: While cloud providers invest heavily in security, storing sensitive
data on remote servers introduces potential risks.12 Data breaches and unauthorized
access are valid concerns that need to be addressed with strong security measures.13
• Cost Management: While the pay-as-you-go model can be cost-effective, it can also
lead to unexpected expenses if usage is not carefully monitored and managed.14 The
cost of all the servers and services can add up, making it potentially costly if not
optimized.15
• Limited Control and Flexibility: When you use a public cloud service, you are bound
by the provider's infrastructure, policies, and terms of service.16 This can sometimes
limit your control and flexibility compared to an on-premises solution.17
• Vendor Lock-in: Migrating data and applications from one cloud provider to another
can be complex and costly, a situation known as vendor lock-in.18
The Lifecycle of Cloud Computing
The journey to adopting and managing cloud services typically follows a lifecycle with
several key phases:
1. Strategy and Planning: This initial phase involves defining the business goals for
cloud adoption, assessing the current IT infrastructure, and developing a cloud
strategy and roadmap. Key decisions are made regarding which cloud model (public,
private, or hybrid) and service models (IaaS, PaaS, SaaS) to use.
2. Cloud Adoption and Migration: In this phase, the actual migration of applications
and data to the cloud takes place. This can involve rehosting, replatforming, or
refactoring applications to be cloud-native.
3. Cloud Operations and Management: Once in the cloud, ongoing management and
monitoring are crucial. This includes managing security, performance, and costs.
Automation and orchestration tools are often used to streamline these processes.
4. Optimization: This is a continuous process of refining and improving the cloud
environment. It involves optimizing costs by right-sizing resources, improving
performance through monitoring and tuning, and enhancing security measures.
5. Innovation: With the foundational aspects in place, organizations can leverage the
cloud to drive innovation. This includes developing new cloud-native applications,
utilizing advanced services like AI and machine learning, and exploring new business
opportunities.
2. Types of cloud computing (deployment models and service models
explain and diagram)

Cloud Computing Deployment Models

Deployment models define the type of access to the cloud. There are four main
types:
1. Public Cloud
The public cloud is owned and operated by third-party cloud service providers, like
Amazon Web Services (AWS), Google Cloud, and Microsoft Azure. You access these
services over the internet. The key feature is that you share the same hardware,
storage, and network devices with other organizations or "tenants."
• Best for: Businesses with fluctuating demands, startups, and for services used by the
general public (like email or online photo storage).
• Pros: High scalability, cost-effective (pay-as-you-go), and no maintenance.
• Cons: Less control and potential security and compliance concerns since resources
are shared.
2. Private Cloud
A private cloud is a cloud computing environment dedicated to a single organization.
The infrastructure can be located on-premises or hosted by a third-party provider.
The key is that the resources are not shared.
• Best for: Large enterprises, government agencies, and organizations with strict
security and regulatory requirements.
• Pros: Enhanced security, greater control and customization, and improved
compliance.
• Cons: Higher costs, more complex to manage, and less scalability compared to a
public cloud.
3. Hybrid Cloud
A hybrid cloud combines a private cloud with one or more public cloud services, with
proprietary software enabling communication between them. This allows an
organization to use the public cloud for non-sensitive operations while keeping
sensitive data and applications in its private cloud.
• Best for: Businesses that want the flexibility to scale while maintaining security for
critical applications. For example, a retailer might use the public cloud to handle a
surge in online traffic during a sale but keep customer data in their private cloud.
• Pros: Flexibility, scalability, and security. It offers the best of both worlds.
• Cons: Can be complex to set up and manage.
4. Community Cloud
 A community cloud is a collaborative effort where infrastructure is shared between
several organizations from a specific community with common concerns (e.g.,
security, compliance, or jurisdiction). It can be managed internally or by a third-party.
• Best for: Organizations with similar needs, such as universities or healthcare
organizations.
• Pros: Cost-effective, enhanced security and compliance tailored to the community,
and collaborative.
• Cons: Can be more expensive than a public cloud and may have limited scalability.

Cloud Computing Service Models

Service models are the different layers of service that you can rent from a cloud
provider. There are three main models:
1. Infrastructure as a Service (IaaS)
IaaS is the most basic level of cloud service. With IaaS, you rent IT infrastructure—
servers, virtual machines, storage, networks, and operating systems—from a cloud
provider on a pay-as-you-go basis. It's like leasing the hardware for a data center
without having to physically manage it.
• You manage: Applications, data, runtime, middleware, and the operating system.
• Provider manages: Virtualization, servers, storage, and networking.
• Examples: Amazon EC2, Google Compute Engine, Microsoft Azure Virtual Machines.
2. Platform as a Service (PaaS)
PaaS provides a platform allowing customers to develop, run, and manage
applications without the complexity of building and maintaining the infrastructure
 typically associated with developing and launching an app. It's like having a workshop
where all the tools and equipment are provided for you.
• You manage: Applications and data.
• Provider manages: Runtime, middleware, operating system, virtualization, servers,
storage, and networking.
• Examples: AWS Elastic Beanstalk, Google App Engine, Heroku.
3. Software as a Service (SaaS)
SaaS is a method for delivering software applications over the Internet, on a
subscription basis. With SaaS, cloud providers host and manage the software
application and underlying infrastructure and handle any maintenance, like software
upgrades and security patching. The user simply logs in and uses the application.
• You manage: Nothing. Everything is managed by the provider.
• Provider manages: Everything from the application down to the networking.
• Examples: Google Workspace, Microsoft 365, Salesforce, Dropbox.
This diagram illustrates the "stack" of services and what you manage versus what the
provider manages for each model. As you move from IaaS to SaaS, you have less to
manage, but also less flexibility.
3. Architecture of cloud computing
The architecture of cloud computing is a blueprint of the components and their
relationships required for cloud technology.1 It's designed to deliver cloud services by
leveraging virtualization and resource pooling.2 The architecture is broadly divided
into two main parts: the front-end and the back-end, which are connected through
the internet.3
Here is a breakdown of the key components and layers that make up the architecture
of cloud computing.

1. Front-End Architecture (The Client Side)

The front-end is the part that the end-user sees and interacts with.4 It includes the
client's device and the applications needed to access the cloud services.5 Think of it
as the "face" of the cloud.
• Client Infrastructure: This is the device you use to access the cloud, such as a laptop,
smartphone, tablet, or desktop computer.6
• User Interface (UI): This is the application or web browser that you use to interact
with the cloud.7 For example, when you open Google Drive in your web browser, you
are interacting with the front-end UI.8
• Software: This includes client-side applications and browsers that provide a gateway
to the cloud's resources.9

2. Back-End Architecture (The Cloud Provider's Side)

The back-end is the core of the cloud computing architecture, managed by the cloud
service provider.10 It comprises all the resources and infrastructure needed to
provide the cloud services. It's the "behind-the-scenes" powerhouse.
• Application: This layer provides the actual service to the user.11 It could be a software
application (SaaS), a development platform (PaaS), or a virtual machine (IaaS).12
• Service Model: This defines the type of service being offered.13 The back-end
architecture is built to deliver these services:14
o SaaS (Software as a Service):15 Delivers ready-to-use software over the
internet (e.g., Gmail, Salesforce).16
o PaaS (Platform as a Service): Provides a platform for developers to build,
deploy, and manage applications (e.g., Google App Engine, Heroku).17
o IaaS (Infrastructure as a Service): Offers virtualized computing resources like
virtual machines, storage, and networks (e.g., Amazon Web Services,
Microsoft Azure).18
• Runtime: This layer provides the environment for applications to run. It includes the
operating system and other necessary components.
• Storage: This component provides massive, scalable storage for data.19 It can include
hard drives and solid-state drives in data centers.20
• Infrastructure: This is the foundational layer and includes the physical hardware like
servers, networking gear, and storage devices.21 This is the physical foundation of the
cloud.
• Management: This layer is responsible for managing and monitoring the resources in
the back-end.22 It handles tasks like resource allocation, security, and performance
monitoring.23
• Security: This is a critical component that ensures data privacy, integrity, and
protection against threats. It is implemented throughout the back-end infrastructure.
Visualizing the Cloud Architecture

Here is a simplified diagram to help you visualize the architecture of cloud

computing:
This diagram shows how the front-end and back-end are connected via the internet.
The back-end is a layered architecture with the physical infrastructure at the bottom
and the applications at the top. The management and security layers span across all
the components of the back-end to ensure smooth and secure operations.24
In essence, the architecture of cloud computing is designed to be highly scalable,
resilient, and flexible, allowing users to access powerful computing resources on
demand without having to manage the underlying complexity.25
4. AWS infrastructure (Application and services)

The AWS infrastructure is a vast and complex ecosystem built on a global network of
physical data centers, which provides a wide array of cloud-based applications and
services. It's best understood by looking at its two main components: the Global
Infrastructure (the foundation) and the Services (the building blocks that run on that
foundation).

AWS Global Infrastructure

The AWS Global Infrastructure is the physical foundation of its cloud services. It's
designed for high availability, low latency, and fault tolerance. The key components
are:
• Regions: An AWS Region is a physical geographical area in the world, such as "US East
(N. Virginia)" or "Asia Pacific (Mumbai)". Each region is isolated from the others,
providing a high degree of fault tolerance and stability. AWS services are typically
region-scoped, meaning when you launch a resource, you do it in a specific region.
• Availability Zones (AZs): Each AWS Region is made up of multiple, isolated locations
known as Availability Zones. An AZ consists of one or more discrete data centers with
redundant power, networking, and connectivity, housed in separate facilities. By
running applications across multiple AZs, you can protect them from single-point-of-
failure events, like power outages or natural disasters at a single data center.
• Edge Locations: These are smaller sites that are part of the Amazon CloudFront
Content Delivery Network (CDN). They are located in major cities around the world
and are used to cache content closer to end-users, which reduces latency and
improves performance for content delivery.

Core AWS Applications and Services

AWS offers over 200 fully-featured services from data centers globally. These services
are often categorized by their function. Here are some of the most fundamental and
widely used services:
Compute Services
These services provide the processing power for your applications.
• Amazon EC2 (Elastic Compute Cloud): This is one of the most popular AWS services.
It provides secure, resizable compute capacity (virtual servers) in the cloud. Think of
it as renting a virtual computer that you can run your applications on.
• AWS Lambda: This is a serverless compute service that lets you run code without
provisioning or managing servers. You simply upload your code, and Lambda
automatically runs and scales it in response to events.
• Amazon ECS (Elastic Container Service): A highly scalable, high-performance
container orchestration service that supports Docker containers.
Storage Services
These services are designed to store your data in a reliable and scalable way.
• Amazon S3 (Simple Storage Service): An object storage service offering industry-
leading scalability, data availability, security, and performance. It's perfect for storing
any amount of data, from backups and archives to big data analytics and web
content.
• Amazon EBS (Elastic Block Store): Provides high-performance block storage volumes
for use with Amazon EC2 instances. Think of it as a virtual hard drive for your virtual
server.
• Amazon Glacier: A very low-cost storage service for data archiving and long-term
backup.
Database Services
AWS provides a wide range of managed database services to fit different application
needs.
• Amazon RDS (Relational Database Service): Makes it easy to set up, operate, and
scale a relational database in the cloud. It supports popular database engines like
MySQL, PostgreSQL, and Microsoft SQL Server.
• Amazon DynamoDB: A fast and flexible NoSQL database service for all applications
that need consistent, single-digit millisecond latency at any scale. It's a fully managed
database that supports both document and key-value store models.
• Amazon Redshift: A fast, fully managed data warehouse that makes it simple and
cost-effective to analyze all your data using standard SQL.
Networking and Content Delivery
These services help you isolate your cloud resources and deliver content securely
with high performance.
• Amazon VPC (Virtual Private Cloud): Lets you provision a logically isolated section of
the AWS Cloud where you can launch AWS resources in a virtual network that you
define.
• Amazon CloudFront: A fast content delivery network (CDN) service that securely
delivers data, videos, applications, and APIs to customers globally with low latency
and high transfer speeds.
• Amazon Route 53: A highly available and scalable cloud Domain Name System (DNS)
web service.

Machine Learning (ML) & AI

AWS provides a broad set of services for developers and data scientists to build,
train, and deploy machine learning models.
• Amazon SageMaker: A fully managed service that provides every developer and data
scientist with the ability to build, train, and deploy machine learning models quickly.
• Amazon Lex: The same deep learning engine that powers Amazon Alexa, allowing
you to build chatbots and conversational interfaces.
• Amazon Rekognition: A service that makes it easy to add image and video analysis to
your applications.

5. Components of cloud computing (virtualization,middleware,security

and compliance,access control,data encryption)

The components of cloud computing can be categorized into several key layers and
elements,
each responsible for a specific function in delivering cloud services. Here's a
breakdown:
1. Front-End Components (User Interface):
These are the parts that users interact with to access cloud services.
Web Interface or Client Software: Tools like browsers or apps that allow users to
interact with the cloud.
Devices: Devices used to access cloud services.

2. Back-End Components (Infrastructure):

The backend is responsible for providing the core functionalities of cloud computing.
It includes the infrastructure and platforms that power the cloud.
a. Infrastructure:
Servers: Physical and virtual machines used to run applications and process requests.
Storage: Systems that store data in the cloud.
Networking: Connections and bandwidth to ensure smooth communication between
users and cloud resources.
Data Centers: Physical locations housing servers and infrastructure.
Components of cloud computing
b. Service Models:
Infrastructure as a Service (IaaS): Provides virtualized hardware and basic
infrastructure (e.g., AWS EC2, Google Compute Engine).
Platform as a Service (PaaS): Offers a platform for developers to build, deploy,
and manage applications (e.g., Heroku, Microsoft Azure).
Software as a Service (SaaS): Delivers software applications over the internet
(e.g., Gmail, Salesforce).
c. Virtualization: Technology that creates virtual versions of hardware and
resources, enabling multiple users to share the same physical resources.
d. Management Tools: Software for managing and monitoring resources, scaling
services, and ensuring performance. Examples: CloudWatch (AWS), Azure Monitor.
Components of cloud computing

3. Middleware:
Middleware acts as a bridge between the user interface and backend, enabling
communication
and connectivity between applications, services, and databases.
Example: Application programming interfaces (APIs) for accessing cloud services.

4. Security and Compliance:

Access Control: Ensures secure authentication and authorization.
Data Encryption: Protects data in transit and at rest.
Firewalls and Monitoring: Defend against cyberattacks and monitor system activity.
Regulatory Compliance: Ensures adherence to standards.

5. Deployment Models:
Public Cloud: Shared resources hosted by third-party providers (e.g., AWS, Google
Cloud).
Private Cloud: Dedicated infrastructure for a single organization.
Hybrid Cloud: Combines public and private clouds for flexibility.
Community Cloud: Shared infrastructure for organizations with similar needs.
Components of cloud computing

6. Application Layer:
This includes the software and services that run on the cloud platform.
Examples: CRM systems (Salesforce), collaboration tools (Slack), and cloud storage
apps (Dropbox).
6. Types of cloud computing service (EC2 , etc)

Computing and Containerization.

Here's a breakdown of these types with popular examples for each:
1. Infrastructure as a Service (IaaS)
IaaS provides the fundamental building blocks of computing infrastructure—servers,
storage, and networking—on a rental basis. It gives you the highest level of flexibility
and management control over your IT resources.
• Amazon EC2 (Elastic Compute Cloud): This is the quintessential IaaS service from
Amazon Web Services (AWS). It allows you to rent virtual servers (called instances)
on which you can run your own applications. You can choose the operating system,
memory, CPU, and storage, and you only pay for what you use. It's like having your
own server in the cloud.
• Microsoft Azure Virtual Machines: This is Microsoft's equivalent to EC2, allowing you
to create and manage virtual machines in the Azure cloud. It offers a wide range of
options for Linux and Windows virtual machines.
• Google Compute Engine (GCE): This is Google Cloud's service for creating and
running virtual machines on Google's infrastructure. It is known for its fast boot
times and high performance.
2. Platform as a Service (PaaS)
PaaS provides a platform that allows developers to build, run, and manage
applications without the complexity of building and maintaining the underlying
infrastructure. It's like a workshop where all the tools and infrastructure are provided
for you.
• AWS Elastic Beanstalk: An easy-to-use service for deploying and scaling web
applications and services developed with Java, .NET, PHP, Node.js, Python, Ruby, Go,
 and Docker. You simply upload your code, and Elastic Beanstalk automatically
handles the deployment, from capacity provisioning and load balancing to auto-
scaling and application health monitoring.
• Heroku: A popular PaaS that enables developers to build, run, and operate
applications entirely in the cloud. It's known for its simplicity and ease of use, making
it a favorite among startups and for smaller projects.
• Google App Engine: A fully managed, serverless platform for developing and hosting
web applications at scale. It supports a variety of popular programming languages
and allows developers to focus on writing code.
3. Software as a Service (SaaS)
SaaS delivers complete software applications over the internet on a subscription
basis. You don't have to worry about managing the software or the underlying
infrastructure; you just use the application.
• Google Workspace (formerly G Suite): A suite of cloud-based productivity and
collaboration tools, including Gmail, Google Drive, Google Docs, and Google Sheets.
You access and use these applications through a web browser without installing any
software.
• Microsoft 365: Similar to Google Workspace, it provides online versions of
Microsoft's popular productivity software, including Outlook, OneDrive, Word, Excel,
and PowerPoint.
• Salesforce: A leading customer relationship management (CRM) platform that is
delivered as a SaaS application. It helps businesses manage their sales, marketing,
and customer service activities.
4. Serverless Computing (Function as a Service - FaaS)
This is a newer model of cloud computing that allows you to run code without
provisioning or managing any servers. The cloud provider automatically allocates the
compute resources and you are only charged for the time your code is actually
running.
• AWS Lambda: A pioneer in the serverless space. It lets you run code in response to
events, such as an image being uploaded to an S3 bucket or a new entry in a
database. You simply write and upload a "function," and Lambda takes care of the
rest.
• Azure Functions: Microsoft's event-driven, serverless compute service that allows
you to run small pieces of code ("functions") without worrying about the application
infrastructure.
• Google Cloud Functions: A serverless execution environment for building and
connecting cloud services. It allows you to write simple, single-purpose functions
that are attached to events emitted from your cloud infrastructure and services.
5. Containerization Services
While not a traditional service model in the same vein as IaaS, PaaS, and SaaS,
containerization services have become a crucial part of the cloud computing
landscape. They allow you to package your application and its dependencies into a
single, isolated "container," which can then be run on any infrastructure.
• Amazon ECS (Elastic Container Service): A highly scalable, high-performance
container orchestration service that supports Docker containers. It allows you to
easily run and scale containerized applications on AWS.
• Amazon EKS (Elastic Kubernetes Service): A managed service that makes it easy to
run Kubernetes on AWS without needing to install and operate your own Kubernetes
control plane.
• Google Kubernetes Engine (GKE): Google's managed environment for deploying,
managing, and scaling containerized applications using Google infrastructure.

7. What are the 3 ways through which AWS services can be utilised:
Command line interface , SDK , Webbased applicatoin , console

1. AWS Management Console

This is the web-based application or graphical user interface (GUI) for AWS. You
access it through your web browser. It's user-friendly and ideal for visualizing your
cloud environment, managing resources manually, and viewing billing information.
This is what's meant by "console" and "web-based application".

2. AWS Command Line Interface (CLI)

The AWS CLI is a unified tool that allows you to control and manage AWS services
from your terminal or command prompt. It's powerful for automating repetitive tasks
and scripting cloud operations. You can use it to do everything the console can do,
but through text-based commands, making it a favorite for system administrators and
developers.

3. Software Development Kits (SDKs)

AWS provides SDKs for various programming languages (like Python, Java, JavaScript,
Go, etc.). These are libraries and tools that allow you to interact with AWS services
programmatically from your application's code. This is the method you use when you
want to integrate AWS functionality directly into your software, such as storing files
in Amazon S3 or querying a DynamoDB database from your application.
8. Describe the core components of the AWS Global Infrastructure,
detailing the relationship between Regions, Availability Zones, and
Data Centers. Explain four key factors you must consider when
choosing a specific AWS Region. Finally, define the 'Compute' category
of AWS services and provide two distinct examples.

AWS Global Infrastructure

The AWS Global Infrastructure is the physical foundation upon which all AWS cloud
services are built. It is designed for high availability, fault tolerance, and low latency.
The core components are:
1. Region: A Region is a physical, geographic location in the world, like us-east-1 (N.
Virginia) or ap-south-1 (Mumbai). Each Region is designed to be completely isolated
from the others, providing the highest degree of fault tolerance and stability.
2. Availability Zone (AZ): Each Region is composed of multiple, isolated locations
known as Availability Zones. An AZ consists of one or more discrete Data Centers,
each with redundant power, networking, and connectivity. By launching resources
across multiple AZs within a Region, an application can be protected from a single
point of failure (e.g., a fire or power outage in one data center).
3. Data Center: This is the secure physical facility that contains the thousands of
computer servers, storage devices, and networking equipment that power the cloud.
4. Edge Location: These are smaller sites, more numerous than Regions, that are used
by Amazon CloudFront (AWS's Content Delivery Network) to cache content closer to
end-users, drastically reducing latency for content delivery.
 The relationship is hierarchical: the global infrastructure is made up of Regions,
which are made up of Availability Zones, which are made up of one or more Data
Centers.

Factors for Choosing an AWS Region

Choosing the right AWS Region is a critical decision. The four primary factors to
consider are:
1. Latency: To provide the best experience for your users, you should choose a Region
that is physically closest to them. Lower latency means faster response times and
better performance for your application.
2. Cost: The pricing for AWS services can vary from one Region to another. These
differences are influenced by local taxes, real estate costs, and energy prices.
Choosing a less expensive Region can lead to significant cost savings.
3. Compliance and Data Sovereignty: Many countries have laws requiring that certain
types of data (like personal or government information) must remain within their
borders. You must select a Region that allows you to comply with these data
residency and sovereignty laws.
4. Service Availability: Not all AWS services are available in every Region, especially
newer ones. Before committing to a Region, you must verify that all the specific AWS
services your application requires are available there.

The 'Compute' Category in AWS

In AWS, the 'Compute' category refers to services that provide the processing power
required to run applications and execute workloads. These services are the "brains"
of a cloud environment, offering everything from virtual servers to serverless
execution environments. Essentially, they are services that perform calculations and
run code.
Two key examples of AWS Compute services are:
• Amazon EC2 (Elastic Compute Cloud): This is a foundational IaaS service that
provides secure, resizable virtual servers, known as "instances," in the cloud. It gives
users complete control over their computing resources, allowing them to choose the
operating system, memory, and CPU.
• AWS Lambda: This is a serverless compute service (FaaS) that runs code in response
to events without requiring you to provision or manage any servers. You simply
upload your code as a "function," and AWS handles the execution and scaling
automatically, charging you only for the compute time you consume.