Before the cloud – Example 1 – Online Shopping App

 Challenge:
 Peak usages during holidays and Weekends.
 Less load during less of the time.
 Solution (Before the Cloud)
 Procure (Buy) infrastructure for peak load.

Before the cloud – Example 2 – Start-up

 Challenge:
 It suddenly becomes popular.
 How to handle sudden increase in Load?
 Solution (before the Cloud)
 Procure (Buy) infrastructure assuming they would be successful.
o What if they are not successful?

Before the cloud – Challenges

 High cost of procuring Infrastructure.
 Needs ahead of Time Planning (Can you guess the future?)
 Low infrastructure utilization.
 Dedicated infrastructure maintenance team (Can a start-up afford it?)

Silver Lining in the Cloud

 How about provisioning (renting) resources when you want them and releasing them back
when you don’t need them?
 This is also called on–Demand resource provisioning.
 Also called Elasticity.
Cloud – Advantages
 Trade “capital expense” for “variable expense”.
 What is Capital expense: - It’s something which we put ahead of time.
 What is variable expense: - We are renting resource on cloud based on the needs and once
we use them, we can release them back.
 Benefit from massive economics of scale.
 Stop guessing capacity.
 Increase speed and agility.
 Stop spending money running and maintaining the data centers.
 “Go Global” in minutes.

Amazon Web Services (AWS)

 It’s the leading cloud services provider.
 Competitors for AWS: - Azure and Google Cloud.
 Provides most (200+) services.
 Reliable, secure and cost effective.

Best path to learn AWS!

 Cloud applications make use of multiple AWS services.

 There is no single path to learn these services independently.
 However, I have worked out a simple path!

Setting up AWS account

 Create AWS account.
 Setup an IAM user.
 You are creating your “AWS Root Account”.
Now we will understand types of Users
 Root User: - When we first time we created the AWS account with the email id and
password, this is what we called Root user. The root user can be used for both Console
access as well as programmatic access to the application. The root user has complete
access everything within AWS account. He/she can even close anybody AWS account. So,
it’s strongly recommended not to use Root user for your day-to-day activities, even for the
administrative activities. It’s better to create different set of users called the IAM users
(Identity and Access Management). Therefore, the only things we should do with Root
user is to first create an IAM user and lock down the credentials somewhere secure.
 Now, we will see how to create IAM user.