The document outlines AWS cloud deployment models, including hybrid and all-on-cloud options, highlighting how to choose between them based on application needs, compliance, and connectivity. It provides examples of scenarios for each model and emphasizes the need for secure network connectivity for hybrid models. Additionally, it discusses considerations such as cost, data privacy, and AWS service availability in making deployment decisions.

1. AWS Fundamentals-
Cloud Deployment
Models
ANANATHARAMU MP

2. This website and its content is copyright of foxydev.blogspot.com © anantharamu 2022. All rights
reserved.
Any redistribution or reproduction of part or all of the contents in any form is prohibited other than
the following:
● you may print or download to a local hard disk extracts for your personal and non-commercial
use only
● you may copy the content to individual third parties for their personal use, but only if you
acknowledge the website as the source of the material
You may not, except with our express written permission, distribute or commercially exploit the
content. Nor may you transmit it or store it in any other website or other form of electronic retrieval
system.
Copyright NOTICE - https://foxydev.blogspot.com

3. Overview
Agenda
● Cloud Deployment Models
● How to choose
● AWS TIPS

4. AWS deployment Models
Hybrid
● Some applications on cloud and some
in local data center
● Secure Network connectivity is setup
between local data center and AWS.
● Ex: Application in process of migrating
to AWS
Private Cloud
● AWS services run on local data
center
● Many features may NOT be
available.
● Ex: Strict Data privacy and
compliance requires data &
processes to be in local.
ALL on Cloud
● Application fully runs on AWS
● AWS services fully suite the
application needs
● Ex: Startup product or POC or
product built from scratch
● Ex: Lift and Shift of application to
EC2

5. AWS TIPS
Hybrid - Choose?
● AWS compliance/SLA does not meet your
data compliance/SLA requirements.
● Some parts of applications cannot be
moved to AWS due to legacy hardware.
● AWS costs are higher than on premise
solution.
● Service of your application NOT available
in AWS
● AWS connectivity from local is acceptable.
● Huge data which cannot be sent to AWS or
costly to have it in AWS
Private Cloud - Choose?
● AWS compliance/SLA does not meet
your data compliance/SLA
requirements.
● Privacy of applications and data is
highly strict.
● AWS is not operational in your region.
● AWS connectivity is slow or
unavailable over the network.
● Huge data which cannot be sent to
AWS or costly to have it in AWS
ALL on Cloud - Choose?
● Application is built from
scratch.
● SLA agreements are met.
● Application needs and services
are satisfied by AWS.
● Cost is justified.
● AWS compliance meets your data
compliance requirements.

6. Support Us
PayPal:
https://paypal.me/aramu80?country.x=IN&locale.x=en_GB
UPI: anantha.ramu80@okicici

7. Thank you