chris.c.wegmann@accenture.com

chris.scott@accenture.com

tomlasz@amazon.com

Accenture is a global management consulting, technology services,

and outsourcing company of more than 305,000 employees.

We help organizations

assess how to maximize their

performance and work with

them to achieve their vision

We develop and implement

technology solutions to improve

our clients’ productivity and efficiency

– and may run parts

of their business

Ultimately, we enable

our clients to become

HIGH-PERFORMANCE businesses and governments

We deliver through Accenture

Strategy, Accenture Digital,

Accenture Technology, and

Accenture Operations

Accenture implements AWS solutions for our clients, and we

also extensively use AWS for our internal solutions and client

offerings. Using AWS for more than 8 years, we have learned

how to effectively manage our cloud usage and develop

offerings that are agile and scale to meet our client demand.

2014

• Released ACP 3.0 with discovery capabilities for AWS

• Leveraging AWS to run ACP

• Moved more production Systems to AWS with higher levels of data calcification

• Accenture Analytics based on AWS

• Released our AWS Migration Framework

• Introduced our AWS COE

• Accenture.com moving to AWS

• Business Services built on AWS

2012• Release our first set

of AWS assets and production solutions

• Release of Accenture consumer goods and services on AWS

2010Starting moving dev and test environments to AWS

2008 Signed our first enterprise agreement with AWS

2006Started using Amazon EC2 and Amazon S3 in Accenture Lab

Client Solutions ShowcaseAccenture is delivering cross-industry,

enterprise solutions for big data,

analytics, and management in the

cloud, all run on AWS

Download brochure

Cloud-based architectures help

Discovery Networks International

plan for growth and changing

business needsAccenture implemented a scalable,

flexible, and cost-effective hosting

solution on Amazon Web Services for

DNI, without compromising on security

and availability.

Download brochure

Public credentials:Example projects:

Global electronics retailerWeb presence, cloud bursting, continuous development, search,

recommendations engine

Global pharmaceuticalArchitecture, application development/delivery

US gas/oilDivestiture program, AWS QA/performance review

Global insuranceArchitecture, management, Cloud CoE

US financialSharePoint deployment and management

South American miningSAP PoC / Nonproduction environment

We see many enterprises moving to cloud and AWS. To get started, we typically

see one of the below patterns:

Use cloud for test and development

environments to improve development agility

Develop new applications in the cloud. Building

for the cloud, utilizing IaaS+, takes best

advantage of cloud benefits

Use the cloud to improve current applications.

Cloud services can be used for cheap storage,

global content delivery, or failover

Build new cloud applications that

integrate back to applications on premises.

Examples include databases on premises

or thick clients

Move existing applications to cloud.

Migrate options include lift

and shift and refactoring the application

to use cloud services

Move wholesale to the cloud.

(Has not been historical enterprise use case, but

beginning to hear interest from a few of our clients.)

Examples include Netflix, Pinterest, etc.

Test/dev

New apps,

greenfield

Augment

Integrate

All-in

Migrate

Within the last 6 months, we have seen significant client demand for migrations.

Clients are seeking to migrate hundreds to thousands of workloads to AWS. We

are hearing the following form our clients:

Challenges / concerns

• Security

• Operational impacts

• Lack of resources

• Lack of cloud experience

• Pressures of shadow IT

• Older platforms

• Complexity of migrating systems and interfaces

Value drivers / benefits

• Agility

• Capital to operational expense

• Responsiveness to business needs

• Cost savings (in some scenarios)

Migrating to the cloud can take one of many paths

Discover,

assess (enterprise

architecture and

applications)

Lift and shift

(minimal

change)

Migration and

UAT testing Operate

Refactor

for AWS

Application

lift and shift

Move the app

infrastructure

Plan migration

and sequencing

Determine

migration path

Decommission

Do Not Move

Create cloud

strategy

Design, build AWS

environment

Move the

application

Determine

migration

process

Manually move

app and data

Third-party tools

AWS VM importRefactor

for AWS

Rebuild application

architecture

Vendor

S/PaaS

(if available)

Third-party migration tool

Manually move app and data

Determine

migration process

Replatform

(typically legacy

applications)

Recode app

components

Rearchitect

application

Recode

application

Architect AWS environment

and deploy app, migrate data

Signoff

Tuning Cutover

Org/ops

impact

analysis

Identify

ops changes

Change

management

plan

