Introduction to Cloud Computing

1. Introduction to cloud computing
www.edureka.co/cloudcomputing

2. What is Cloud Computing? (Contd.)
It’s a
Spear!
It’s a Fan!
It’s a
Snake!
It’s a Tree!
It’s a
Rope!
It’s a Wall!
Slide 2 www.edureka.co/cloudcomputing

3. Cloud Introduction
 According to Forrester, Cloud Computing is:
“A form of standardized IT-based capability — such as Internet-
based services, software, or IT infrastructure — offered by a
service provider that is accessible via Internet protocols from any
computer, is always available and scales automatically to adjust to
demand, is either pay-per-use or advertising-based, has Web- or
programmatic-based control interfaces, and enables full customer
self-service.”
Slide 3 www.edureka.co/cloudcomputing

4. Cloud Introduction
Slide 4 www.edureka.co/cloudcomputing
 According to NIST, Cloud Computing is:
“Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing
resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with
minimal management effort or service provider interaction. This cloud model promotes availability and is composed of five
essential characteristics, three service models, and four deployment models.” - (NIST)

5. Cloud Introduction
Public Cloud
(multi-
tenant)
Deployment
Models
Service
Models
Attributes
Broad Network
Access
Rapid Elasticity
Measured Service
/Pay as you go
On Demand self-
service
Resource Pooling
Hybrid
Software as a Service
(SaaS)
CRM, Email, Social
Collaboration, Payment
and Reconciliation
Platform as a Service
(PaaS)
Middleware, Database,
Build/Dev/Test
Infrastructure as a
Service (IaaS)
Compute, Storage,
Network, Desktop
Anything as
a Service
(XaaS)
Slide 5 www.edureka.co/cloudcomputing
Community
(Special purpose/group)
Private Cloud
(single-tenant)
http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf

6. Cloud Delivery Models
 Software as a Service (SaaS):
» The application is hosted centrally
» Software testing takes place at a faster rate
» Reduction in IT operational costs
» No need to install new software to release updates
 Platform as a Service (PaaS):
» Facilitation of hosting capabilities
» Designing and developing the application
» Integrating web services and databases
» Providing security, scalability and storage
 Infrastructure as a Service (IaaS):
» Virtualization of Desktop
» Internet availability
» Use of billing model
» Computerized administrative tasks
Slide 6 www.edureka.co/cloudcomputing

7. What does Pay-as-you-go Mean?
Service
Model
Typical Unit of Measure Typical values
SaaS Per user per month,
Per location per month, etc.
No norm. The vendor is free to set his
pricing and the unit of measure!
PaaS Per GB per month for DBs,
Per connection per month for integration layer,
Data Transfer In/Out
10 USD/GB-month
IaaS Instance-hours per month,
Data Transfer in/Out,
GB per month for storage
10 cents/hour
10 cents/GB – in, 15 cents/GB-out
10 cents/GB-month
Slide 7 www.edureka.co/cloudcomputing

8. Sample Benefits and Risks for Cloud Types
Service
Model
Benefits Risks Best Fit
IaaS
On-Demand Infrastructure Security
Data persistence
Data aggregation
Business Risk of Outages
Service failures can affect
multiple tenants and
customers
Non-legacy apps
Consolidation Efforts
Hosting for Dev & Test
PaaS
Standardized development
environment
Rapid development & testing
Similar risks as above
Vendor Lock-in
New application development
Application development that uses
provider building blocks to reduce
time-to-market
SaaS
Re-usable services
Only requires limited
configuration & management
Similar risks as IaaS
Lack of control
Vendor Lock-in
Configuration over customization
Commoditized applications
Slide 8 www.edureka.co/cloudcomputing

9. Distribution of Control between Service Models
Slide 9 www.edureka.co/cloudcomputing

10. Cloud Computing Deployment Models
Slide 10 www.edureka.co/cloudcomputing

11. Hybrid Cloud
 Hybrid Cloud consisting of multiple internal and/or external
providers will be typical for most of the enterprises
 Example : GoGrid, Amazon VPC
Slide 11 www.edureka.co/cloudcomputing

