Join AWS and BlueMetal, a technology architecture firm and a member of the Amazon Partner Network, for this live webinar where we will discuss modernizing your applications when moving your data center to the AWS Cloud. Microsoft has announced that July 30, 2015, is the end of support for Windows Server 2003. This will affect customers since there will be no patches or security updates, putting applications and business at risk. Attend this webinar to learn about considerations and best practices for creating a composed solution when moving off of Windows Server 2003 and migrating your data center and applications to the cloud.

1. Migrating & Modernizing your applications when moving your data center to the
AWS Cloud
Windows 2003 Server end of support (EOS) as a motivator
Datacenter as a Service

2. Modern technology, craftsman quality.
We’re an interactive design and technology
architecture firm matching the most
experienced consultants in the industry to
the most challenging business and technical
problems facing our clients.
BOSTON | NEW YORK | CHICAGO
44 Pleasant Street, Suite 200
Watertown, MA 02472
www.bluemetal.com
Blog.bluemetal.com
@bluemetalinc
The Modern Application Company ™ Giorgio Pironi
Managing Architect - Cloud & Services
www.bluemetal.com
giorgio.pironi@bluemetal.com
@giorgiopironi
Introductions

3. Our Services

4. Agenda
1. What does Windows Server 2003 end of support (EOS) mean?
2. Windows Server 2003 options – How to move forward?
3. What is a “Modern Application”?
4. What is a “Modern Infrastructure”?
5. AWS as the Modern Infrastructure enabler
6. Modern Application demands Modern Infrastructure
7. Best Practices & patterns for migrating/modernization
8. Taking your data center to cloud as a service
4

5. Windows Server 2003 EOS - Why we are here?
• Windows Server 2003 approaching end of support (EOS) on July 14, 2015
• No more patches and updates without a custom support agreement
• Custom support agreement will be expensive
• No Security patches for OS & IIS
Days until Windows Server
2003 End of Support
Time is running out!!!
5

6. Windows Server 2003 EOS – The impact
Months Ago Today July 14, 2015 After July 14, 2015
6

7. Windows Server 2003 EOS – The Risks
• Applications at Risk
• Running applications on unsupported WS2003 machines
• Security and Regulatory Compliance Risks
• Is your application required to run on a supported platform for compliance?
• Due to regulations like: HIPAA, PCI, SOX, & Dodd-Frank, regulated industries must run on supported platforms
• Business Continuity/Risk
• Will your users not be able to use a product/service because of a unpatched security hole or
perhaps application updates run into issues related to Windows 2003
• Supportability
• Loss of Microsoft support
• Loss of third-party vendor support
• What impact does this have on your application
7

8. What are the challenges in waiting to act?
• How do you mitigate your business risk?
• Can you afford custom support?
• How do you remain compliant (if applicable)?
• How do you continue releasing product updates?
• How do you maintain the security of the system for your users?
8

9. Seize the opportunity in doing something
• Maintain Business Continuity
• Use migration & modernization as a means to deliver a compelling and
competitive product that
1. Grows your business
2. Provides increased competitive advantage
3. Is cost effective
4. Delivers a compelling user-centric experience
9

10. Windows 2003 EOS Options
Migrate
SaaS platform
Service model
3rd party product
Retire
Create a Retirement Plan
Apr 24, 2003 – July 14, 2015
Do Nothing
Take the risk
Modern Application (User Centric)
Modern UX (Responsive)
Modern Security (Two factor)
Modern Data (Hadoop/Analytics)
Modern Infrastructure (Cloud)
Modernize
Replace
Stay in place
Manual update
Lift & Shift to Cloud
Hybrid
10

