aws migration competency - cloud object storage | store ... · pdf fileaws migration...

AWS Migration Competency Consulting Partner Validation Checklist April 2017 Version 1.1

AWS Migration Competency:

Consulting Partner Validation Checklist

AWS Migration Competency: Consulting Partner Validation Checklist, v1.1 pg. 2

Table of Contents

Introduction ............................................................................................................................. 3

Competency Application and Audit Process ........................................................................ 3

Program Policies ..................................................................................................................... 3

AWS Migration Competency Program Prerequisites ............................................................ 5

AWS Migration Consulting Partner Validation Checklist ..................................................... 6

Migration Consulting Requirements ...................................................................................... 6

1.0 AWS Customer References – Migration Consulting ................................................ 6

Migration Delivery Requirements........................................................................................... 7

2.0 AWS Customer References – Migration Delivery..................................................... 7

Appendix A: Example of Architecture Diagrams .................................................................. 9

Appendix B: Example of Security Documentation Outline .................................................. 9

Appendix C: Example of Migration Process........................................................................ 10




Introduction

The Competency Partner Validation Checklist is intended for APN Partners who are interested in applying for AWS Competency. This checklist provides the criteria necessary to achieve the designation under the AWS Competency Program. The goal of the AWS Competency Program is to recognize APN Partners who demonstrate technical proficiency and proven customer success in specialized solution areas. APN Partners undergo a validation of their capabilities upon applying for the specific Competency, and every 12 months thereafter. AWS leverages in-house expertise and a third-party firm to facilitate the review. AWS reserves the right to make changes to this document at any time. It is expected that APN Partners will review this document in detail before submitting a Competency application, even if all of the pre-requisites are met. If items in this document are unclear and require further explanation, please contact your AWS Partner Development Representative (PDR) or Partner Development Manager (PDM) as the first step. Your PDR/PDM will contact the Competency Program Team if further assistance is required.

Competency Application and Audit Process

In order to begin the validation process, please follow the steps outlined below: Step #1: Review the Partner Validation Checklist

Step #2: Submit a Competency Application through the APN Portal

• Login to the APN Portal

• Click “View My APN Account” in left navigation

• Scroll to AWS Competencies and select the appropriate Competency

• Complete the Competency Application

Incomplete applications will not be considered and will be rejected.

Once your firm’s application has been submitted through the APN Portal, the APN Team will review for compliance and will send to the third party firm to coordinate scheduling of your Competency review. AWS recommends that APN Partners have individuals who are able to provide evidence of compliance and to speak in-depth to the requirements available during the validation process. Upon completion of the third party review, a recommendation is given to the APN Team regarding APN Partner acceptance into the Competency. The final decision regarding acceptance is made by the APN Team; APN Partners will be notified of their status by AWS.

Program Policies

An APN Partner's application to the Competency may be rejected at the discretion of the Global Segment Business or Technical Lead. Rejections may be made due to estimated ability to consistently implement technical solutions, lack of current required APN Partner certifications, judgment of the technical or business merit of the proposed solution, perceived lack of solution delivery capabilities, or any other business or technical criteria deemed critical.

http://aws.amazon.com/partners/competencies

https://www.apn-portal.com/




Competency status can be revoked at the discretion of the Global Segment Business or Technical Lead. Revocations may be issued due to loss of required APN Partner certifications, lack of progress toward billing or win goals, repeated violations of AWS PR guidelines, evidence of poor customer experience, including cost vectors, when using the solution, or any other business/technical factors that would indicate that the practice or solution may not meet current requirements, or is projected not to meet future requirements. Competency status must be renewed annually on a calendar year basis. Requirements for renewal may change from year to year, subject to the business and technical needs of AWS and its customers.




AWS Migration Competency Program Prerequisites

AWS Migration Competency Partners provide solutions or have deep experience helping businesses move successfully to AWS, through all phases of complex migration projects, discovery, planning, migration and operations. They focus on developing their customer’s internal skills and helping to build the foundations required for complex migrations to AWS. They are experts in reducing friction when migrating legacy applications.

AWS Migration Competency – Consulting Partner Prerequisites

APN Membership APN Partner must meet Advanced tier+ APN Consulting Partner requirements (view requirements)

AWS Customer References

APN Partner must provide ≥ 5 AWS customer references specific to completed Migration projects of 10 applications or more:

2 of the 5 AWS customer references must be public (i.e., documented in a case study, white paper, or blog post). Public references must mention AWS, the end customer, and the APN Partner.

References must be related directly to the Migration segment, and not be reused for other segments

References must be for projects started within the past 12 months, and must be for projects that are in production, rather than in pilot or proof of concept stage

All customer references submitted must have supporting documentation providing evidence of compliance to the requirements of this checklist

AWS Migration Practice

APN Partner must have a Migration practice on AWS, including:

Qualifying for and posting an AWS public support statement on APN Partner’s website detailing the APN Partner’s Migration practice on AWS and including public reference to the APN Partner’s solution, practice, tools, or guidance on Migration. For example, an acceptable public support statement is a landing page on the APN Partner’s website that contains various element, including the AWS solutions and competency use cases, reference architecture, technology partnerships, customer references, sample TCO pricing, and any other relevant information supporting the APN Partner’s expertise related to Migration and highlighting the partnership with AWS through the APN.

Pass technical review by AWS Solution Architects

Recommends AWS Security Best Practices

AWS Migration Category Requirements

(Must meet requirements of one to achieve Competency)

Migration Consulting

≥ 10 AWS Certifications in total

o ≥ 2 Professional Level

AWS Certifications

Must hold AWS DevOps

Competency

Migration Delivery

≥ 30 AWS Certifications in total

o ≥ 8 Professional Level AWS

Certifications

Must be an audited AWS Managed

Service Provider and/or hold the AWS

DevOps Competency

Provides professional services to

perform migrations on behalf of

customers

Provides project management

functions for migration projects

http://aws.amazon.com/partners/consulting

http://media.amazonwebservices.com/AWS_Security_Best_Practices.pdf

http://aws.amazon.com/solutions/partners/dev-ops/


http://aws.amazon.com/partners/msp/

http://aws.amazon.com/partners/msp/






AWS Migration Consulting Partner Validation Checklist

In preparation for the validation process, APN Partners should become familiar with the requirements of this checklist. Supporting documentation (e.g., design and architectural documents) for the submitted customer references must be provided, in order to demonstrate compliance to the below requirements. Please review by the Migration category your firm wishes to apply for (Migration Consulting or Migration Delivery).

Migration Consulting Requirements

AWS Migration Competency Partners provide solutions or have deep experience helping businesses move successfully to AWS, through all phases of complex migration projects, discovery, planning, migration, and operations. Migration Consulting Partners provide expertise and training to help develop their cloud capabilities. These APN Partners will provide DevOps, application, and environment modernization consulting to set customers on the path to success.

1.0 AWS Customer References – Migration Consulting Met Not Met

1.1 Customer References

APN Partner has five (5) AWS customer references of completed Migration projects for mid-market or Enterprise customers. 2 of the 5 references must be public. References include: Name of Customer

Problem statement/definition

What you proposed

AWS services used

Third party applications or solutions used

Start and end dates of project

Outcome(s)/results

Lessons learned

Number of distinct applications migrated (≥ 10 per project)*

Number of source VM’s and number of resulting AWS instances (source VMs ≥

100)**

* Note that applications need to be distinct applications. Applications that are services or components of a larger application are counted as a single application. Please provide the list of application names and a brief description of each application. ** A referenced project must have migrated either 10+ applications or 100+ source VMs.

1.2 Architecture Best Practices

References must show AWS architecture diagrams for each of the projects. The architecture information must cover all the AWS components and services deployed. For architecture diagram example, refer to Appendix A.

1.3 Security Best Practices

References must show how migrated environments were deployed against AWS Security Best Practices. For an example of Security Best Practices documentation content, refer to Appendix B.

1.4 Consistent Methodology and Process

References must demonstrate a consistent methodology and process applied through well-defined migration phases. For an example of multi-phase migration process, refer to Appendix C. The competency application must include the following materials for each of the projects if applicable: Application and resource discovery and tools used

Project plan with role and responsibility assignment (RACI)

https://d0.awsstatic.com/whitepapers/Security/AWS_Security_Best_Practices.pdf





Cost analysis

Migration plan including procedure, tools, downtime management and rollback

strategy, and validation plan

Post-migration cost or performance optimization

Operation practices in AWS

1.5 Completion

References must show completed projects.

Migration Delivery Requirements