12. Sample Benefits and Risks for Cloud Models
Delivery
Model Benefits Risks Best Fit
Public
 Costs
 Time-to-Market
 Elasticity
 Self-Service
 Simplicity
 Lack of Control
 Security
 Regulatory & Compliance
 Data Migration
 Application Development
 Software Licensing
 Vendor Lock-In
 Limitations
 Applications and Data that can be publicly hosted
 Applications that can be easily moved or ported to
commodity virtual platforms
Private
 Control
 Security
 Compliance
 Scale
 Management Tools
 Charge-back
 Adoption
 ROI
 Applications and data that can not be hosted publicly for
security or compliance reasons
 Applications and data the require a high-level of control
Hybrid
 Flexibility
 Security
 Efficiencies
 Multiple Points of Failure
 Same risks as public and
private clouds
 When it is required to separate applications and data
between private and public clouds
 When public clouds can not accommodate requirements
 When public cloud resources are only required temporarily
and workloads can be migrated betweenclouds
Slide 12 www.edureka.co/cloudcomputing

13. Key Characteristics
Slide 13 www.edureka.co/cloudcomputing
 Agility :
» Improves with users able to rapidly and inexpensively re-provision technological infrastructure resources
 Cost (Pay as You Go) :
» Cost is greatly reduced and capital expenditure is converted to operational expenditure . Also you can convert
fixed cost to variable
 Device and location independence :
» Enable users to access systems using a web browser regardless of their location or what device they are using,
e.g., PC, mobile
 Multi-tenancy:
» Enables sharing of resources and costs among a large pool of users, allowing for:
» Centralization of infrastructure in areas with lower costs (such as real estate, electricity, etc.)
» Peak-load capacity increases (users need not engineer for highest possible load-levels)
» Utilization and efficiency improvements for systems that are often only 10-20% utilized

14.  Reliability : improves through the use of multiple redundant sites, which makes it suitable for business continuity
and disaster recovery
 Scalability : via dynamic ("on-demand") provisioning of resources on a fine-grained, self-service basis near real-
time, without users having to engineer for peak loads
 Sustainability : comes about through improved resource utilization, more efficient systems, and carbon neutrality.
Nonetheless, computers and associated infrastructure are major consumers of energy
 Virtualized : applications are decoupled from the underlying hardware. Multiple applications can run on one
computer (virtualization a la VMWare) or multiple computers can be used to run one application
Slide 14 www.edureka.co/cloudcomputing
Key Characteristics

15. Typical Use Case for Cloud
Infrastructure
Transformation
SaaS (e-mail,
collaboration, etc. )
Dev and Test Hosted Solutions Content Delivery
Networks
High performance
Computing
POCs Backup DR VPCs/ Private
Clouds
Slide 15 www.edureka.co/cloudcomputing

16. Verticals Cloud Caters to
Insurance
Education
Healthcare
Manufacturing
$
$
Banking
Accounts for 20% of public
storage
Communication
& Media
Suffer legacy drag, but still
a leader in Cloud
Initially just email and DR
A place to test
"beachheads" or industry-
specific cloud platforms –
less regularly/ compliance
constrained
Driven by mobile, storage,
budget cuts and hybrid
classes
CRM is most popular app
Slide 16 www.edureka.co/cloudcomputing

17. Cloud & Open Source
Open Source in IAAS
Open Source in IAAS
Open Source in IAAS
Open Source in IAAS
Open Source in PAAS
Open Source in PAAS
Slide 17 www.edureka.co/cloudcomputing

18. Cloud Computing Concerns
Slide 18 www.edureka.co/cloudcomputing
 Loss of control
 Integration: enterprise & federated authorization
 Interoperability: with key enterprise applications
 Accessibility and UI limitations of web apps
 Reliability, performance, security; offline access
 Features; changes; vendor lock-in

19. Cloud Computing Concerns
Slide 19 www.edureka.co/cloudcomputing
 Policy/compliance concerns (privacy)
 Breach forensics and mitigation
 Business “surprises”
 Support; More Logins
 Consequences of “Creative Destruction”

20. Security issues in Cloud Computing
https://downloads.cloudsecurityalliance.org/initiatives/top_threats/The_Notorious_Nine_Cloud_Computing_Top_Threats_in_2013.pdf
Notorious Nine
1. Data Breaches
2. Data Loss
3. Account Hijacking
4. Insecure APIs
5. Denial of Service
6. Malicious Insiders
7. Abuse of Cloud Services
8. Insufficient Due Diligence
9. Shared TechnologyIssues
Slide 20 www.edureka.co/cloudcomputing

