`

UNIT-V
EXPLORING INFRASTRUCTURE
AS A SERVICE (IaaS)
T1: UNDERSTANDING AMAZON WEB SERVICES: Amazon Web Services (AWS) has a fascinating history
that traces its roots back to the early 2000s when Amazon.com was looking for ways to expand its business
and capitalize on its growing IT infrastructure. Here is a brief history of AWS:

1. Inception (Early 2000s):

 The idea for AWS began to take shape within Amazon.com when the company's engineers
realized that they could leverage their internal IT infrastructure, which was already
substantial due to the demands of the growing e-commerce giant.
2. Launch of AWS (March 14, 2006):
 AWS was officially launched on March 14, 2006, with the release of Amazon Simple Queue
Service (SQS) and Amazon Simple Storage Service (S3). These services marked the beginning
of AWS's cloud offerings.
3. Elastic Compute Cloud (EC2) (August 25, 2006):
 AWS introduced Amazon Elastic Compute Cloud (EC2), allowing customers to rent virtual
servers on-demand, which was a groundbreaking development in cloud computing. EC2
allowed businesses to scale their computing resources as needed.
4. Expansion and Innovation (Late 2000s to Early 2010s):
 AWS continued to expand its portfolio of services, adding Amazon RDS (Relational Database
Service), Amazon DynamoDB (NoSQL database service), and Amazon CloudFront (content
delivery network) among others.
 AWS also launched its first region outside of the United States in 2010 with the
establishment of the AWS EU (Ireland) region.
5. Mass Adoption (Mid-2010s):
 AWS experienced significant growth as more businesses and startups adopted its cloud
services. Companies of all sizes, from small startups to large enterprises, began using AWS to
power their applications and infrastructure.
6. Acquisitions and Expansions (2015-2017):
 AWS made strategic acquisitions, including Annapurna Labs, a semiconductor company, and
Cloud9 IDE, an integrated development environment. These acquisitions helped AWS further
expand its capabilities.
 In 2016, AWS launched its first AI and machine learning services, including Amazon Lex and
Amazon Polly.
7. Competition and Market Dominance (2010s):
 AWS faced increasing competition from other cloud providers like Microsoft Azure and
Google Cloud Platform (GCP). Despite the competition, AWS maintained its position as the
leading cloud provider.
8. Global Expansion (2010s):
 AWS expanded its global infrastructure with multiple regions and Availability Zones
worldwide. This expansion allowed customers to host their applications and data in regions
that were geographically closer to their users.
9. Innovation in AI and Machine Learning (2018-2019):
 AWS introduced services like Amazon SageMaker, a machine learning platform, and AWS
DeepRacer, a machine learning racing car, to make AI and ML more accessible to developers.
10. Ongoing Innovation (2020s):
 AWS continues to innovate and expand its offerings, with a focus on areas such as edge
computing, quantum computing, and sustainability. AWS also remains a leader in cloud
security and compliance.
------------------------------------------------------------------------------------------------------------------------------
T2: AMAZON WEB SERVICE COMPONENTS AND SERVICES

Amazon Web Services is comprised of the following components, listed roughly in their order of
importance:

 Amazon Elastic Compute Cloud

o Amazon Simple Queue Service
o Amazon Simple Notification Service
o Amazon CloudWatch
o Load Balancing
 Amazon Simple Storage System
 Amazon Elastic Block Store
 Amazon SimpleDB
 Amazon Relational Database Service
 Amazon Cloudfront

1.Amazon Elastic Compute Cloud (EC2; http://aws.amazon.com/ec2/), is the central application in the
AWS portfolio. It enables the creation, use, and management of virtual private servers running the Linux
or Windows operating system over a Xen hypervisor. Amazon Machine Instances are sized at various
levels and rented on a computing/ hour basis. Spread over data centers worldwide, EC2 applications
may be created that are highly scalable, redundant, and fault tolerant. EC2 is described more fully the
next section. A number of tools are used to support EC2 services:

 Amazon Simple Queue Service (SQS; http://aws.amazon.com/sqs/) is a message queue or

transaction system for distributed Internet-based applications. See “Examining the Simple
Queue Service (SQS)” later in this chapter for a description of this AWS feature. In a loosely
coupled SOA system, a transaction manager is required to ensure that messages are not lost
when a component isn’t available.
 Amazon Simple Notification Service (SNS; http://aws.amazon.com/sns/) is a Web service that
can publish messages from an application and deliver them to other applications or to
subscribers. SNS provides a method for triggering actions, allowing clients or applications to
subscribe to information (like RSS), or polling for new or changed information or perform
updates.
 EC2 can be monitored by Amazon CloudWatch (http://aws.amazon.com/ cloudwatch/), which
provides a console or command line view of resource utilization, site Key Performance Indexes
(performance metrics), and operational indicators for factors such as processor demand, disk
utilization, and network I/O. The metrics obtained by CloudWatch may be used to enable a
feature called Auto Scaling (http://aws.amazon.com/autoscaling/) that can automatically scale
an EC2 site based on a set of rules that you create. Autoscaling is part of Amazon Cloudwatch
and available at no additional charge.
 Amazon Machine Instances (AMIs) in EC2 can be load balanced using the Elastic Load Balancing
(http://aws.amazon.com/elasticloadbalancing/) feature. The Load Balancing feature can detect
when an instance is failing and reroute traffic to a healthy instance, even an instance in other
AWS zones. The Amazon CloudWatch metrics request count and request latency that show up in
the AWS console are used to support Elastic Load Balancing.

2.Amazon Simple Storage System (S3; http://aws.amazon.com/s3/) is an online backup and storage
system, which is described in “Working with Amazon Simple Storage System (S3)” later in this chapter. A
high speed data transfer feature called AWS Import/Export (http://aws.amazon. com/importexport/)
can transfer data to and from AWS using Amazon’s own internal network to portable storage devices.

3.Amazon Elastic Block Store (EBS; http://aws.amazon.com/ebs/) is a system for creating virtual disks
(volume) or block level storage devices that can be used for Amazon Machine Instances in EC2.

4.Amazon SimpleDB (http://aws.amazon.com/simpledb/) is a structured data store that supports

indexing and data queries to both EC2 and S3. SimpleDB isn’t a full database implementation, as you
learn in “Exploring SimpleDB (S3)” later in this chapter; it stores data in “buckets” and without requiring
the creation of a database schema. This design allows SimpleDB to scale easily. SimpleDB interoperates
with both Amazon EC2 and Amazon S3.

5.Amazon Relational Database Service (RDS; http://aws.amazon.com/rds/) allows you to create

instances of the MySQL database to support your Web sites and the many applications that rely on data-
driven services. MySQL is the “M” in the ubiquitous LAMP Web services platform (for Linux, APACHE,
MySQL, and PERL), and the inclusion of this service allows developers to port applications, their source
code, and databases directly over to AWS, preserving their previous investment in these technologies.
RDS provides features such as automated software patching, database backups, and automated
database scaling via an API call

6.Amazon Cloudfront (http://aws.amazon.com/cloudfront/) is an edge-storage or content-delivery

system that caches data in different physical locations so that user access to data is enhanced through
faster data transfer speeds and lower latency. Cloudfront is similar to systems such as Akamai.com, but
is proprietary to Amazon.com and is set up to work with Amazon Simple Storage System (Amazon S3).
Cloudfront is currently in beta, but has been well received in the trade press. See “Defining Cloudfront”
later in this chapter for more details.

While the list above represents the most important of the AWS offerings, it is only a partial list—a list
that is continually growing and very dynamic. A number of services and utilities support Amazon
partners or the AWS infrastructure itself.

7.Alexa Web Information Service ( http://aws.amazon.com/awis/ )

Alexa Top Sites http://aws.amazon.com/alexatopsites/) :-
Alexa Top Sites are two services that collect and expose information about the structure and traffic
patterns of Web sites. This information can be used to build or structure Web sites, access related sites,
analyze historical patterns for growth and relationships, and perform data analysis on site information.
Alexa Top Sites can rank sites based on their usage and be used to structure awareness of site popularity
into the structure of Web service you build.
8.Amazon Associates Web Services (A2S) is the machinery for interacting with Amazon’s vast product
data and eCommerce catalog function. This service, which was called Amazon E-Commerce Service
(ECS), is the means for vendors to add their products to the Amazon.com site and take orders and
payments.

9.Amazon DevPay (http://aws.amazon.com/devpay/) is a billing and account management service that

can be used by businesses that run applications on top of AWS. DevPay provides a developer API that
eliminates the need for application developers to build order pipelines, because Amazon does the billing
based on your prices and then uses Amazon Payments to collect the payments.

10.Amazon Elastic MapReduce (http://aws.amazon.com/elasticmapreduce/) is an interactive data

analysis tool for performing indexing, data mining, file analysis, log file analysis, machine learning,
financial analysis, and scientific and bioinformatics research. Elastic MapReduce is built on top of a
Hadoop framework using the Elastic Compute Cloud (EC2) and Simple Storage Service (S3).

11.Amazon Mechanical Turk (http://aws.amazon.com/mturk/) is a means for accessing human

researchers or consultants to help solve problems on a contractual or temporary basis. Problems solved
by this human workforce have included object identification, video or audio recording, data duplication,
and data research. Amazon.com calls this type of work Human Intelligence Tasks (HITs). The Mechanical
Turk is currently in beta.

12.AWS Multi-Factor Authentication (AWS MFA; http://aws.amazon.com/mfa/) is a special feature that

uses an authentication device you have in your possession to provide access to your AWS account
settings. This hardware key generates a pseudo-random sixdigit number when you press a button that
you enter into your logon. This gives you two layers of protection: your user id and password (things you
know) and the code from your hardware key (something you have). This multifactor security feature can
be extended to Cloudfront and Amazon S3 Secure access to your EC2 AMIs is controlled by passwords,
Kerberos, and 509 Certificates

13.Amazon Flexible Payments Service (FPS; http://aws.amazon.com/fps/) is a payments-transfer

infrastructure that provides access for developers to charge Amazon’s customers for their purchases.
Using FPS, goods, services, donations, money transfers, and recurring payments can be fulfilled. FPS is
exposed as an API that sorts transactions into packages called Quick Starts that make this service easy to
implement.

14.Amazon Fulfillment Web Services (FWS; http://aws.amazon.com/fws/) allows merchants to fill

orders through Amazon.com fulfillment service, with Amazon handling the physical delivery of items on
the merchant’s behalf. Merchant inventory is prepositioned in Amazon’s fulfillment centers, and
Amazon packs and ships the items. There is no charge for using Amazon FWS; fees for the Fulfillment by
Amazon (FBA; http:// www.amazon.com/gp/seller/fba/fulfillment-by-amazon.html) service apply.
Between FBA and FWS, you can create a nearly virtual store on Amazon.com.

15.Amazon Virtual Private Cloud (VPC; http://aws.amazon.com/vpc/) provides a bridge between a

company’s existing network and the AWS cloud. VPC connects your network resources to a set of AWS
systems over a Virtual Private Network (VPN) connection and extends security systems, firewalls, and
management systems to include their provisioned AWS servers. Amazon VPC is integrated with Amazon
EC2, but Amazon plans to extend the capabilities of VPC to integrate with other systems in the Amazon
cloud computing portfolio.

16.AWS Premium Support (http://aws.amazon.com/premiumsupport/) is Amazon’s technical support

and consulting business. Through AWS Premium Support, subscribers to AWS can get help building or
supporting applications that use EC2, S3, Cloudfront, VPC, SQS, SNS, SimpleDB, RDS, and the other
services listed above. Service plans are available on a per-incidence, monthly, or unlimited basis at
different levels of service

-----------------------------------------------------------------------------------------------------------------------------
T3: WORKING WITH THE ELASTIC COMPUTE CLOUD (EC2)
Amazon Elastic Compute Cloud (EC2) is a virtual server platform that allows users to create and run
virtual machines on Amazon’s server farm. With EC2, you can launch and run server instances called
Amazon Machine Images (AMIs) running different operating systems such as Red Hat Linux and
Windows on servers that have different performance profiles. You can add or subtract virtual servers
elastically as needed; cluster, replicate, and load balance servers; and locate your different servers in
different data centers or “zones” throughout the world to provide fault tolerance. The term elastic
refers to the ability to size your capacity quickly as needed.

Consider a situation where you want to create an Internet platform that provides the following:

 A high transaction level for a Web application

 A system that optimizes performance between servers in your system
 Data driver information services
 Network security
 The ability to grow your service on demand

Implementing that type of service might require a rack of components that included the following:

 An application server with access to a large RAM allocation

 A load balancer, usually in the form of a hardware appliance such as F5’s BIG-IP
 A database server
 Firewalls and network switches
 Additional rack capacity at the ISP

Amazon Machine Images AMIs are operating systems running on the Xen virtualization hypervisor.
Each virtual private server is accorded a size rating called its EC2 Compute Unit

 Standard Instances: The standard instances are deemed to be suitable for standard server
applications.
 High Memory Instances: High memory instances are useful for large data throughput
applications such as SQL Server databases and data caching and retrieval.
 High CPU Instances: The high CPU instance category is best used for applications that are
processor- or compute-intensive. Applications of this type include rendering, encoding, data
analysis, and others.
Pricing models:- The pricing of these different AMI types depends on the operating system used,
which data center the AMI is located in (you can select its location), and the amount of time that the
AMI runs. Rates are quoted based on an hourly rate. Additional charges are applied for:

 The amount of data transferred

 Whether Elastic IP Addresses are assigned
 Your virtual private server’s use of Amazon Elastic Block Storage (EBS)
 Whether you use Elastic Load Balancing for two or more servers
 Other features

AMIs that have been saved and shut down incurs a small one-time fee, but do not incur additional
hourly fees.
The three different pricing models for EC2 AMIs are as follows:
 On-Demand Instance: This is the hourly rate with no long-term commitment.
  Reserved Instances: This is a purchase of a contract for each instance you use with a
significantly lower hourly usage charge after you have paid for the reservation.
 Spot Instance: This is a method for bidding on unused EC2 capacity based on the current spot
price. This feature offers a significantly lower price, but it varies over time or may not be
available when there is no excess capacity
NOTE:- The AWS Simple Monthly Calculator help you estimate your monthly charges.
http://calculator.s3. amazonaws.com/calc5.html

System images and software: Choose & use a template AMI system image with the operating system
of your choice or create your own system image that contains your custom applications, code libraries,
settings, and data. Security can be set through passwords, Kerberos tickets, or certificates.
These operating systems are offered:
 Red Hat Enterprise Linux OS
 OpenSuse Linux OS
 Ubuntu Linux OS
 Sun OpenSolaris OS
 Fedora OS
 Gentoo Linux OS
 Oracle Enterprise Linux OS
 Windows Server 2003/2008 32-bit and 64-bit up to Data Center Edition OS
 Debian OS
Note:- When you create a virtual private server, you can use the Elastic IP Address feature to create
what amounts to a static IPv4 address to your server. This address can be mapped to any of your AMIs
and is associated with your AWS account.

There are currently many different EC2 service zones or regions:

 Asia Pacific Mumbai( ap-south-1)
 Asia Pacific Singapore (ap-southeast-1)
 US East (Northern Virginia)
 US West (Northern California)

Creating an AWS account

1. Visit the AWS website: Go to the AWS official website at https://aws.amazon.com/.
2. Click on "Sign Up": Look for the "Create an AWS Account" or "Sign Up" button on the AWS
homepage and click on it.
3. Provide your email address: Enter your email address, and choose whether you're creating an
AWS account for personal or business use.
4. Fill in the required information: You'll need to provide your name, company (if applicable), and
contact information.
5. Choose an AWS support plan: AWS offers different support plans, including a free tier with
limited services. Select the plan that best suits your needs.
6. Enter payment information: You'll be asked to provide your payment details, including a credit
card number. AWS may charge a small verification fee, which will be refunded later.
7. Verify your identity: AWS may ask you to verify your identity through a phone call or text
message.
8. Accept the AWS Customer Agreement: Read and accept the AWS Customer Agreement and the
AWS Service Terms.
9. Complete the registration: Once you've provided all the necessary information and accepted the
terms, your AWS account will be created.
Creating an instance on EC2
1. Create VPC Network with IP range for your VPC (e.g., 10.0.0.0/16).
2. Create Subnet with IP range for your VPC (e.g., 10.0.1.0/24 | 10.0.2.0/24).
3. Create an Internet Gateway (IGW) & associate VPC
4. Create Route Table & associate with VPC
5. Edit routes & add a new route with destination 0.0.0.0/0 and target as the IGW
6. Associate private Subnet with Route Table, so subnets will become public
7. Launch Ec2 Instance in Public subnet to create a new EC2 instance.
8. Choose an Amazon Machine Image (AMI) for your instance, e.g., Amazon Linux 2.
9. Select an instance type with 2GB RAM and 200GB storage, like t2.micro or t3.micro.
10. Configure instance details, including selecting the VPC you created earlier and choosing the
public subnet.
11. Create a Key pair ( PEM | PPK )- & it is used to securely connect to your instance using SSH |RDP
12. Configure Firewall security groups to allow HTTP (80) | HTTPS (443)and SSH ( 22) traffic.
13. Review and launch the instance.
-------------------------------------------------------------------------------------------------------------------------------
T3: WORKING WITH AMAZON STORAGE SYSTEMS

Creating an Amazon Machine Instance or provision it with a certain amount of storage. That storage is
temporal; It only exists for as long as your instance is running. All of the data contained in that storage is
lost when the instance is suspended or terminated, as the storage is reassigned to the pool for other
AWS users to use. For this and other reasons you need to have access to persistent storage(S3 BUCKET )

1.Amazon Simple Storage System (S3): Amazon S3’s cloud-based storage system allows you to store
data objects ranging in size from 1 byte up to 5GB in a flat namespace. In S3, storage containers are
referred to as buckets, and buckets serve the function of a directory, although there is no object
hierarchy to a bucket, and you save objects and not files to it. It is important that you do not associate
the concept of a file system with S3, because files are not supported; only objects are stored.
Additionally, not needed to “mount” a bucket as you do a file system.

You can do the following with S3 buckets through the APIs:

 Create, edit, or delete existing buckets

 Upload new objects to a bucket and download them
 Search for and find objects and buckets
 Find metadata associate with objects and buckets
 Specify where a bucket should be stored
 Make buckets and objects available for public access
Amazon Simple Storage Service (S3) provides secure, durable, and highly scalable object storage. To
upload data such as photos, videos, and static documents, you must first create a logical storage bucket
in one of the AWS regions. Then you can upload any number of objects to it. Buckets and objects are
resources, and Amazon S3 provides both APIs and a web console to manage them.

Amazon S3 can be used alone or together with other AWS services such as Amazon EC2, Amazon Elastic
Block Store (Amazon EBS), and Amazon Glacier, as well as third-party storage repositories and gateways.
Amazon S3 provides cost-effective object storage for a wide variety of use cases including web
applications, content distribution, backup and archiving, disaster recovery, and big data analytics.

Creating a backup process in Amazon S3 involves a few key steps to ensure your data is securely backed
up and can be easily restored when needed. Here's a general outline of the process:

1. Set Up an Amazon S3 Bucket:

 Log in to your AWS Management Console.
 Create the bucket.
2. Configure Data Backup:
 Decide what data you want to back up to your S3 bucket. This could include files, databases,
server logs, and more.
 Depending on your data source, you might use AWS services like AWS Backup, AWS DataSync, or
write custom scripts to transfer data to your S3 bucket.
3. Data Transfer to S3:
 Use the AWS CLI, SDKs, or other transfer methods to upload your data to the S3 bucket.
 Ensure that you organize your data within the bucket with appropriate folder structures to make
it easy to locate and restore.
4. Enable Versioning (Optional):
 Enabling versioning in your S3 bucket allows you to store multiple versions of an object. This can
be beneficial for accidental deletions or changes.
 To enable versioning, go to your bucket's properties in the AWS Management Console, and under
the "Versioning" tab, click "Enable versioning."
5. Data Encryption:
 Consider enabling server-side encryption (SSE) for your S3 objects to protect your data at rest.
SSE can use AWS-managed keys (SSE-S3) or AWS Key Management Service (KMS) keys (SSE-KMS)
for encryption.
 You can also implement client-side encryption if you want to encrypt data before uploading it to
S3.
6. Access Control:
 Define access control policies using bucket policies, access control lists (ACLs), and IAM (Identity
and Access Management) to restrict who can access and manage your data in the S3 bucket.
 Ensure that you maintain proper permissions for backup and restore processes.
7. Backup Frequency and Retention:
 Determine your backup frequency. This could be daily, weekly, or according to a specific
schedule.
 Set retention policies to define how long you want to keep backups. AWS Backup, if used, can
help manage retention policies.
8. Monitoring and Alerts:
  Configure monitoring and alerts using AWS CloudWatch to track the health and status of your
backups.
 Set up notifications to alert you in case of backup failures or other issues.
9. Testing Backup and Restore:
 Periodically test your backup and restore processes to ensure that they work as expected. This
will help you verify the integrity of your backups.
10. Disaster Recovery Plan:
 Develop a disaster recovery plan that outlines the steps to follow in case of data loss or other
disasters.
 Test your disaster recovery plan to ensure that you can successfully recover data from your
backups.
NOTE:- Amazon S3 is highly reliable, it is not highly available. You can definitely get your data back from
S3 at some point with guaranteed 100% fidelity, but the service is not always connected and experiences
service outages. By comparison, an EBS volume is offered with an annual failure rate of 0.1% to 0.5%,
about a factor of 10 better than typical disk drives you use in your own physical servers

2.Amazon Elastic Block Store (EBS): Amazon Elastic Block Store (Amazon EBS) is a block storage service
provided by Amazon Web Services (AWS) that allows you to create and attach persistent block storage
volumes to your Amazon EC2 (Elastic Compute Cloud) instances. EBS volumes are designed for high
availability and durability and provide scalable and reliable block-level storage for your EC2 instances.

Here are some key features and concepts associated with Amazon EBS:

1. Volume Types:
 Amazon EBS offers different volume types optimized for various workloads:
 General Purpose (SSD): Provides a balance of price and performance. Suitable
for a wide range of workloads.
 Provisioned IOPS (SSD): Designed for I/O-intensive applications, allowing you to
provision a specific number of IOPS (input/output operations per second).
 Cold HDD: Offers low-cost storage for infrequently accessed data.
 Throughput Optimized HDD: Designed for big data and data warehousing
workloads that require high throughput.
 I/O Optimized HDD: Designed for big data and data warehousing workloads that
require high IOPS.
 You can choose the most appropriate volume type based on your application's
performance and cost requirements.
2. Volume Size and Attach/Detach:
 EBS volumes can range in size from 1 GB to 16 TB, depending on the volume type.
  You can attach and detach EBS volumes from EC2 instances, allowing you to move data
between instances or resize volumes as needed.
3. Snapshots:
 EBS snapshots are point-in-time copies of your EBS volumes.
 You can use snapshots to back up your data, create new volumes, and migrate data to
other AWS regions.
 Snapshots are incremental, meaning that only changed data is stored, which helps in
reducing storage costs.
4. Encryption:
 EBS volumes support encryption at rest using AWS Key Management Service (KMS) keys.
 You can encrypt both the root volume of an EC2 instance and additional data volumes.
5. Availability and Durability:
 EBS volumes are designed for high availability and durability. They are replicated within
an Availability Zone (AZ) to protect against component failures.
 You can also create EBS snapshots and copy them to different regions for added data
resilience.
6. Performance Scaling:
 For performance-intensive workloads, you can dynamically resize and scale EBS volumes
to meet the performance requirements of your applications.
 Provisioned IOPS volumes allow you to provision a specific level of performance.
7. Multi-Attach (Beta):
 Some EBS volume types support multi-attach, allowing you to attach a single volume to
multiple EC2 instances simultaneously.
 This can be useful for shared storage scenarios.
8. Lifecycle Management:
 EBS offers features like EBS Lifecycle Manager to automate the creation, retention, and
deletion of snapshots based on policies.
9. Use Cases:
 Amazon EBS is commonly used for various use cases, including database storage, file
storage, boot volumes for EC2 instances, and application data storage.
10. Pricing:
 EBS pricing is based on the volume type, size, and region. You pay for the provisioned
storage capacity and the volume type's performance characteristics.

NOTE:- Amazon EBS plays a critical role in providing scalable and persistent storage for AWS EC2
instances, making it an essential component for running various workloads in the AWS cloud.

3.Amazon CloudFront

Amazon CloudFront is a content delivery network (CDN) service provided by Amazon Web Services
(AWS). It is designed to distribute content, including web pages, media files, and application data, to
users worldwide with low-latency and high data transfer speeds. CloudFront uses a global network of
edge locations to cache and deliver content to users from the nearest location, reducing latency and
improving the overall user experience.
Key features and concepts associated with Amazon CloudFront include:

1. Content Delivery: CloudFront accelerates the delivery of your content by caching it at edge
locations around the world. When a user requests content, CloudFront serves it from the
nearest edge location, reducing the round-trip time and improving load times.
2. Edge Locations: CloudFront has a network of edge locations strategically located in multiple
regions worldwide. These edge locations are where your cached content is stored and served
from. AWS continuously adds new edge locations to expand its global reach.
3. Distribution: To use CloudFront, you create a distribution, which is a collection of settings and
configuration information related to how CloudFront should cache and serve your content.
There are two types of distributions:
 Web Distribution: Used for websites and web applications.
 RTMP (Real-Time Messaging Protocol) Distribution: Used for streaming media over
Adobe Flash Media Server.
4. Origin: An origin is the source of your content. It can be an Amazon S3 bucket, an EC2 instance,
a load balancer, or even a custom HTTP server. CloudFront retrieves content from the origin and
caches it at edge locations.
5. Cache Behavior: You can define cache behaviors to specify how CloudFront should handle
requests for different types of content. For example, you can configure different TTLs (Time to
Live) for various file types.
6. HTTPS Support: CloudFront supports HTTPS to secure the transmission of data between your
users and the edge locations. You can use AWS Certificate Manager (ACM) to provision free
SSL/TLS certificates.
7. Logging and Monitoring: CloudFront provides access logs that can be sent to Amazon S3 or
Amazon CloudWatch for monitoring and analysis. You can track viewer activity and performance
metrics.
8. Customization: You can customize the behavior of CloudFront using features like
Lambda@Edge, which allows you to run serverless functions at the edge locations to modify
content or responses dynamically.
9. Security: You can use AWS Identity and Access Management (IAM) to control access to your
CloudFront distributions. You can also use AWS Web Application Firewall (WAF) to protect
against web application attacks.
10. Geo-Restriction: CloudFront allows you to restrict access to your content based on geographic
locations, helping you comply with content distribution regulations.
11. Cost Management: CloudFront pricing is based on data transfer and the number of requests.
You can use AWS Cost Explorer to monitor and manage your CloudFront costs.
 WORKING MODEL AMAZON CLOUDFRONT

NOTE:- CloudFront is a highly scalable and globally distributed CDN service that can significantly improve
the performance, availability, and security of your web applications and content delivery. It is widely
used by websites, mobile apps, and streaming platforms to deliver content efficiently to users
worldwide.

T4: UNDERSTANDING AMAZON DATABASE SERVICES:

Amazon offers two different types of database services:

 Amazon SimpleDB, (Non-relational)
 Amazon Relational Database Service (Amazon RDS)
Dynamic data access is a central element of Web services, particularly “Web 2.0” services, so although
AMIs support several of the major databases.

1.Amazon SimpleDB
Amazon SimpleDB, also known as Amazon Simple Database, was a fully managed NoSQL database
service offered by Amazon Web Services (AWS). AWS announced that they were retiring Amazon
SimpleDB, and they were no longer accepting new sign-ups for the service.

Here are some key characteristics and features of Amazon SimpleDB as it existed before its retirement:
1. Schema-less: Amazon SimpleDB was a schema-less database, meaning you could store data
without predefining a fixed schema. This made it flexible for handling various types of data.
2. Data Attributes: Instead of tables, SimpleDB used domains to store data. Each domain could
have multiple data attributes, which were key-value pairs.
 3. Automatic Scaling: SimpleDB automatically scaled to handle increasing workloads by
distributing data across multiple servers.
4. High Availability: It provided high availability with data replication across multiple Availability
Zones within a region.
5. Query Language: SimpleDB used a query language called SimpleDB Query Language (SQL),
which allowed for querying and filtering data based on attribute values.
6. Consistency Model: It offered eventual consistency for read operations, which means that data
might not immediately reflect updates but would eventually converge to a consistent state.
7. Limited Indexing: SimpleDB supported indexing of attributes, which allowed for efficient
querying of data.
8. Usage-Based Pricing: Billing was based on actual usage, including the amount of data stored,
the number of requests, and data transfer.

2.Amazon Relational Database Service (RDS)

Amazon Relational Database Service (Amazon RDS) is a fully managed relational database service
provided by Amazon Web Services (AWS). It makes it easier to set up, operate, and scale a relational
database in the cloud. Amazon RDS supports various database engines, including:

1. MySQL: A popular open-source relational database management system.

2. PostgreSQL: Another powerful open-source relational database system known for its robustness
and extensibility.
3. MariaDB: A community-developed fork of MySQL, designed for high performance and reliability.
4. Oracle: A commercial relational database management system known for its scalability and
advanced features.
5. Microsoft SQL Server: A commercial database management system from Microsoft with robust
enterprise-level capabilities.
6. Amazon Aurora: Amazon's own relational database engine compatible with MySQL and
PostgreSQL, offering high performance, availability, and scalability.

Amazon RDS simplifies database management tasks such as provisioning, patching, backup, recovery,
and scaling, allowing developers and database administrators to focus on application development
rather than infrastructure management.
Key features of Amazon RDS include:

1. Automated Backups: Amazon RDS automatically takes daily backups of your database and
allows you to retain backups for a specified period, making data recovery easier.
2. High Availability: Amazon RDS provides options for high availability, including Multi-AZ
deployments, which replicate your database across multiple availability zones for failover
protection.
3. Scalability: You can easily scale your database instance vertically by changing its instance type or
horizontally by adding read replicas to offload read traffic.
4. Security: Amazon RDS offers security features like network isolation, encryption at rest and in
transit, IAM database authentication, and automated software patching to enhance database
security.
5. Monitoring and Metrics: You can use Amazon CloudWatch to monitor database performance
and set up alarms to be notified of any issues.
6. Database Engine Compatibility: Amazon RDS provides options to select the database engine
that best fits your application's needs, and it manages the underlying infrastructure for you.
7. Ease of Maintenance: Routine database maintenance tasks such as software patching, hardware
scaling, and backups are automated, reducing the administrative overhead.
3.Choosing a database for AWS.
In choosing a database solution for your AWS solutions, consider the following factors in making your
selection:

 Choose SimpleDB when index and query functions do not require relational database
support.
 Use SimpleDB for the lowest administrative overhead.
 Select SimpleDB if you want a solution that autoscales on demand.
 Choose SimpleDB for a solution that has a very high availability.
 Use RDS when you have an existing MySQL database that could be ported and you want
to minimize the amount of infrastructure and administrative management required.
 Use RDS when your database queries require relation between data objects.
 Chose RDS when you want a database that scales based on an API call and has a pay-asyou-use-
it pricing model.
 Select Amazon EC2/Relational Database AMI when you want access to an enterprise relational
database or have an existing investment in that particular application.
 Use Amazon EC2/Relational Database AMI to retain complete administrative control over
your database server.