AWS DevOps Competency Consulting Partner Validation Checklist. Author: Allen Brown June 2016 Version 1.1

Transcription

1 AWS DevOps Competency Consulting Partner Validation Checklist Author: Allen Brown June 2016 Version 1.1

2 Table of Contents Introduction... 3 Competency Application and Audit Process... 3 Program Requirements... 4 AWS DevOps Competency Partner Validation Checklist AWS Customer References Solution Design Capabilities Infrastructure Build and Migration Capabilities Application Build and Migration Design Capabilities Security AWS Service Knowledge... 7 Appendix A... 8 AWS DevOps Competency: Consulting Partner Validation Checklist, v1.1 pg. 2

3 Introduction The AWS DevOps Competency Consulting Partner Validation Checklist is intended for APN Partners ( Partners ) who are interested in applying for the AWS DevOps Competency. This checklist provides the criteria necessary to achieve the DevOps Competency for APN Consulting Partners, under the AWS Competency Program. The goal is to recognize APN Partners who demonstrate expertise in DevOps principles. Partners undergo a validation of their capabilities upon applying for the AWS DevOps Competency, and every months thereafter. AWS leverages an objective third-party auditing firm to facilitate the review. AWS reserves the right to make changes to this document at any time, but will do so with effective version control, by including a summary of changes with each document released after Version 1.0. It is expected that APN Partners will review this document in detail before submitting an application for the AWS DevOps Competency, 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 Program Office if further assistance is required. Competency Application and Audit Process In order to schedule the validation, Partners must submit the Competency application by following the steps outlined below: Step #1: Review AWS DevOps Competency: Consulting Partner Validation Checklist Step #2: Submit AWS DevOps 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 DevOps Competency Complete DevOps Competency Application Once your firm s application has been submitted through the APN Portal, the APN Team will review for compliance, then send to the third party audit firm to coordinate scheduling of the audit. AWS recommends that Partners have individuals who are able to speak in-depth to the requirements at the audit. Upon completion of the audit, the audit firm will submit a report to the APN Team with a recommendation regarding Partner acceptance into the DevOps Competency Program. The final decision regarding acceptance is made by the APN Team; Partners will be notified of their status by AWS. AWS DevOps Competency: Consulting Partner Validation Checklist, v1.1 pg. 3

4 Program Requirements DevOps Competency Partners provide solutions to, or have deep experience working with businesses to help them implement continuous integration and continuous delivery practices or helping them automate infrastructure provisioning and management with configuration management tools on AWS. AWS DevOps Competency Consulting Partner Requirements APN Membership AWS Billings AWS Support AWS Customer References AWS Certifications AWS DevOps Practice Advanced+ APN Consulting Partner (view requirements) $10,000/month in AWS Revenue (direct and/or indirect) Business Level+ (view AWS Support plans) 4 AWS Public Customer References specific to DevOps projects: Customer references must be endorsed by the customer (i.e., validated and signed by the customer) Recommended: 1 joint AWS Customer Reference with a AWS DevOps Competency Technology Partner 4 AWS Certified Developer Associate or AWS Certified SysOps Administrator Associate 4 AWS Professional Level Certified DevOps Engineers DevOps practice or solution on AWS AWS DevOps practice leverages the following AWS Services: AWS CodeDeploy, AWS CodeCommit, AWS CodePipeline, AWS Elastic Beanstalk, AWS OpsWorks, AWS CloudFormation Practice recommends AWS Security Best Practices Public reference to practice, tools, and guidance on DevOps and AWS AWS DevOps Competency: Consulting Partner Validation Checklist, v1.1 pg. 4

5 AWS DevOps Competency Partner Validation Checklist In preparation for the validation process, Partners should become familiar with the items outlined in this document, and prepare objective evidence, including but not limited to: prepared demonstration to show capabilities, process documentation, and/or actual customer examples. 1.0 AWS Customer References Met Not Met 1.1 Customer References Partner has four (4) Customer transformation and modernization reference case studies. All case studies are customer endorsed through direct customer comment or approval. References include: Name of Customer State of their business prior to your engagement Problem statement/definition What you proposed Start and end dates of project Outcome(s) Lessons learned AWS services used Third party applications or solutions used Recommended: One (1) of the customer reference case studies from is a joint reference, with referable content from a DevOps certified Technology Partner found in Appendix A. This case study shows how the Technology Partner relationship was leveraged to provide services to the customer. 2.0 Solution Design Capabilities Met Not Met 2.1 Solution Capabilities Partner demonstrates that during customer engagements, a complete detailed design document is delivered such that customers and partners are both assured that due diligence, capacity planning, architectural review, and long term operational process have been assessed for the customer engagement. Evidence must be in the form of four (4) actual customer system detailed design documents that contain the following components: Documentation of customer requirements Assessment of current infrastructure/application environment Architectural details of the proposed design Details of the system performance, capacity management and availability measurement systems to be put in place to measure success of proposed design Assessment of customer s security policies and procedures with gap identification Detailed design shows that customer infrastructure is architected as per AWS security best practices as outlined as per AWS Security Best Practices Detailed design shows that the proposed design allows for governance and risk management at scale as per AWS Security at Scale and AWS Risk and Compliance For each customer engagement, Partner provides an initial and ongoing assessment of that customer s architectural status by maintaining the AWS Basic Operations Checklist and Enterprise Operations Checklist (where applicable) contained in AWS Operational Checklists. Evidence must be in the form of at least one (1) completed Basic Operations Checklist and Enterprise Operations Checklist (if applicable) for a current or past customer, and evidence that ongoing assessments are scheduled with current customers where appropriate. AWS DevOps Competency: Consulting Partner Validation Checklist, v1.1 pg. 5