11. Windows Server 2003 EOS – Options
Option Notes Effort Benefits
1. Do Nothing • Maintain legacy systems; accept risk
• Evaluate custom support agreement with MSFT
Low Low effort
2. Retire • Sunset legacy applications Medium Simplification
3. Replace • Transition to SaaS, service model, or third-party
product
Medium - High Leverage better
capabilities and
operations
4. Migrate • Upgrade OS
• “Lift and ship” to cloud, then upgrade applications
via manual and automated processes
Medium Predictable and
manageable
5. Modernize Modernize the application using updated UX, security,
data, and virtualization approaches
High Competitive
advantage, business
growth, at lower cost
11

12. Next – Modern Application & Modernization
“The Modern Application”
12

13. What is a “Modern Application”?
The “Modern Application” is a set of
principles for best practices and design
patterns in developing applications that
are user-centric.
Modern applications are:
• Responsive
• Secure
• Intelligent
• Dynamic
• Data/Information driven
• Available
• Performant
• API driven
13

14. Modern Application Behavioral Aspects
Modern applications:
• Provide a great experience
• Architecturally sound & flexible
• Great Design
• Deliver Productivity
• Act intelligently
• Adaptable to environment
• Interact with the world around them, like
infrastructure
• Possess agility
Experiences
Architecture Design
14

15. The Modern Application Directive
“A philosophy of best practices and
design patterns to meet today’s
business drivers”
15

16. The Pillars (Framework) of the Modern Application
• Modern Security (Two-factor auth, Fingerprint)
• Modern UX (Responsive, Multi-device, Voice)
• Modern Data (Relational, NoSQL, Storage, DW)
• Modern Intelligence (Data & Predictive Analytics)
• Modern Access (Anywhere, anytime, any device)
• Modern Performance (Speed, Agility, Scalability)
• Modern API (Interoperability, expose & consume)
• Modern Workflow (user centric, design &
process flow)
• Modern Operations (predictable, cost-effective)
16

17. Modernizing your application
Modern Security
Where a “security first” mentality permeates
throughout the entire application design &
implementation. Security follows the user, is
consistent, and is delivered by infrastructure
that is protected.
 Two-factor authentication
 Fingerprint
 Voice Authorization
 Encrypt data at rest / in transit
Dynamic, adaptive to device, context aware,
simplification of information. Modern UX is a
paradigm of the way a user would interact
with an application.
 Responsive
 Multi-Device
 Context aware
 Voice
Modern UX Modern Data
The promotion of data storage repositories
that are optimized to the structure of the
data , but where data can still be viewed and
communicated in a uniformed manner.
 Relational
 NoSQL
 Object Store
 Data Warehouse
17

18. Modernizing your application
Modern Intelligence
Making use of data and the current context
that surrounds us to be predictive,
suggestive, and actionable. Information
presented in a coherent structure, easily
understandable, in a given user context.
 Data Analytics
 Predictive Analytics
 Suggestive Analytics
 Actionable
Architecting your application to be highly
accessible with a great user experience.
 Anywhere
 Anytime
 Any Device
Modern Access Modern Performance
Users expect responsive results. Applications
must be designed to provide information
context on time, or adapt appropriate
communication paradigms when processes
will take long time.
 Speed
 Agility
 Scalability
 Elasticity
18

19. Modernizing your application
Modern API
Connectivity delivers functionality that
follows the user.
 Interoperability
 Expose & Consume
One application instead of many, designed
to follow all of the activity surrounding a
user process.
 User-centric
 Design Flow
 Process Flow
 Adaptable
Modern Workflow Modern Operations
High levels of interactivity with context to
provide feedback to the end user regarding
their environment .
 Predictable
 Feedback / Dashboard
 Status
 Activity Progress
19

20. What is Modern Infrastructure?
“The Modern Infrastructure”
enables
“The Modern Application”
20

21. The Pillars (Framework) of Modern Infrastructure
21
• Security (Processes, methods, procedures)
• Availability (MAA, Cross region DR)
• Scalability (Limited by what you can afford)
• Reliability (eleven 9’s, etc.)
• Elasticity (Grow & contract)
• Global Presence (all around the world)
• Performance (Highly performant)
• Infrastructure API (provision and control your
infrastructure)
• Management (Deployment, operations)

