Introduction
• In 2006, Amazon Web Services (AWS) began
offering IT infrastructure services to businesses in
the form of web services
• Today, Amazon Web Services provides a highly
reliable, scalable, low-cost infrastructure platform
in the cloud that powers hundreds of thousands of
businesses in 190 countries around the world.
Amazon Web Services Cloud
Platform
• AWS consists of many cloud services that user can
use in combinations tailored to their business or
organizational needs
• To access the services, user can use the AWS
Management Console or the Command Line
Interface
AWS Cloud Platform
• Compute • Benefits of EC2
– Amazon Elastic – Elastic Web-Scale
Compute Cloud Computing
(Amazon EC2) is a web – Completely Controlled
service that provides – Flexible Cloud Hosting
resizable compute Services
capacity in the cloud. It – Designed for use with
is designed to make other Amazon Web
web-scale computing Services
easier for developers – Reliable
– Secure
– Inexpensive
AWS Cloud Platform
• Compute
– Auto Scaling: allows users to scale
– Elastic Load Balancing: automatically distributes
incoming application traffic across multiple Amazon
EC2 instances in the cloud
– AWS Lambda: run code without provisioning or
managing servers.
– Amazon EC2 Container Service: is a highly scalable,
high performance container management service that
supports Docker containers
AWS Cloud Platform
• Storage and Content Delivery
– Amazon S3
– Amazon Glacier
– Amazon Elastic Block Store
– Amazon Elastic File System
– AWS Storage Gateway
– Amazon CloudFront
– AWS Import/Export Snowball
AWS Cloud Platform
• Database • Enterprise Applications
– Amazon Relational – Amazon WorkSpaces
Database Service – Amazon WorkDocs
– Amazon Aurora – Amazon WorkMail
– AWS Database
Migration Service
– Amazon DynamoDB
– Amazon Redshift
– Amazon ElastiCache
AWS Cloud Platform
• Networking • Application Services
– Amazon VPC – Amazon API Gateway
– AWS Direct Connect – Amazon AppStream
– Amazon Route 53 – Amazon CloudSearch
• Developer Tools – Amazon Elastic
– AWS CodeCommit Transcoder
– AWS CodeDeploy – Amazon SES
– AWS CodePipeline – Amazon SQS
– Amazon SWF
AWS Cloud Platform
• Management Tools • Security and Identity
– Amazon CloudWatch – AWS Identity and
– AWS CloudFormation Access Management
– AWS CloudTrail – AWS Key Management
– AWS Config Service
– AWS OpsWorks – AWS Directory Service
– AWS Service Catalog – Amazon Inspector
– AWS Trusted Advisor – AWS WAF
– AWS CloudHSM
AWS Cloud Platform
• Analytics • Internet of Things
– Amazon EMR – AWS IoT
– Amazon QuickSight • Mobile Services
– AWS Data Pipeline – AWS Mobile Hub
– Amazon Elasticsearch – Amazon Cognito
Service – Amazon Mobile
– Amazon Kinesis Analytics
– Amazon Machine – AWS Device Farm
Learning – Amazon SNS
– AWS Mobile SDK
Creating an Account in AWS
• Signup
• Credit/Debit Card Information
• Call Verification
• Support Plan
• Confirmation
AWS Free Tier Details
• 12 months free
• COMPUTE
– 750 HOURS per month on EC2
– 1 MILLION free requests per month on Lambda
• STORAGE & CONTENT DELIVERY
– 5GBof standard storage on S3
• DATABASE
– 750 HOURS per month of database usage on RDS
• ANALYTICS
– 1GB of SPICE capacity on QuickSight
Creating an Amazon EC2 Instance
• EC2 instance is virtual server in AWS terminology.
• EC2 is a web service where an AWS subscriber can
request and provision a compute server in AWS cloud.
• An on-demand EC2 instance is an offering from AWS
where the subscriber/user can rent the virtual server
per hour and use it to deploy his/her own
applications.
• The instance will be charged per hour with different
rates based on the type of the instance chosen.
• AWS provides multiple instance types for the
respective business needs of the user.
Login and access to AWS
services
• Login to AWS account
• Go to the AWS Services tab at the top left corner
• All of the AWS Services categorized as per their
area
• Choose the service you want to select for instance
we are using EC2
Login and access to AWS
services
Login and access to AWS
services
• Open all the services and click on EC2 under
Compute services.
• This will launch the dashboard of EC2.
• You will get all the information in gist about the
AWS EC2 resources running on EC2 dashboard.
Login and access to AWS
services
Login and access to AWS
services
• On the top right corner of the EC2 dashboard, choose the
AWS Region in which you want to provision the EC2
server.
Login and access to AWS
services
• Once your desired Region is selected, come back to
the EC2 Dashboard.
• Click on 'Launch Instance' button in the section of
Create Instance
• Instance creation wizard page will open as soon as
you click 'Launch Instance'
Login and access to AWS
services
Choose Amazon Machine
Image (AMI)
• You will be asked to choose an AMI of your choice
• Here we are choosing the default
Amazon Linux (64 bit) AMI.
Choose Instance Types
• In the next step, you have to choose the type of
instance you require based on your business
needs.
• We will choose t2.micro instance type, which is a
1vCPU and 1GB memory server offered by AWS.
• Click on "Configure Instance Details" for further
configurations
• In the next step of the wizard, enter details like no.
of instances you want to launch at a time.
• Here we are launching one instance.
Choose Instance Types
Configure Instance
• No. of instances- you can provision up to 20
instances at a time. Here we are launching
one instance.
Configure Instance
• Under Purchasing Options, keep the option
of 'Request Spot Instances' unchecked as of
now.
Configure Instance
• Next, we have to configure some basic networking details
for our EC2 server.
• You have to decide here, in which VPC (Virtual Private
Cloud) you want to launch your instance and under which
subnets inside your VPC
• Your AWS architecture set-up should include IP ranges for
your subnets etc. pre-planned for better management.
• Subnetting should also be pre-planned.
• Network section will give a list of VPCs available in our
platform.
• Select an already existing VPC
• You can also create a new VPC
Configure Instance
Configure Instance
• In this step,
• A VPC consists of subnets, which are IP ranges that
are separated for restricting access.
• Under Subnets, you can choose the subnet where
you want to place your instance.
• You can also create a new subnet in this step.
• Once your instance is launched in a public subnet,
AWS will assign a dynamic public IP to it from
their pool of IPs.
Configure Instance
Configure Instance
• You can choose if you want AWS to assign it an IP
automatically, or you want to do it manually later.
You can enable/ disable 'Auto assign Public IP'
feature here likewise.
Configure Instance
Configure Instance
• In this step, you have to do following things
• Shutdown Behavior – when you accidently shut down your
instance, you surely don't want it to be deleted but
stopped.
Configure Instance
• In this step,
• In case, you have accidently terminated your instance,
AWS has a layer of security mechanism. It will not delete
your instance if you have enabled accidental termination
protection.
Configure Instance
• In this step,
• Under Monitoring- you can enable Detailed
Monitoring if your instance is a business critical
instance.
• AWS will always provide Basic monitoring on your
instance free of cost.
• Under Tenancy- select the option if shared tenancy.
• If your application is a highly secure application, then
you should go for dedicated capacity.
• AWS provides both options.
Configure Instance
Configure Instance
• In this step,
• Click on 'Add Storage' to add data volumes to your
instance in next step.
Add Storage
• In this step we do following things,
• In the Add Storage step, you'll see that the instance
has been automatically provisioned a General Purpose
SSD root volume of 8GB. ( Maximum volume size we
can give to a General Purpose volume is 16GB)
• You can change your volume size, add new volumes,
change the volume type, etc.
• AWS provides 3 types of EBS volumes- Magnetic,
General Purpose SSD, Provisioned IOPs. You can
choose a volume type based on your application's IOPs
needs
Add Storage
Tag Instance
• In this step
• you can tag your instance with a key-value pair. This
gives visibility to the AWS account administrator
when there are lot number of instances.
• The instances should be tagged based on their
department, environment like Dev/SIT/Prod. Etc. this
gives a clear view of the costing on the instances
under one common tag.
• Here we have tagged the instance as a Dev_Web
server 01
• Go to configure Security Groups later
Tag Instance
Configuring Security Groups
• In this next step of configuring Security Groups, you can
restrict traffic on your instance ports.
• This is an added firewall mechanism provided by AWS apart
from your instance's OS firewall.
• You can define open ports and IPs.
• Since our server is a webserver, we will do following things
– Creating a new Security Group
– Naming our SG for easier reference
– Defining protocols which we want enabled on my instance
– Assigning IPs which are allowed to access our instance on
the said protocols
– Once, the firewall rules are set- Review and launch
Configuring Security Groups
Review Instances
• In this step, we will review all our choices and parameters
and go ahead to launch our instance.
Review Instances
• In the next step you will be asked to create a key pair to
login to you an instance. A key pair is a set of public-private
keys.
• AWS stores the private key in the instance, and you are
asked to download the public key. Make sure you
download the key and keep it safe and secured; if it is lost
you cannot download it again.
• Create a new key pair
• Give a name to your key
• Download and save it in your secured folder
Review Instances
Review Instances
• When you download your key, you can open and have a
look at your RSA private key.
Launch Instances
• Once you are done downloading and saving your key,
launch your instance.
Launch Instances
• You can see the launch status meanwhile.
Launch Instances
You can also see the launch log
Launch Instances
• Click on the 'Instances' option on the left pane where you
can see the status of the instance as 'Pending' for a brief
while. Once your instance is up and running, you can see its
status as 'Running' now.
• Note that the instance has received a Private IP from the
pool of AWS
Launch Instances