AWS Migration Competency Partners provide solutions or have deep experience helping businesses move successfully to AWS, through all phases of complex migration projects, discovery, planning, migration, and operations. Migration Delivery Partners accelerate customer cloud adoption by providing technical personnel, tools, education, and technical support to customers in the form of professional services. These partners either are, or have a relationship with an audited AWS Managed Service Provider to help customers with ongoing support of AWS workloads where required.

2.0 AWS Customer References – Migration Delivery Met Not Met

2.1 Customer References

APN Partner has five (5) AWS customer references of completed Migration projects for mid-market or Enterprise customers. 2 of the 5 references must be public. References include: Name of Customer

Problem statement/definition

What you proposed

AWS services used

Third party applications or solutions used

Start and end dates of project

Outcome(s)/results

Lessons learned

Number of distinct applications migrated (≥ 10 per project)*

Number of source VM’s and number of resulting AWS instances (source VMs ≥

100)**

* Note that applications need to be distinct applications. Applications that are services or components of a larger application are counted as a single application. Please provide the list of application names and a brief description of each application. ** A referenced project must have migrated either 10+ applications or 100+ source VMs.

2.2 Professional Services

References must be accompanied by a signed statement of work showing the scope and scale of professional services provided.

2.3 Project Ownership

References must be accompanied by a project plan or RACI that shows the APN partner jointly or singly owned project management of the migration.

2.4 Architecture Best Practices

References must show AWS architecture diagrams for each of the projects. The architecture information must cover all the AWS components and services deployed. For architecture diagram example, refer to Appendix A.

2.5 Security Best Practices

References must show how migrated environments were deployed against AWS Security Best Practices. For an example of Security Best Practices documentation content, refer to Appendix B.






2.6 Consistent Methodology and Process

References must demonstrate a consistent methodology and process applied through well-defined migration phases. For an example of multi-phase migration process, refer to Appendix C. The competency application must include the following materials for each of the projects if applicable: Application and resource discovery and tools used

Project plan with role and responsibility assignment (RACI)

Cost analysis

Migration plan including procedure, tools, downtime management and rollback

strategy, and validation plan

Post-migration cost or performance optimization

Operation practices in AWS

2.7 Completion

References must show completed projects.




Appendix A: Example of Architecture Diagrams

Appendix B: Example of Security Documentation Outline

The competency application shall document the Security Best Practices including the following areas if applicable.

Threat modeling & application security (AWS Shield, WAF, security between application layers, etc.)

Protecting operating system (AMI hardening, OS security hardening, etc.)

IAM (Identity Access Management) (Two-factor authentication, policies, roles, etc.)

Infrastructure security (VPC design, security groups, network access control, etc.)

Securing data at rest (S3, EBS, RDS encryption, etc.)

Securing data on transit (SSL/TLS, etc.)

Data privacy and data restrictions (compliance with security standards, etc.)

Monitoring, logging, and alert (CloudWatch, CloudTrail, or other tools)

Vulnerability management and penetration testing (Trusted Advisor, etc.)





Appendix C: Example of Migration Process

References for each of the completed projects must demonstrate a consistent methodology and process applied through multiple migration phases as exemplified below. Though specific details may vary from projects to projects, a solid migration framework with major phases and work areas shall be clearly identified and exercised across the projects. It is the consistent methodology and process that is validated through each and every Migration Competency application.

Migration Phase Sample Task Areas

1. Opportunity Evaluation Opportunity Evaluation Phase – may involve but not limited to analyzing cost and benefits for migration, determining IT portfolios to be migrated.

2. Planning Planning Phase – may involve but not limited to discovering resources used by the portfolios, assessing security risks, determining application dependencies and priorities, validating business logics and compliance requirements, organizing migration teams, and accordingly forming a migration plan.

3. Design Design Phase – may involve but not limited to identifying migration patterns (retain, retire, re-hosting, re-platform, refactor, re-purchase), architecting AWS application infrastructure, determining AWS services, and conducting Well-Architected Review, reviewing business acceptance criteria, conducting migration pilot and test.

4. Migration Migration Phase – may involve but not limited to migrating applications and data per the migration plan, integrating with AWS infrastructure, services, and operations, validating application functionality, security, performance, and reliability per application requirements and acceptance criteria.

5. Operation & Optimization Operation & Optimization Phase – may involve but not limited to establishing and conducting service management, assessing and optimizing performance and cost.

aws migration competency - cloud object storage | store ... · pdf fileaws migration...

Documents