22. Modern Application “meets” modern Infrastructure
“AWS”
is the
“The Modern Infrastructure”
that powers
“The Modern Application”
22

23. Why AWS for Modern Infrastructure?
• #1 reseller of Windows Server & SQL Server
• Maturity
• Ecosystem – Whitepapers, webinars, target first
• Reliability & Scalability
• Global Footprint
• Automation
• Large number of services
• Leader in the introduction of new innovative services
23

24. Software Defined Data Center (SDDC)
“Everything now is a programmable
resource. There are no physical things
anymore……..” – Dr.Werner Vogels (Re:Invent 2012)
24

25. Modern API – Infrastructure as code / software
+ API = Programmable
Platform
25

26. Modern Access
The scale that you want
• Broad range of different combinations of CPU,
memory, disk, and networking
• AWS global Infrastructure
– 9 Regions
– 25Availability Zones
– Continuous Expansion
26

27. Modern Data
RDS is a managed relational database service that is simple to deploy,
easy to scale, reliable, and cost-effective
Managed Service
Amazon Relational Database Service (RDS)
Choice of Database Engine
Managed Service
Easy to Scale
High Performance
High Availability
Amazon RDS
DynamoDB
Amazon NoSQL DB
27

28. Modern Performance
DynamoDB
Optimized
Instances
Redis
ElastiCache
Memcached for
performance,
scalability, and cost
savings
Amazon DynamoDB for
unbounded data
with heavy write load.
Redis for fast, complex
caching and message
passing
Instances to handle any
load – high memory, GPU
based,
Auto Scale
Auto scale to
handle any load
Memcached
28

29. Modern Operations
• System Center +AWS Management Pack
• Amazon CloudWatch
• AWS CloudFormation
• AWS Identity & Access Management
• AWS CloudTrail
• AWS Trusted Advisor
29

30. Modern Security - Built for Enterprise Security
Standards
Certifications
SOC 1 Type 2 (formerly
SAS-70)
ISO 27001
PCI DSS for EC2, S3,
EBS, VPC, RDS, ELB, IAM
FISMAmoderate compliant
controls
HIPAA& ITAR compliant
architecture
Physical Security
Data centers in nondescript
facilities
Physical access strictly
controlled
Must pass two-factor
authentication at least
twice for floor access
Physical access logged
and audited
HW, SW, Network
Systematic change
management
Phased updates
deployment
Safe storage
decommission
Automated monitoring and
self-audit
Advanced network
protection
Note: See http://aws.30 amazon.com/security/ for latest information

31. Modern Security – AWS Advantage
Cloud Security Advantages:
• Dedicated Security Team
• Greater Investment in Security Infrastructure
• Greater Security Certifications that are met
• Real-Time Detection of System Tampering
Quotes from Forrester:
• “Cloud security will expand to be much more centralized and automated. If you’re resisting the
cloud because of security concerns, you’re running out of excuses. The leading public cloud
providers have made strong gains in security and compliance, and there are few workloads
completely off-limits for public cloud anymore.”
• “…the larger Cloud providers tend to have a better grasp of threats, because as Forrester's
Wang says: "These people deal with security issues at more complex levels than your own IT
team sees on a daily basis".
31

32. AWS Services for Migration/Modernization
Modern Compute & Storage
Amazon EC2 Elastic Load
Balancing Amazon VPC
Modern Data
DynamoDB Amazon RDS MySQL DB
instance
Oracle DB
instance
MS SQL
instance
PostgreSQL
instance
Modern Performance
ElastiCache Redis Memcached
Modern Intelligence
Amazon Redshift
Modern Security
AWS CloudTrail
IAM
encrypted
data
MFA token
Amazon S3
Auto Scaling
Amazon
CloudSearch
Amazon EMR
Amazon
Kinesis
optimized
instance
Amazon EBS
32