6 3.0 Infrastructure Build and Migration Capabilities Met Not Met 3.1 AWS Architecture Best Practices Partner consistently provides customers with infrastructure that is aligned with AWS architecture best practices and reference architectures. The detailed design document from section 2 should include an architectural overview that provides the following details: Infrastructure architecture reliably utilizes services like Multi-AZ Auto Scaling, Amazon Virtual Private Cloud, Elastic Load Balancing, and Multi-AZ Amazon Relational Database Service to provide highly available and reliable infrastructure. 3.2 Configuration Management 3.3 Design Patterns for Reuse 3.4 Ephemeral Infrastructure Design Patterns 3.5 Monitoring Systems Evidence must be in the form of four (4) actual customer design recommendations with explanation of the customer scenario for which it was developed. Partner has introduced or modernized design that supports customer deployment and infrastructure management on AWS. Partner has introduced design patterns that help the customer consistently deploy best practices building blocks like VPCs and Web App stacks. Partner has introduced the concept of disposable and ephemeral infrastructure as part of designing for failure principles. Partner has introduced or modernized a monitoring system that supports disposable infrastructure and is integrated with deployment and build mechanisms. Monitoring system should also introduce and measure success criteria measurement. 4.0 Application Build and Migration Design Capabilities Met Not Met 4.1 Application Migration Capabilities Partner has application migration capabilities and provides continual integration, automated deployment and takes advantage of elastic, highly available infrastructure. The detailed design document from section 3 should include an application migration overview that provides the following details: Partner provides tooling that abstracts application deployment from infrastructure deployment and allows customers to, independently or in conjunction with the service, deploy and configure their applications. 4.2 CI/CD Development Lifecycle Tools Evidence must be in the form of four (4) actual customer recommendations with explanation of the customer scenario for which it was developed Partner has introduced or modernized code revision and management tools and systems. This can include introduction or modernization of code revision, change tracking and rollback tools for source code management Partner has introduced or modernized code review mechanisms Partner has introduced or modernized automated testing and regression testing mechanisms. 4.3 CI/CD Deployment Partner has introduced a deployment mechanism that leverages infrastructure designs and provides a CI/CD compatible deployment pipeline. AWS DevOps Competency: Consulting Partner Validation Checklist, v1.1 pg. 6

7 Tools Deployment tools should integrate with development pipeline toolsets and infrastructure management tools like monitoring and configuration management. 5.0 Security Met Not Met 5.1 Security Partner has introduced or modernized a code security management system. Management This can include integration into source code analysis tools, security testing frameworks or other mechanisms that allow for seamless threat analysis in development and deployment pipelines Partner has introduced or modernized an infrastructure security management system that specifically scans and audits customer accounts and infrastructure for AWS security and architecture best practices. 5.2 Security Best Practices Partner has introduced or modernized systems that support good governance, specifically including AWS CloudTrail integration Partner has introduced or modernized systems that support good governance and security, specifically including AWS Identity and Access Management. 6.0 AWS Service Knowledge Met Not Met 6.1 AWS Services In addition to their operational capabilities, for each of the following AWS services, Partner must provide the following; Description of the AWS service Examples of customer solutions leveraging each service If AWS service is not being leveraged by an active customer, a hypothetical use case is available Description of how services are supported by Partner, alone or as part of a solution comprising multiple services AWS CodeDeploy AWS CodeCommit AWS CodePipeline AWS Elastic Beanstalk AS OpsWorks AWS CloudFormation AWS DevOps Competency: Consulting Partner Validation Checklist, v1.1 pg. 7

8 Appendix A To review the complete list of AWS DevOps Technology Partners, please visit the AWS DevOps Partner Solutions webpage. Atlassian Circle Ci Cloudbees Codeship GitHub Solano Labs Travis CI Apica Blazemeter Ghost Inspector Runscope Xebia Labs Puppet Chef Ansible Saltstack AWS DevOps Competency: Consulting Partner Validation Checklist, v1.1 pg. 8