21. Amazon Web Services
Slide 21 www.edureka.co/cloudcomputing

22. Why AWS?
Slide 22 www.edureka.co/cloudcomputing

23. Regions & Zones
 Amazon EC2 provides the ability to place instances in multiple
locations
» Amazon EC2 locations are composed of Availability Zones
and Regions
 By launching instances in separate Regions, you can design
your application to be closer to specific customers or to meet
legal or other requirements
» By launching instances in separate Availability Zones, you
can protect your applications from the failure of a single
location
Ref: http://aws.amazon.com/about-aws/globalinfrastructure/
Slide 23 www.edureka.co/cloudcomputing

24. Regions & Zones
http://harish11g.blogspot.in/2012/07/amazon-availability-zones-aws-az.html
11 regions
30 availability zones
53 edge locations
Slide 24 www.edureka.co/cloudcomputing

25. Regions & Zones
Availability
Zone C
US West Region -1 (N.CA)
Availability
Zone A
Availability
Zone B
South America (Sou Poulo)
Availability
Zone A
Availability
AZvoanilaebBility
Zone A
Availability
Zone B
APAC Region Singapore
Availability
Zone B
Availability
Zone A
Availability
Zone B
US West Region -2
(Oregon)
APAC Region Tokyo
Availability
Zone A
Availability
Zone B
APAC Region
Australia
Availability
Zone A
Availability
Zone B
EU -IRELAND
*New customers can access three EC2 Availability Zones in US East
(Northern Virginia) and two in US West (Northern California)
US East Region (N.VA)
Availability Availability
Zone A Zone B
Availability
Zone D
Availability
Zone C
Availability
Zone A
Availability
Zone B
Availability
Zone C
Availability
Zone C
US Govt. Cloud
Availability Zone B Availability Zone A
EU-Frankfurt
Availability Zone B Availability Zone A
China (Beijing) Region
Availability Zone A
Availability
Zone E
Availability
Zone C
Slide 25 www.edureka.co/cloudcomputing
http://aws.amazon.com/about-aws/globalinfrastructure/

26. Amazon Cloud Characteristics
Slide 26 www.edureka.co/cloudcomputing
 Availability & Reliability
 Scalability & Elasticity
 Performance
 Flexible (Numerous options of Programming, APIs , Access)
 Secure

27. Access AWS
AWS
Management
Console
AWS
Web service
APIs
AWS CLI AWS SDKs
Slide 27 www.edureka.co/cloudcomputing

28. Slide 63 www.edureka.co/cloudcomputing
Why AWS
http://aws.amazon.com/resources/gartner-mq-2014-learn-more/

29. EC2 Highlights
Pre-built
AMIs
Flexible
Elastic
Reliable
Secure
In-expensiveControlled
Slide 29
http://www.edureka.co/cloudcom

30. EBS Features
EBS
Features
1 GB – 16 TB
Size Volume
Persistent
Storage
High
Performance
and
Durability
Automatic
Replication in
same Zone
for HA
Raw
Unformatted
Volume
Slide 30
http://www.edureka.co/cloudcom

31. EBS Definitions
Slide 31
http://www.edureka.co/cloudcom
EBS:
» EBS is a distributed, replicated block data store that is optimized for consistency and low latency read and write
access from EC2 instances
 EBSVolume:
» A volume can only be attached to one instance at a time, but many volumes can be attached to a single
instance
 EBSSnapshot:
» Snapshots can also be used to instantiate multiple new volumes, expand the size of a volume or move volumes
across Availability Zones. Snapshots can be shared using AWS Management Console or using API calls
 Amazon EBS is particularly well-suited for use as the primary storage for a file system, database, or for any
applications that require fine granular updates and access to raw, unformatted, block-level storage

32. EBS Volume Life Cycle
Call
create
volume
from
1 GB–
16TB
Slide 32
http://www.edureka.co/cloudcom

33. S3 Definitions
Slide 33
http://www.edureka.co/cloudcom
 Bucket – Collection (container) of objects. Up to 100 per account. Names up to 255 characters long
 Object – Objects are the fundamental entities stored in Amazon S3. Objects consist of object data and metadata. They are