33. Tools you already are familiar with
AWS Tools for Visual Studio AWS Tools for Windows PowerShell
33

34. Modern Application “meets” Modern Infrastructure
“The Modern Application”
demands
“The Modern Infrastructure”
34

35. Modern App / Modern Infra working well
35

36. Modern App / Modern Infra not working well
36

37. Modern App / Modern Infra not working well
37

38. Modern App / Modern Infra working well
38

39. Modern Application “meets” modern Infrastructure
“The Modern Application”
works with/is connected
“The Modern Infrastructure”
39

40. What we want – We want this
40

41. Best Practices / Patterns to move past Win 2003?
“Best practices and patterns for
creating a composed solution
when moving off of Windows
Server 2003”
41

42. Windows 2003 EOS Options
Migrate
SaaS platform
Service model
3rd party product
Retire
Create a Retirement Plan
Apr 24, 2003 – July 14, 2015
Do Nothing
Take the risk
Modern Application (User-centric)
Modern UX (Responsive)
Modern Security (Two factor)
Modern Data (Hadoop/Analytics)
Modern Infrastructure (Cloud)
Modernize
Replace
Stay in place
Manual update
Lift & Shift to Cloud
Hybrid
42

43. Windows EOS Actions (Patterns)
Do Nothing
Retire
Replace
Migrate
Modernize
Hybrid
43

44. Enterprise Windows EOS Solution Methodology
Discover,
Inventory, &
Categorize
Develop
Common
Roadmap for
EOS Action
Determine
best EOS
action for each
item in
inventory
Prioritize and
rank inventory
for migration
actions
Perform the
migration
44

45. Enterprise Windows EOS Solution Methodology
Discover,
Inventory, &
Categorize
Catalog your Software and Workloads
Tools to help you:
Microsoft Assessment and Planning (MAP) Toolkit
AppZero
Cloudamize
Racemi
CloudVelox
many more…
45

46. Enterprise Windows EOS Solution Methodology
Discover,
Inventory, &
Categorize
Develop
Common
Roadmap for
EOS Action
Determine
best EOS
action for each
item in
inventory
Prioritize and
rank inventory
for migration
actions
Perform the
migration
46

47. Enterprise Windows EOS Solution Methodology
Develop
Common
Roadmap for
EOS Action
Do Nothing
Retire
Replace
Migrate
Modernize
Hybrid
47

48. Enterprise Windows EOS Solution Methodology
Discover,
Inventory, &
Categorize
Develop
Common
Roadmap for
EOS Action
Determine
best EOS
action for each
item in
inventory
Prioritize and
rank inventory
for migration
actions
Perform the
migration
48

49. Enterprise Windows EOS Solution Methodology
Determine
best EOS
action for each
item in
inventory
Action Decision Tree
Action Eligibility Matrix
Action Scorecard
Final Action Selection
49

50. Enterprise Windows EOS Solution Methodology
Start
Retire
Add Retire option to
Yes Eligibility Matrix
Replace
No
Yes
Migrate
Add Migrate option to
Yes Eligibility Matrix
No
Modernize
No
Yes
End
Add Replace option to
Eligibility Matrix
Add Modernize option to
Eligibility Matrix
Windows Server 2003
Action Decision Tree
50

51. Enterprise Windows EOS Solution Methodology
1 2 3 4 Solution
Candidate
Business
Business checklist to
determine if migration
path meets business
requirements
Legal/Global
Legal/Global checklist
to determine if
migration path meets
legal & global criteria
Security/Privacy
Security / Privacy
checklist to determine
if migration option
passes all security &
privacy criteria
Architecture/Platform
Compliance
Architecture Platform Compliance
checklist to determine if public cloud
passes the following checklists:
Architecture, Hardware, Platform,
Application
Migration
Pipeline
Checklist
51