To support the massive internal and client demand to migrate existing workloads

to AWS. Accenture and AWS partnered together to develop a repeatable and

scalable method to migrate at scale.

The AWS Migration Framework assists organizations to:

• Build an AWS business case, strategy, TCO

• Rationalize the application portfolio

• Design a robust and scalable AWS architecture

• Define a migration approach and leverage automation tooling

• Integrate with and augment existing IT processes

• Manage cloud environments through support models such as Accenture Cloud Platform

Cloud

assessment,

planning

and pilots

AWS

enterprise

cloud

architecture

Cloud

migration

deployment

and testing

Cloud

management

Cloud

strategy

Unlocking the potential of the cloud requires a shared vision and roadmap for

business and IT

Defining the cloud strategy

Our cloud IT strategy services help you

shape the direction of IT, taking advantage

of cloud computing to maximize

shareholder and business value while

controlling IT spend.

Priorities and business case for

the cloud

Determine how cloud services can be

implemented and integrated to deliver

greater value to your business:

• Align IT with business strategy to

determine how cloud computing can

support growth

• Prioritize cloud investments and align to

business imperatives to drive bottom-line

impact

Agree on the capabilities

for the cloud

Confirm the new business and IT

capabilities, technologies, and strategies

you’ll need to take advantage of new

business opportunities created by the cloud.

Determine the best approach to realizing the

cloud-enabled future.

Pragmatic roadmap to the cloud

Generate alignment and buy-in to the pragmatic, actionable roadmap of change required to

take advantage of cloud computing. Sequence initiatives for the most efficient and effective

journey to the cloud.

Building the TCO model is an important step in the overall strategy and

determining what is the best fit for cloud computing.Understand current fully burdened cost per instance — both physical and virtual.

DON’T FORGET TO INCLUDE:

Physical space Electricity / fuel Blade chassis Compute

Storage Hardware cycles Backup Infrastructure licensing

• Infrastructure labor such as virtualization management

and physical data center management

• Cost of unused capacity

• Costs of physical data center security

• Match your on-premises amortization

with cloud reserved capacity

• Include cloud provider tiered pricing

• Don’t forget the cost–benefits of automation

• Cloud providers will typically provide

• Data center procurement

Assessment factory

Assessment framework

Client and Accenture project teams

Obtain access to environments

DiscoveryAssessment and

analysisInitial assessment

readyDeliver

assessment report

Questionnaire

CMDB / other DB

Existing data gathered

Selected applications

Application documentation

Deliver interim.assessment review

Review and sign-off

Feedback

Assessment tools

Kick-off

assessment

Defining the criteria to assess your applications is an important step in defining

your cloud candidates.

Security / compliance /

regulatory

• Data privacy (PII, PCI, etc.)

• Encryption

Availability

• SLA requirements

• Production / business criticality

• Vertical / horizontal scaling

• Network clustering

Database

• Size (DBs > 50 TB may be

an issue)

• Performance

• Clustering

Additional hardware

• Hardware acceleration

• Specialized hardware

• Hardware architecture

(generally Intel 64 best)

• USB devices / USB key

licensing

Integration

• Number of interfaces

• Data transfer requirements

• Printing / faxing requirements

Support

• Vendor support

• Vendor licensing

Design / platform

• Cloud provider technical limits

• Alignment with cloud strategy

• Operating system

• Programming language

• Application style (best for web)

Data / storage

Data retention period

Shared storage

Defining a practical cloud migration roadmap that incorporates sequencing constrained by

target environment feature availability, application dependencies, investment appetite, and

business calendar is a key outcome for this step of cloud migration activities.

Discovery Tools, Assessment

Framework and ToolsSource Apps

Migration with significant

remediation (x %)

• Apps requiring major remediation in order to be migrated

• Detailed assessment and thorough testing required to validate

• Re-platforming, re-architecting, or re-engineering of applications

• Combination of automated and manual remediation and deployment

Migration with minor

remediation (y %)

• Apps requiring minor code changes or remediation in order to be migrated

• OS changes, version upgrade, reference changes

• Limited configuration changes

• Automated and manual remediation; automated deployment

• Requires fit-for-purpose migration testing

Like for like migration

(z %)

• No code changes or remediation required

• Scripted/ automated

• Minimal or no impact to business

• Minimal testing required

• Roadmap marries together outcome

of assessment activities, discovery

and target cloud arch