Individually addressable data item. Any number per bucket and per account. An object is uniquely identified within a
bucket by a key (name) and a version ID
 Key – A key is the unique identifier for an object within a bucket. Every object in a bucket has exactly one key
 ACL – Access Control List

34. Amazon S3 Namespace
Amazon S3
Bucket Bucket
Object Object Object Object
Bucket
Object ObjectSlide 34
http://www.edureka.co/cloudcom

35. Amazon S3 Namespace (Contd.)
Amazon S3
My-Images Cloud.bucket.com
Friends.jpg 2011/Bday.jpg AWS.jpg S3.jpg
Test.mysite.com
Install.doc Snap/Kid.jpg
Slide 35
http://www.edureka.co/cloudcom

36. Server Side Encryption
Slide 36
http://www.edureka.co/cloudcom

37. Three Services Better Together

38. VPC Architecture Scenarios
3. VPC with Public and Private Subnets and Hardware VPN Access
Conditions Target
10.0.0.0/16 local
0.0.0.0/0 igw-id
Conditions Target
10.0.0.0/16 local
0.0.0.0/0 vgw-id
VPN Connection
Slide 38
http://www.edureka.co/cloudcom
Custom Route Table
Main Route Table

39. AWS IAM Functionality
Slide 39
http://www.edureka.co/cloudcom

40. Integration Option 2 : Identity Federation
Slide 29 http://www.edureka.co/cloudcom

41. www.edureka.co/cloud
Integration Option 2 : Identity Federation (Contd.)
Slide 30 http:// computing

42. Database In AWS Cloud
Slide 42
http://www.edureka.co/cloudcom

43. RDS Highlights
Slide 43
http://www.edureka.co/cloudcom

44. Why RDS?
Slide 44
http://www.edureka.co/cloudcom
 Supports Popular DB like MySQL, Oracle, MS SQL & Now PostgreSQL [Now Aurora]
 Rapid DB Instance Creation
 backups, software patching, automatic failure detection, and recovery
 Scaling
 HA & Durability
 Automated DB Software Upgrade
 Monitoring & Metrics
 Security
 Cheap
http://aws.amazon.com/rds/

45. Security Best Practices (Contd.)
Example: Build security Into Every Layer
HA Architecture
Security Characteristics:






Route 53 (highly scalable DNS)
Autoscaling Groups
Security Groups
ELB Security Group
OS Firewalls (on Instances)
RDS
»
»
»
»
DB Security Groups
backup window
snapshots
multi-AZ
 CloudFront
» Private Distribution
» Pre-signed URLs
 S3 Bucket Policies
» Private bucket
Slide 42 https://s3.amazonaws.com/aws001/basecamp/BaseCamp_Application_Security_Best_Practices.pdhf ttp://www.edureka.co/cloudcomputing

46. Questions
Slide 57 http://www.edureka.co/cloudcomputing

47. Verifiable Certificate
Experienced Instructor
Live Online Class
Survey Feedback
24x7 Support
In-class Questions
Class Recording in LMS
Module Wise Assessment
Project Work
Android & iOS App
Slide 47 www.edureka.co/cloudcomputing
How it Works?

48. AWS Architecture and Design
Slide 48 www.edureka.co/cloudcomputing
 Module 6
» Identity and Access Management
Techniques (IAM) & IAM Techniques and
Amazon Managed Relational Database (RDS)
 Module 7
» Multiple AWS Services and Managing the
Resources' Lifecycle
 Module 8
» AWS Architecture and Design
 Module 9
» Migrating to Cloud & AWS Case Study
 Module 10
» Project & AWS Certification Discussion
 Module 1
» Introduction to Cloud Computing & AWS
 Module 2
» Amazon EC2 and Amazon EBS
 Module 3
» Amazon Storage & Monitoring Services :
S3, RRS & CloudWatch
 Module 4
» 'Scaling' and 'Load Distribution' in AWS
 Module 5
» Amazon VPC & Route 53

49. Survey
Your feedback is important to us, be it a compliment, a suggestion or a complaint. It helps us to make
the course better!
Please spare few minutes to take the survey after the webinar.
Slide 58 http://www.edureka.co/cloudcomputing

50. Slide 59 Course Url