52. Enterprise Windows EOS Solution Methodology
ID Application Do Nothing Retire Replace Migrate Modernize Hybrid
0001 Shipping App Yes Yes No No No No
0002 CRM No No Yes Yes Yes No
0003 Tax Calculator No No No Yes Yes Yes
0004 Search Engine No No Yes Yes Yes Yes
0005 Contact
Management
No Yes Yes No No No
0006 Device Driver No Yes No No No No
0007 E-Commerce
App
No No No Yes Yes Yes
Action Eligibility Matrix
52

53. Enterprise Windows EOS Solution Methodology
Scorecard Biz Growth Competitive Affordable Innovative Criteria X Criteria Y
0001-ShippingApp-Dothing
0001-ShippingApp-Retire
0001-ShippingApp-……
0002-CRM-Replace
0002-CRM-MIgrate
0002-CRM-……
Etc.
Action Scorecard
53

54. Enterprise Windows EOS Solution Methodology
ID Application Migration Action Pattern
0001 Shipping App Do Nothing
0002 CRM Replace
0003 Tax Calculator Migrate
0004 Search Engine Hybrid
0005 Contact Management Replace
0006 Device Driver Retire
0007 E-Commerce App Modernize
Determine
best EOS
action for each
item in
inventory
Action Decision Tree
Action Eligibility Matrix
Action Scorecard
Final Action Selection
54

55. Enterprise Windows EOS Solution Methodology
Discover,
Inventory, &
Categorize
Develop
Common
Roadmap for
EOS Action
Determine
best EOS
action for each
item in
inventory
Prioritize and
rank inventory
for migration
actions
Perform the
migration
55

56. Enterprise Windows EOS Solution Methodology
ID Application Migration Action Pattern Rank
0001 Shipping App Do Nothing 1
0002 CRM Replace 4
0003 Tax Calculator Migrate 2
0004 Search Engine Hybrid 5
0005 Contact Management Replace 6
0006 Device Driver Retire 7
0007 E-Commerce App Modernize 3
Prioritize and
rank inventory
for migration
actions
56

57. Enterprise Windows EOS Solution Methodology
Discover,
Inventory, &
Categorize
Develop
Common
Roadmap for
EOS Action
Determine
best EOS
action for each
item in
inventory
Prioritize and
rank inventory
for migration
actions
Perform the
migration
57

58. Enterprise Windows EOS Solution Methodology - 5
Perform the
migration
JUST DO IT!!
Implement the plan
58

59. Windows EOS Action Patterns
Do Nothing
Retire
Replace
Migrate
Modernize
Hybrid
Many Patterns Many Patterns
59

60. Do Nothing Pattern
1. Identify when to revisit this decision
2. Document the factors that led to this decision e.g.
• Platform Incompatibility (Itanium chip)
• Financial Reasons
• Retirement of product at a later date
• Many more possibilities….
60

61. Retirement Pattern
Develop a retirement roadmap for the asset containing:
• Document the factors that led to this decision
• Develop timeline
• Develop the process & procedures
• Determine how users of the system will be informed and possibly redirected
• Etc.
61

62. Replace Pattern
1. Document functionality compatibility matrix
2. Document the data model
3. Evaluate products that are functionally compatible and can support the data model
4. Make selection of product for replacement
5. Configure product and migrate data
6. Develop a migration plan for users
62

63. Migration Patterns – Multiple Destinations
In-place Migrate OS
Migrate
Application
& Data
Test
In-place, lift
& shift to
cloud
Migrate OS
Migrate
Application
& Data
Test
Lift & Shift
to Cloud
Lift & shift to
cloud & then
migrate OS
Lift & Shift
to Cloud
Migrate OS
Migrate
Application
& Data
Test
63

64. Modernization Patterns
In-place Migrate First
Implement
Modernization
Features
Test
In-place, lift
& shift to
cloud
In-place
Migrate
Implement
Modernization
Features
Test
Lift & Shift to
Cloud
Lift & shift to
cloud & then
migrate OS
Lift & Shift to
Cloud
Migrate
Implement
Modernization
Features
Test
64

