This document discusses hybrid IT strategies for connecting on-premises infrastructure to AWS. It defines key terms like on-premises IT, cloud architecture, and hybrid IT. It then outlines several common enterprise strategies for adopting AWS, such as using AWS for development/test environments, building new apps for the cloud, enhancing existing on-prem apps with cloud services, and migrating apps to AWS. The document also discusses technologies like AWS Direct Connect, Storage Gateway, and disaster recovery options. It emphasizes the importance of cost, workloads, compliance, latency, and user experience when considering a hybrid IT approach.
RightScale Webinar: Hybrid-IT: Connecting Your On-Premises Infrastructure With AWS
1. Ask
the
Architect
Connect
Your
On-‐Premises
Infrastructure
to
AWS
Brian
Adler,
Sr.
Services
Architect,
RightScale
Miles
Ward,
Sr.
Manager,
SoluBons
Architecture,
AWS
August
27,
2013
2. IntroducBons
Q&A
• Michael
Curry,
Account
Execu6ve,
RightScale
• Bryan
Cox,
Sales
Development
Representa6ve
Brian
Adler
Senior
Services
Architect
RightScale
Miles
Ward
Senior
Manager
SoluBons
Architecture
AWS
3. Agenda
• DefiniBons
and
terminology
• Enterprise
strategies
for
hybrid
IT
• Technologies
for
implemenBng
hybrid
paOerns
with
AWS
• Key
consideraBons
for
hybrid
IT
• ImplemenBng
hybrid
IT
with
RightScale
and
AWS
• Use
cases
• Q&A
4. Hybrid
IT
Trends
Source: RightScale State of the Cloud 2013
Currently running apps in
public cloud
Currently running apps in
on-premises environments
Currently running apps in
hybrid environments
Current Cloud Usage
By organizations with a Hybrid IT strategy
Enterprises want multi-cloud/hybrid IT
Hybrid IT
47%
Multi-private
15%
Multi-public
15%
5. DefiniBons
and
Terminology
On-‐Premises
IT
A
collecBon
of
compute,
storage,
and
network
resources
for
a
single
tenant
that
are
accessed
programmaBcally
via
an
API
endpoint.
Cloud
Architecture
A
similar
set
of
resources
that
is
mulB-‐tenant
and
is
provided
by
a
cloud
vendor
with
access
via
an
API
endpoint.
Hybrid
IT
An
environment
that
spans
your
cloud
provider
as
well
as
one
or
more
on-‐premises
IT
environments.
Mul6-‐Cloud
An
environment
that
spans
two
or
more
separate
cloud
providers
or
regions
6. The
Business
Case
for
Moving
to
the
Cloud
IT
Needs
The
AWS
+
RightScale
SoluBon
The
ability
to
scale
your
project
porYolio
without
the
need
to
scale
headcount.
• Professional
services
to
design
and
implement.
• Provision
predictable
and
repeatable
AWS
and
on-‐
premises
resources.
• Ensure
compliance
on
all
IT
resources.
Ensuring
24x7
upBme
in
a
global
marketplace.
• Advanced
monitoring
and
alerBng.
• Automated
remedial
acBons
across
all
your
IT
resources.
Maintain
visibility
and
control.
Advanced
reporBng
and
user
access
providing
visibility
and
control
across
all
your
IT
resources.
Consolidated
management
of
infrastructure
environments.
A
single
pane
of
glass
for
managing
both
all
your
IT
resources.
8. Enterprises
are
AdopBng
AWS
to
Achieve
the
Benefits
of
the
Cloud
Replace
CapEx with
OpEx
✔
Lower
Overall
Costs
✔
No More
Guessing
Capacity
✔
Agility /
Speed /
Innovation
✔ ✔
Shift Focus to
Differentiation
Go Global
in Minutes
✔
9. Many
Enterprises
Worry
that
These
Are
the
Only
Two
Choices
Build a new
‘private’
cloud.
Rip everything
out and move
to AWS.
#1 #2
10. The
Good
News
Is
that
the
Cloud
Isn’t
an
‘All
or
Nothing’
Choice
Corporate
Data
Centers
On-premises
Resources
Cloud
Resources
Integration
11. Active Directory
Network Configuration
Encryption
Back-up Appliances
Users & Access Rules (IAM)
Your Private Network (VPC)
Encryption (S3, RDS, HSM)
Back-ups (Storage Gateway)
AWS Direct
Connect
Your On-premise Apps Your Cloud Apps
IntegraBng
AWS
with
Your
ExisBng
On-‐premises
Infrastructure
Corporate
Data
Centers
12. The
AWS
Ecosystem
Allows
You
to
Use
Your
ExisBng
Management
Tools
Single Pane of Glass
On-
premises
Data
Centers
Consulting &
Management Partner
14. Strategy
1:
Cloud
for
Development
and
Test
Environments
SAP
Reduced
deployment time
from weeks to days
SAP
70% reduction in
operational costs
Oracle
Reduced dev &
test environment
costs
“Using cloud for Test
and Development
workloads is an easy
win. A lot of enterprises
are using AWS in this
way first.”
James Governor,
Founder
15. Strategy
2:
Build
New
Apps
for
the
Cloud
Faster to build
Facebook
app
Global
web sites
Mobile
streaming
Social
games
Consumer
apps
Genetic
sequencing
Marketing
campaigns
Less expensive to run
Distributed
architectures for high
availability
Easier to manage
Financial
record
archiving
17. Operational
applications
Export data to
AWS for analytics
processing
Oracle
databases
Automated back-
up to S3 with
Oracle RMAN
Strategy
3:
Use
Cloud
to
Make
ExisBng
On-‐Prem
Apps
BeOer
Retail
operational
applications
Data
synchronization &
back-up with AWS
storage gateway
18. Strategy
4:
New
Cloud
Apps
that
Integrate
Back
to
On-‐Prem
Systems
On-
premises
Data
Centers
Hybrid
App
AWS serves up
application content &
data
Integration back to
Samsung Data
Centers for financial
transactions
19. Strategy
5:
Migrate
ExisBng
Apps
to
the
Cloud
1/3 of servers
migrated to AWS
Saved 1-1.5 million
GBP
App
Your Data
Center
Migrated 500 web
properties in 5
months
New product web
sites in 2 days vs. 2
weeks
Migrated clinical trials
simulations platform
Simulations in 1.2hrs vs.
60hrs
64% reduction in costs
App
20. Strategy
6:
All-‐In
10,000s of EC2 instances in
multiple regions & zones
100s of middle tier services &
applications to support 33M+ global
members
At peak consumes 1/3 of US
Internet bandwidth
29. On-‐Premises
IT:
Key
ConsideraBons
Cost
• Sunk
investment
in
physical
infrastructure
–
try
to
maximize
the
uBlizaBon
of
this
CAPEX
Workload
and
Infrastructure
Interac6on
• ApplicaBons
have
different
resource
needs
• Choose
the
right
fit
for
your
applicaBon
and
your
infrastructure
Compliance
• Data
may
be
contained
on-‐premises
for
compliance
needs
or
requirements.
30. On-‐Premises
IT:
Key
ConsideraBons
Latency
• Consumers
of
the
on-‐premises
resources
are
generally
“closer”
to
the
environment,
which
reduces
latency
User
Experience
• Related
to
latency,
end
user
experience
is
enhanced
due
to
proximity
to
resources.
31. Management
ConsideraBons
Elevates:
• Configurations
• APIs
• Automation behaviors
• Access control
• Billing and governance
Users
and
systems
RightScale
–
MulB
Infrastructure
Resource
Management
Common
API
and
UI
AWS
On-‐Premises
OS
Hardware
Hypervisor
Services
APIs
APIs
32. Design Considerations
Location of Physical Hardware
• On-premises
• Availability considerations (power, cooling, networking, etc.)
• Hosted or Co-location facility
• Accessibility of hardware for additions and/or modification
• Latency to end users
• Security
33. Design
ConsideraBons
Availability and Redundancy Configuration
• Easiest configuration (single zone, single region, single API endpoint)
does not promote high availability
• High Availability of resources requires more complex configurations
35. Design
ConsideraBons
Intended
Workloads
and
Use
Cases
• Does
the
applicaBon
require
high
availability
or
is
it
tolerant
of
interrupBons
of
service?
• Does
the
applicaBon
require
(or
greatly
benefit
from)
specialized
hardware
or
network
configuraBons?
36. Use Cases
Cloudburs6ng
– An
applicaBon
deployment
model
in
which
an
applicaBon
runs
in
your
on-‐
premises
environment
and
bursts
to
a
cloud
provider
when
the
demand
for
compuBng
capacity
spikes.
– The
advantage
of
a
cloud
bursBng-‐enabled
deployment
is
that
an
organizaBon
only
pays
for
extra
compute
resources
when
they
are
needed.
– ConsideraBons:
• Control
–
public
Internet
traversal
may
be
required
• Latency
–
traversal
of
public
Internet
involves
the
Great
Unknown
• Cost
–
bandwidth
charges
for
public
Internet
traversal
• Complexity
–
numerous
opBons
exist
for
configuraBon
of
a
hybrid
secure
environment
37. Hybrid
IT
/
CloudbursBng
ON-PREMISES
CLOUD
LOAD BALANCERS
APP SERVERS
MASTER DATABASE
SLAVE DATABASE
OBJECT STORAGE
APP SERVERS
PUBLIC
INTERNET
CloudbursBng
38. Use
Cases
Disaster
Recovery
(DR)
• ProducBon
environment
in
on-‐premises
environment
• DR
environment
in
the
cloud
• Most
common
configuraBon
is
the
“Warm
DR”
scenario
• ReplicaBng
slave
in
the
cloud
• All
other
servers
in
non-‐operaBonal
state
40. Use
Cases
Self-‐Service
IT
Portal
(“IT
Vending
Machine”)
• Users
select
one
of
several
pre-‐configured
tech
stacks
• Isolated
Test/Dev
environments
41. User identity Your portal
On-Premises
end users
(web browser)
request a certain server type is
launched, and specify cloud location
Amazon Web Services
Deploy the chosen server
in a private or public cloud,
based on the
ServerTemplate
Service catalog of IaaS
applications
(ServerTemplates)
RightScale API
RightScale UI
service
designers(web
browser)
server
instance
Self
Service
IT
Portal
server
instance
is displayed as service
catalogue items within
review access logs, version
control and change logs, set
permissions
managers (web
browser)
billing data sent to
RightScale, for all cloud
usage
42. The
Business
Case
for
Moving
to
the
Cloud
IT
Needs
The
AWS
+
RightScale
SoluBon
The
ability
to
scale
your
project
porYolio
without
the
need
to
scale
headcount.
• Professional
services
to
design
and
implement.
• Provision
predictable
and
repeatable
AWS
and
on-‐
premises
resources.
• Ensure
compliance
on
all
IT
resources.
Ensuring
24x7
upBme
in
a
global
marketplace.
• Advanced
monitoring
and
alerBng.
• Automated
remedial
acBons
across
all
your
IT
resources.
Maintain
visibility
and
control.
Advanced
reporBng
and
user
access
providing
visibility
and
control
across
all
your
IT
resources.
Consolidated
management
of
infrastructure
environments.
A
single
pane
of
glass
for
managing
both
all
your
IT
resources.
43. Upcoming
“Ask
the
Architect”
Events
OperaBonalize
Your
AWS
Usage
Through
An
Enterprise
IT
Vending
Machine
Depth
of
content
Webinar
Digging Deep with Hybrid IT
AWS
re:Invent
In
Person
Online
9/17
Los
Angeles
9/10
NYC
10/1
Boston
10/15
Connecting your Datacenter to AWS
Designing and Implementing a Hybrid IT
Strategy and Solution
@
AWS
re:Invent
Las
Vegas,
NV
11/12
44. Q&A
• [I
am]
looking
for
reusable
templates,
best
pracBces,
and
approaches
to
perform
assessments
on
moving
workloads
to
the
cloud.
• RightScale
MulBCloud
Marketplace
– Repository
of
hundreds
of
publicly-‐available
ServerTemplates
• Onboarding/CloudSight/CloudRank
45. Q&A
• How
does
applicaBon
management
work
in
hybrid
clouds
where
the
private
cloud
workload
may
burst
to
AWS?
What
are
good
pracBces
for
app
data
sync
when
the
app
is
running
in
private
cloud
and
AWS?
• Stateless
applicaBon
servers
are
best-‐suited
to
cloudbursBng.
• If
data
synchronizaBon
is
required:
– Highly-‐available
shared
storage
(such
as
S3)
– High-‐performance
shared
filesystem
(like
GlusterFS
or
OpenAFS)
– Implement
a
low-‐latency
secure
link
(such
as
DirectConnect).
46. Q&A
• Is
there
a
published
checklist
somewhere
of
what
all
needs
to
be
validated
prior
to
deciding
to
move
a
system
(Exchange,
AD,
etc.)
to
the
cloud?
And
is
there
a
checklist
for
what
all
needs
to
take
place
when
you
actually
decide
to
move
something?
Do
you
have
any
whitepapers
to
show
how
customers
have
been
impacted
posiBvely
by
moving
on
prem
systems
to
cloud
that
most
customers
have
(i.e.
Exchange,
Email,
etc.)
How
have
they
saved
money,
provided
beOer
performance,
etc.),
and
made
their
lives
easier?
• This
is
a
common
quesBon
we
get
at
RightScale
-‐-‐
so
common
that
we
developed
a
consulBng
product
offering
around
for
this
exact
need
(CloudSight).
This
is
tough
to
answer
in
general
terms,
but
would
be
a
great
topic
for
our
in-‐person
events.
47. Q&A
• How
does
using
Amazon
VPC
impact
using
right
scale
middle
ware?
• Instances
need
to
route
out
to
RightScale
(no
inbound
access
required).
– NAT
– EIPs
– Route
through
on-‐premise
device
48. Q&A
• How
to
deal
with
long
distance
latency
issues
in
data
transfer?
• WAN
OpBmizaBon
Tools
– Compression/De-‐dup/TCP
OpBmizaBons,
etc.
49. Q&A
• If
we
save
data
to
the
AWS
cloud,
does
the
key
reside
on
the
cloud
or
with
us
exclusively?
(for
security
reasons,
we
would
prefer
not
to
have
the
key
reside
on
the
cloud
as
it
does
on
some
systems)
• TrendMicro,
a
RightScale
partner,
has
SecureCloud
which
allows
data
encrypBon
with
the
key
management
provided
by
Trend’s
SaaS
plaYorm
(not
in
AWS),
or
in
your
own
datacenter.