• Includes business case updates

and realization plan

• Focus on early value, momentumCloud Migration

Roadmap

Pilot

Migrations

Updated

Business Case

PA

CK

AG

ED

/ C

OT

S

CU

ST

OM

CL

OU

D M

IGR

AT

ION

CO

MP

LE

XIT

Y &

EF

FO

RT

Design and architecture of the cloud environment is important to enable benefits

such as agility and cost savings. Key components of cloud architecture include:

Key areas of focus:

Network architectures

• Convergence of on-

premises networks to

cloud environments

• Using application and

cloud oriented protocols

• Homogenous network

constructs

• IP scheme and

addressing

Security architectures

• Authentication/federation

• Risk

• Audits

• Compliance

• Asset management

• IDS/IPS/HIDS

• Logging

• MFA

• IAM

Governance

• Billing

• Cost management

• Asset management

• Inventory

• Controls

• Architecture

standards

• SLA/SLO

• Procurement

Data management

• RPO/RTO

• Retention policies

• Replication

• Storage optimization

• ILM

Monitoring

• Notifications/alerting

• Application level

awareness

• Thresholds

• Service desk integration

Defining your architecture requires mapping on-premises to AWS solutions:

Technology

stack

On-premises solution AWS

Network VPN, MPLS Amazon VPC, VPN, AWS Direct Connect

Security Firewalls, NACLs, routing tables, disk encryption,

SSL, IDS, IPS

AWS security groups, AWS CloudHSM,

NACLs, routing tables, disk encryption, SSL, IDS, IPS

Storage DAS, SAN, NAS, SSD Amazon EBS, Amazon S3, Instance storage (SSD),

GlusterFS

Compute Hardware, virtualization Amazon EC2

Content delivery CDN solutions Amazon CloudFront

Databases DB2, MS SQL Server, MySQL, Oracle,

PostgresSQL, MongoDB, Couchbase

Amazon RDS, Amazon DynamoDB, DB2, MS SQL Server,

MySQL,PostgesSQL, Oracle, MongoDB, Couchbase

Load balancing Hardware and software load balancers, HA Proxy Elastic Load Balancing, software load balancers, HA Proxy

Scaling Hardware and software clustering, Apache

ZooKeeper

Auto Scaling, software clustering, Apache ZooKeeper

Domain name

services

DNS providers Amazon Route 53

• Language re-platforming: COBOL, PowerBuilder to Java, .Net

• Use of automated tooling such as Accenture’s Legacy2Cloud

based upon Blue Age software

Re-platforming

• Major remediation required in order to be migrated, e.g., moving apps

using EJB containers to lightweight Java containers such as Tomcat

• Detailed assessment and thorough testing required to validate

• Combination of automated and manual remediation and deployment

• Minor code changes required to be migrated

• OS changes, version upgrade

• Limited configuration changes

• Automated and manual remediation; automated deployment

• No code changes or remediation required

• Scripted/ automated

• Minimal or no impact to business

• Minimal testing required

Migration with

significant

remediation

Migration with

minor remediation

Like for like migration

CO

MP

LE

XIT

Y &

EF

FO

RT

Repeatable processes ensure predictable outcomes with measurable results

and clearly defined milestones

CUTOVER & DECOMMISSION

• Obtain go-live approval

• Schedule and perform cutover (go-live)

• Start of “enhanced support”

• SME support provided by project

to BAU support teams

• Perform postmigration review

to collect lessons learned

• Execute technical decommission

activities and release original resources

TESTING AND CERTIFICATION

• Perform acceptance testing (as required)

– Integration

– Regression

– UAT

– Performance

– Interface

• Complete operational assessment

tests (OAT)

• Obtain sign-off on migration

• Plan cutover

• Submit request to go-live

MIGRATE

• Perform remediation, code changes

• App code migration

• Data, interfaces, and

dependencies migration

• Code retrofitting

• Document code changes performed

• Perform unit testing, validate app

• Plan acceptance testing

• Confirm overall migration timeline

ON-GOING WORKLOAD, RESOURCE, AND PIPELINE MANAGEMENT

Migrated code/app,

documentation

Validated migrated application

in target environment

Migration planned App migrated and ready for acceptance test App ready to go-live

Application live

In target environment

Migrated application

More than 50 delivery centers, across 5 continents, with 194,000

deeply skilled professionals. Accenture can scale to meet the

largest AWS migrations.