65. Hybrid Patterns
Lift & shift to
cloud &
Keep OS
Lift & Shift to
Cloud
Test
Continue with
Win2003 &
AWS *
Migrate to
Modernize
(Cloud Dest.)
Implement a
Migration
Pattern
Leverage AWS
Perform
Application
modernization
Test
* Contact AWS for more details
65

66. Tying it all together
“Datacenter to Cloud”
66

67. Getting From A to B
EBS
RDS Redshift ElastiCache
AWS Cloud
EC2 Elastic Load
Balancing
67

68. AWS CloudFormation
• Use AWS CloudFormation to create, provision & manage AWS resources
in a uniformed manner
• Template-Derived Infrastructure Design
• Infrastructure becomes code
• Source control managed – can track changes
• You have governance and auditability, via SCC and AWS CloudTrail
• Easy to set up and tear down
• AWS CloudFormation is for macro deployment of your data center
68

69. AWS CloudFormation Template – JSON Text File
CloudFormation
Software Defined Datacenter (SDDC)
Your datacenter as code
Actionable documentation
that defines & provisions your
infrastructure
Dynamic and user-driven
templates
Version Control & share
templates with others
No Extra Charge
Declarative & Flexible
Repeatable process
69

70. AWS CloudFormation – How it works
AWS CLOUDFORMATION
TEMPLATE
Model Click Done
70

71. Sample CloudFormation Template
Sample Templates
http://docs.aws.amazon.com/AWSCloudFormati
on/latest/UserGuide/cfn-sample-templates.html
Many more no the internet:
71

72. AWS Cloud Design Patterns
AWS Cloud Design pattern (a.k.a. CDP) is a general repeatable solution
to a commonly occurring problem in cloud architecture.
Examples:
Availability
Multi-Server Multi-
Datacenter
Floating IP
Deep Health Check
Scaling Scale
Out Clone
Server NFS
Sharding NFS
Replica State
Sharing
URL Rewriting Rewrite
Proxy Cache Proxy
Scheduled Scale Out
Batch Processing
Queuing Chain Priority
Queue
Job Observer Scheduled
Auto Scaling
Networking
On-demand NAT
Backnet Functional
Firewall
Operational Firewall
Multi Load Balancer
WAF Proxy CloudHub
Cloud Design Pattern wiki
http://en.clouddesignpattern.org
Example
Server
redundancy
pattern
72

73. Sample 3 Tier migration to AWS
DynamoDB
CloudWatch
73

74. Sample 3 Tier migration/modernize to AWS
Amazon SNS
Amazon SQS
AWS Services
CloudWatch
email notification
Amazon Redshift
Amazon
Kinesis
74

75. Global Infrastructure for the Modern Application
75

76. Datacenter as a Service – What does this mean?
Datacenter as a service (DCaaS) is the provision of offsite physical data
center facilities and infrastructure to clients. Clients rent or lease access to
the provider’s data center, using the servers, networking, storage and
other computing resources owned by the DCaaS provider.
You pay for only what you use
You operate and manage your applications
Cloud vendor provides and manages the infrastructure
76

77. The Management Console
77

78. Moving Forward – The Path Ahead
• With regards to Windows 2003 end of support, you are on a timeline,
and the best time to take action is today.
• Modern Application – Your users deserve more and your business will
profit from it. Look at modernization as an opportunity to meet core
business goals of business agility & business growth at lower costs.
• Modern Infrastructure – Do you continue to invest in your data center,
or do you leverage modern infrastructure that can help modernize (and
monetize) your application?
• AWS is a winner!! Your application is only as good as the infrastructure
to support and interact with. Re:Invent!!!
78

79. BOSTON | NEW YORK | CHICAGO
44 Pleasant Street, Suite 200
Watertown, MA 02472
www.bluemetal.com
Blog.bluemetal.com
@bluemetalinc
Giorgio Pironi
Managing Architect
giorgio.pironi@bluemetal.com
Thank You!