Migration at enterprise scale

There are seven key components to an IT operating model. Each component is

impacted by cloud.

IT operating

model

Functions

Processes

Interfaces

Governance

Organization,

roles, and

sourcing

Performance

metrics

Tools

How we organize ourselves

to deliver IT services1

How we execute the work2

How we interact to deliver

consistent IT services3

How we make, sponsor & enforce the right decisions around IT4

What enabling technology

we use to deliver IT services7

How we measure IT effectiveness6

Who is accountable

for doing the work5

The journey to the cloud is different for every organization. The impact of the cloud on IT

operations is most significant for organizations of lower maturity levels.

• Services not defined

• No service catalog

• No SLAs

LOW MATURITY HIGH MATURITYKEY CAPABILITY AREA

SERVICE DEFINITION

SERVICE MANAGEMENT

SERVICE COSTING

PROVISIONING

VIRTUALIZATION

• No service managers

• No service metrics

• Cost of service delivery unknown at service level

• No chargeback/ show back

• Manual provisioning

• Virtualization not in place

• Automated service catalog

• External and internal services defined

• SLAs in place

• Service managers in place

• Managers manage services to optimize service

metrics

• Service costs known, tracked & managed down over time

• Cost of services transparent to users of service

(chargeback)

• Provisioning fully automated

• Self-service provisioning implemented

• Virtualization pervasive

HIGH TO VERY HIGH MODERATE TO LOWAmount of preparation

required for cloud

High impact Moderate impact

Service developmentService strategy Service management and operations IT management

Business/customer relationship management

Supplier relationship management

IT strategyformulation

Demand and supply Management

EA planning and governance

Planning and Scheduling

Portfolio delivery Management

Prog and projectManagement

Analyse

Design

Build

Test

Incident management

Business demand management

Business impact management

Problem management

Service request management

Enterprise performance mgmt.

Knowledge management

HR operationsand support

Finance and accounting ops

Finance performance mgmt.

Investment Planning

Technologyinnovation mgmt.

Architecturedevelopment

Business service level management

Strategic supplier management

Operationalsupplier management

Change management

Serviceintroduction

Release and deploymanagement

Access management

Service catalogue management

Service reporting

Event management

Asset & configManagement

Availabilitymanagement

ElementManagement

Provisioningmanagement

Capacity Management

Technical security mgmt

Commercial services mgmt.

Qualitymanagement

Talent management

Business continuity and DR

Risk management

Infrastructure security

Service Charging

Information Protection

Application Security

Almost all

points of IT

operations are

affected when

moving to the

cloud,

although there

are number of

higher impact

areas:

To meet our internal and client demand and challenges, we developed

Accenture Cloud Platform.

Cloud management

services

Service and policy management

Self servicewith governance

Key challenges

SHADOW IT

Business demand continues to grow

and requires IT to respond quickly.

Slow response threatens to IT’s

ability to meet business needs.

GOVERNANCE

While business demands increase,

IT needs to respond and add

governance controls without

holding back the pace of innovation.

BILLING / CHARGEBACK

Understanding cloud provider billing

and showing detailed invoices with IT

services and be able to buy smart.

MANAGEMENT

IT is pressed to provide services on

a granular pricing basis. Existing IT

operations and tools do not often work

“out of the box” with the cloud.

Key challenges

Agility

Rapid demand for new rapid technology development to advance the customer experience.

Governance

While business demands increase, IT needs to respond and run the solutions that are developed without holding back the pace of innovation.

Billing / chargeback

Understanding cloud provider billing and showing detailed invoices with IT services and be able to buy smart.

Management

IT is pressed to provide services on a granular pricing basis. Existing IT operations and tools do not often work “out of the box” with the cloud.

Cloud management

services

Service and policy management

Self servicewith governance

Ran a full appraisal of current infrastructure

>

COSTS Down by 73%>

Developed a plan for the move to AWS

Carried out the necessary development work and content migration

Tested the system

>AGILITY Site up in a day

>SCALING Automatic

>CAPITAL OUTLAY None

Beginning your cloud journey should start with a few key steps:

Define the business needs and drivers

Establish cloud use cases

Develop TCO model and cost estimates

Define your cloud strategy

Assess your application portfolio and move applications

Apply governance controls

Understand the impact to the organization

Please give us your feedback on this session.

Complete session evaluations and earn re:Invent swag.

http://bit.ly/awsevals