AWS Telecom Competency
Service Offering Validation Checklist
Validity Period: February 2025-August 2025
This version of the checklist was released on February 14th, 2025. The next version of this checklist is expected to be released in August 2025. AWS Partners may continue to use this version of the checklist until November 2025. Please review the change log for a list of changes (if any) since the previous version.
Introduction
The goal of the AWS Specialization Programs is to recognize AWS Partner Network Partners (“AWS Partners”) who demonstrate and maintain technical proficiency and proven customer success in specialized AWS Partner solution areas. The AWS Competency Partner Validation Checklist (“Checklist”) is intended for AWS Partners who are interested in applying for an AWS Specialization. This Checklist provides the criteria necessary to achieve the specialization as a consulting partner. AWS Partners undergo a technical validation of their capabilities upon applying for a specific specialization. AWS leverages in-house expertise and a third-party firm to facilitate the technical validation. AWS reserves the right to make changes to this document at any time and without notice.
Expectation of Parties
It is expected that AWS Partners will review this document in detail before applying for the AWS Competency Program, even if all of the prerequisites are met. If items in this document are unclear and require further explanation, please contact your AWS Partner Development Representative (“PDR”) or AWS Partner Development Manager “(PDM”) as the first step. Your PDR/PDM will contact the program office if further assistance is required.
AWS Partners should complete the Self-Assessment Spreadsheet linked at the top of this page, prior to submitting a program application. Once completed, AWS Partners must submit an application in APN Partner Central. Visit the AWS Competency Program guide for step-by-step instructions on how to submit an application.
AWS will review and aim to respond back with any questions within five business days to initiate scheduling of your technical validation or to request additional information.
AWS Partners should prepare for the technical validation by reading the Checklist, completing a self-assessment using the Checklist, and gathering and organizing objective evidence to share with the reviewer on the day of the technical validation.
AWS recommends that AWS Partners have individuals who are able to speak in-depth to the requirements and the customer examples during the technical validation. The best practice is for the AWS Partner to make the following personnel available for the technical validation: one or more highly-technical AWS certified engineers/architects in the area of competency specialty, an operations manager who is responsible for the operations and support elements, and a business development executive to conduct the overview presentation.
AWS may revoke an AWS Partner’s Competency designation if, at any time, AWS determines in its sole discretion that such AWS Partner does not meet its AWS Competency Program requirements. If an AWS Partner’s AWS Competency designation is revoked, such AWS Partner will (i) no longer receive benefits associated with its designation, (ii) immediately cease use of all materials provided to it in connection with the applicable AWS Competency designation and (ii) immediately cease to identify itself as a member of the AWS Competency.
AWS Partners should ensure that they have the necessary consents to share with the auditor (whether AWS or a third-party) all information contained within the objective evidence or any demonstrations prior to scheduling the audit.
AWS Telecom Competency Definition
Vertical AWS Competencies are designed for AWS Partners with segment-specific solutions and practices on AWS. These are specialized AWS Partners with extensive expertise and experience focused on a specific market segment. AWS Partners with highly targeted solutions to industry-specific challenges and consulting practices that offer a unique segment domain knowledge are best positioned to pursue vertical AWS Competencies. AWS Telco Competency Partners have demonstrated technical proficiency and proven customer success in specialized Telco industry solutions defined by categories.
Below are the five (5) categories for Telco Consulting Competency. A total of minimum 4 case studies are required, and at least 2 of the 4 must be public. Partners can submit exception requests regarding publicly referring to customer names. Partners applying for only one category must submit 4 total case studies for the selected category. Partners applying for more than one category must submit a minimum of 2 case studies per category. Note that case studies can be used across multiple categories if applicable.
- Mobile Networks - This category consists of Radio Access Network and Core Network integrated with AWS cloud infrastructure to deliver end-to-end cellular network services.
- Operation Support Systems (OSS) - This category consists of functions such as Service Quality Management and Fault Management utilizing AWS cloud services for communication service providers to manage their networks.
- Business Support Systems (BSS) - This category consists of functions such as Customer Order Management and Billing utilizing AWS cloud services for communication service providers to run their business operations towards customers.
- Communication as a Service (CaaS) - This category is a collection of different services used by communication service providers to facilitate business communications. There are three domains of CaaS services - Contact Center, Unified Communications as a Service, and Communications Platform as a Service .
- Media & TV - This category consists of television broadcast or video streaming via wires, wireless, cables, satellite, or any other communication channel supported by AWS cloud services.
AWS Partners can apply for a minimum of one and a maximum of five service categories as your specialization(s). Irrespective of the number of Telco Service Competency categories you apply, you need to fill out - Common Practice Requirements, Common Customer Requirements, and Telco Common Customer Requirements. You then fill out category-specific tabs with associated customer examples.
Requirements Overview
The subsequent sections of this document define the requirements for AWS Partners to achieve the AWS Telecom Competency designation. These requirements are broken down into the following categories:
AWS Telecom Competency Program Prerequisites - These requirements will be validated by the AWS Competency program team before scheduling a technical validation.
Common AWS Partner Practice Requirements - These requirements validate the mechanisms and organizational practices in place to ensure the AWS Partner is able to consistently deliver high quality customer outcomes for AWS projects.
Telecom Practice Requirements - These requirements validate the AWS Partner's overall capabilities related to delivering Telecom solutions for customers on AWS.
Common Customer Example Requirements - These requirements validate that the architectural designs and implementation details of each of the provided customer examples follow best practices defined in the AWS documentation and other resources such as the AWS Well-Architected Framework. Use technical calibration guide for control-by-control best practices and example responses.
Telecom Customer Example Requirements - These requirements validate whether the provided customer examples demonstrate Telecom-specific best practices and align with the target customer use cases for this AWS Competency.
AWS Telecom Competency Program Prerequisites
The following items will be validated by the AWS Competency Program Manager; missing or incomplete information must be addressed prior to scheduling of the technical validation.
-
1.0APN Program Membership
-
1.1Program Guidelines
The AWS Partner must read the Program Guidelines and Definitions before applying to the Telecom Competency Program. Click here for Program details.
-
1.2Services Path Membership
Partner must be at the Validated or Differentiated stage within the Services Path. Partners should talk to their PDR/PDM about how to join the Services Path.
-
1.3AWS Partner Tier
Partner must be an AWS Advanced or Premier Tier Partner.
-
-
2.0Example AWS Customer Deployments
-
2.1Production AWS Customer Case Studies
AWS Partner must privately share with AWS details about four (4) unique examples of Telecom projects executed for four (4) unique AWS customers. Each case study must demonstrate how the partner offering was used by a customer to solve a specific Telecom customer challenge using AWS.
In addition to the required case study details provided in AWS Partner Central, the partner must also provide architecture diagrams of the specific customer deployment and information listed in the technical requirements sections of this validation checklist.
The information provided for these case studies will be used by AWS for validation purposes only. AWS Partner is not required to publish these details publicly.
AWS Partner can reuse the same case study across different AWS Specialization designations as long as the case study and implementation scope are relevant to those designations. The partner should make sure the existing case study clearly explains the relevance to each designation they are applying for.
In cases where a case study is used across multiple AWS Partner Specialization applications, the partner must attach a completed self-assessment spreadsheet for each Specialization with all service-specific details provided.
AWS will accept one case study per customer. Each customer must be a separate legal entity to qualify. The partner may use an example for an internal or affiliate company of the partner if the offering is available to outside customers.
All case studies must describe deployments that have been performed within the past 18 months and must be for projects that are in production with customers, rather than in a ‘pilot’ or proof of concept stage.
All case studies provided will be examined in the Documentation Review of the Technical Validation. The partner offering will be removed from consideration if the partner cannot provide the documentation necessary to assess all case studies against each relevant validation checklist item, or if any of the validation checklist items are not met.
-
2.2Publicly Available Case Studies
At least two (2) of the provided case studies must be publicly available examples describing how the AWS Partner used AWS to help solve a specific customer challenge related to Telecom. These publicly available examples may be in the form of formal customer case studies, white papers, videos, or blog posts. The partner will provide the publicly available URL (published by the partner) in the AWS Partner Central "Case Study URL' field, which must include the following details:
- AWS Customer name
- AWS Partner name
- AWS Customer challenge that aligns with the scope of the competency and selected category
- Using both high-level and technical details, describe how AWS was leveraged as part of the AWS Partner solution
- Outcome(s) and/or quantitative results
Anonymized Public Case Studies
In cases where the partner cannot publicly name customers due to the sensitive nature of the customer engagements, the partner may choose to anonymize the public case study. Anonymized public case study details will be published by AWS, but the customer name will remain private. The partner must provide the AWS Customer name in the ‘Company name’ field of the AWS Partner Central case study for validation purposes, but it will not be published by AWS. The case study fields that will be published to Partner Solutions Finder (PSF) by AWS include the ‘Title’, ‘Case Study Description’, and ‘Case Study URL’. The partner will provide the publicly available URL (published by the partner) in the AWS Partner Central‘Case Study URL’ field, which must include the following details:
- AWS Customer description (e.g. a top 5 US retailer, a Fortune 500 financial institution, etc.)
- AWS Partner name
- AWS Customer challenge that aligns with the scope of the competency and selected category
- Using both high-level and technical details, describe how AWS was leveraged as part of the AWS Partner solution
- Outcome(s) and/or quantitative results
For best practice on how to write an accepted Public case study, see the Public Case Study Guide.
-
2.3Telecom Case Studies
For every category the AWS Partner selects to be validated for, the partner must provide two (2) case studies that include the requirements for the selected category. It is possible to use the same case studies for multiple category requirements if the scope of the project allows. If the partner is applying for additional categories and the four (4) minimum required case studies do not collectively cover all applied-for categories, the partner will need to submit additional unique case studies executed for additional unique AWS customers.
-
-
3.0AWS Partner Self-Assessment
-
3.1AWS Partner Self-Assessment
AWS Partner must conduct a self-assessment of their compliance to the requirements of the AWS Telecom Consulting Partner Validation Checklist. A version of this checklist is available in spreadsheet format. Links to the appropriate Self-Assessment Spreadsheet can be found at the top of this page.
- AWS Partner must complete all sections of the Self-Assessment Spreadsheet. For competency with multiple categories, AWS Partners will fill in details for the chosen application Category and mark other Categories as N/A.
- Completed Self-Assessment Spreadsheet must be uploaded at the time of submitting an application in APN Partner Central.
- It is recommended that AWS Partner have their AWS Partner Solution Architect, Partner Development Representative (PDR), or Partner Development Manager (PDM) review the completed Self-Assessment Spreadsheet before submitting to AWS. The purpose of this is to ensure the AWS Partner’s AWS team is engaged and working to provide recommendations prior to the validation and to help ensure a positive validation experience.
-
Common AWS Partner Practice Requirements
The following requirements validate the mechanisms and organizational practices in place to ensure the AWS Partner is able to consistently deliver high quality customer outcomes for AWS projects. This section of the requirements are WAIVED if the associated offering has an approved Service Offering Foundational Technical Review OR if the AWS Partner has achieved another AWS Services Competency within the last 12 months.
Telecom Practice Overview
-
POV-001 - Customer Presentation
AWS Partner has a company overview presentation that sets the stage for customer conversations about their AWS Telecom capabilities and showcases AWS Partner’s demonstration capabilities.
Presentation contains information about the AWS Partner’s AWS Telecom capabilities, including AWS specific differentiators, e.g., what is unique about the AWS Partner’s practice that can only be accomplished leveraging AWS.
Overview presentations contain:
- Company history
- Office locations
- Number of employees
- Customer profile, including number, size, and industries of customers
- Overview of Telecom practice
- Notable AWS projects
Please provide the following as evidence:
- Delivery of presentation by a business development executive at the beginning of the validation session. This should be limited to 15 minutes.
-
POV-002 - Maintaining AWS Expertise
AWS Partner has internal mechanisms for maintaining their consultants' expertise on Telecom-related AWS services and tools.
Please provide the following as evidence:
- List of internal and/or external AWS-focused education events lead by AWS Partner staff (e.g. formal training, lunch and learns, meetups, user groups, etc.) in last 12 months.
- Resources provided by AWS Partner to staff for ongoing AWS skills development
-
POV-003 - AWS Partner Solution Selling
AWS Partner must describe how Telecom opportunities are identified, how their sellers are trained to identify and sell those opportunities, and specific demand generation/lead generation efforts associated to their AWS Telecom practice.
Please provide the following as evidence:
- A description on how the AWS Partner engages with customers, their internal sellers, and AWS sellers if applicable.
-
POV-004 - AWS Sales Engagement
AWS Partner must describe how and when they engage with AWS sellers and AWS Solutions Architects.
Please provide the following as evidence:
- A verbal description for how and when they engage AWS sellers or AWS Solutions Architects on an opportunity or in the form of a demonstration of the AWS Opportunity Management tool in AWS Partner Central with sales qualified opportunities submitted (sales qualified = budget, authority, need, timeline, and competition fields completed).
-
POV-005 - Training for Internal Personnel
AWS Partner must have a process to ensure that there are sufficient Telecom trained personnel to effectively support customers.
Please provide the following as evidence:
- An established training plan including on-boarding processes that identify job roles (sellers, solutions architects, project managers) and required training paths
- A verbal description of methods used to allocate required resources to Telecom projects
AWS Partner Delivery Model
-
PRJ-001 - Expected Outcomes
AWS Partner has processes for working with customers to determine and define expected outcomes associated with the projects.
Please provide the following as evidence:
- Project deliverable templates or other resources used for project scoping and definition
-
PRJ-002 - Scope
AWS Partner has processes to determine scope of work with specific criteria defining customer project with expected deliverables.
Please provide the following as evidence:
- Project templates or other resources(e.g. RACI Matrix) used for project scoping and definition
-
PRJ-003 - Statement of Work
AWS Partner has standard Statement of Work (SOW) templates for Telecom projects that can be customized to customer needs.
Please provide the following as evidence:
- Default SOW template
-
PRJ-004 - Project Manager
AWS Partner assigns Project Manager to each project to ensure project remains on time and within budget.
Please provide the following as evidence:
- Documentation to show that Project Managers were assigned to each of the 4 customer example projects.
-
PRJ-005 - Change Management
AWS Partner has processes to document, manage, and respond to requests for changes to the project scope.
Please provide the following as evidence:
- Documentation of change management practices
Customer Satisfaction
-
CSN-001 - Customer Acceptance for Projects
AWS Partner has a customer acceptance process.
Please provide the following as evidence:
- Example customer training documents
- SOW language describing handoff responsibilities and acceptance criteria
-
CSN-002 - Customer Satisfaction Aligned to Project Milestones
AWS Partner implements customer satisfaction checkpoints as part of the project plan.
Please provide the following as evidence:
- Project plan and customer satisfaction results for milestone-defined checkpoints
Telecom Practice Requirements
The following requirements apply to AWS Partners' Telecom Practice. Partners must also select at least one of categories outlined as a section below and meet the requirements within the selected category.
Mobile Networks
For this category, provide a reference architecture and summary of custom policies, scripts, procedures, and training with a list of products used to deliver solutions to customers with the following requirements. Reference architectures can be re-used between sections if they are broad enough to apply.
-
EDGE-001 - AWS Edge Service Experience
Mobile Network's real-time characteristics require network functions (e.g., 5G User Plane Function) to be designed and implemented at AWS Cloud Edge. AWS Telco Mobile Network Service Partner must be experienced in using AWS Edge Services such as one or more of the following for Mobile Network solutions.
- Outposts Rack
- Outposts Server
- Snowball
- Snowcone
Please provide the following as evidence:
- Written description of how each submitted customer example use the specific AWS edge service.
-
CAP-001 - Capacity Planning
AWS Telco Mobile Network Service Partner must be experienced in RAN capacity planning, dimensioning or tracking.
Please provide the following as evidence:
- Process documents used for validation, optimization or tracking of radio capacity planning for production networks.
-
CORE-001 - Mobile Core Network Component and Interface Experience
AWS Telco Mobile Network Service Partner must be experienced in implementing, integrating or managing Core Network solutions required for 5G or 4G/LTE Mobile Networks in compliance with 3GPP standard interfaces and integration points.
Please provide the following as evidence:
- Documentation from reference examples illustrating experience with implementing, integrating or managing 5G or 4G/LTE Core Network solutions in compliance with 3GPP standard interfaces and integration points with clear definitions of AWS Service Partner's responsibilities and deliverables.
-
CORE-002 - Interoperability and Validation
AWS Telco Mobile Network Service Partner must be experienced in validating interoperability between RAN and Mobile Core vendors.
Please provide the following as evidence:
- AWS Services Partner must provide "plugfest" participation or other customer example interoperability testing examples of validation between RAN and Mobile Core vendors.
-
CORE-003 - Core Capacity Planning
AWS Telco Mobile Network Service Partner must be experienced in Core capacity planning or dimensioning.
Please provide the following as evidence:
- Example of the process used for validation and optimization of Core Network capacity planning from customer references, illustrating approach to capacity planning across network, compute, storage and databases.
-
DAT-001 - Data Management
AWS Telco Mobile Network Service Partner must implement appropriate data security, governance and controls for the different types of data processed in Telco networks according to the implementation (RAN or Core Network), the use case (e.g., consumer network and private 5G) and Geo or Mobile Network Operator specific regulations.
Please provide the following as evidence:
- Documents, best practices or SOPs on appropriate data security, governance and controls for data processing in Telco Networks.
-
PERM-001 - Mobile Network Performance and KPIs
AWS Telco Mobile Network Service Partner must ensure that implementations support latency, throughput and other performance critical Mobile Network KPIs through appropriate technology selection, implementation or managed services.
Please provide the following as evidence:
- Example solution design or implementation to meet use case specific customer KPI or example managed service observability of KPIs.
BSS
This category defines the BSS specific practice requirements.
-
BSS-001 - BSS training for internal personnel
AWS Telco Service Partner must have processes to ensure that there are BSS trained personnel (TMForum certified) to effectively support customers.
Please provide the following as evidence:
- A description of methods used to allocate required resources to BSS projects and data relating to levels of certification (e.g. TMForum certification)
-
BSS-002 - Data Management - BSS
AWS Telco Services Partner must be implement appropriate data security, governance and controls for the different types of data processed in Telco networks according to the implementation (BSS) and the use case (for example network performance management, real time charging ).
Please provide the following as evidence:
- Describtion of how appropriate data security, governance and controls for the different types of data processed in Telco networks is demonstrated in the provided customer example references.
OSS
This category defines the OSS specific practice requirements.
-
OSS-001 - OSS training for internal personnel
AWS Telco Service Partner must have processes to ensure that there are BSS trained personnel (TMForum certified) to effectively support customers.
Please provide the following as evidence:
- A description of methods used to allocate required resources to OSS projects and data relating to levels of certification (e.g. TMForum certification)
-
OSS-002 - Data Management - OSS
AWS Telco Services Partner must implement appropriate data security, governance and controls for the different types of data processed. This includes data integration between systems, for example shipping Data Records (XDRs) to a data lake. All integrated data pipelines between OSS systems and data lakes/data warehouses require appropriate encryption and data management.
Please provide the following as evidence:
- Describtion of how appropriate data security, governance and controls for the different types of data processed in Telco networks is demonstrated in the provided customer example references.
Media & TV
This category defines the Media & TV specific practice requirements.
-
MTV-001 - Media Transfer and Encryption
When the implementation, migration, integration or managed service supports connections to on-premises facilities, the solution documentation must describe the hybrid connection’s SLA, performance and reliability, and the hybrid connectivity must offer encryption in transit. The solution can offer Direct Connect or VPN over the internet. However, the solution must offer and explain how a private connection can be enabled.
Please provide the following as evidence:
- A technology design or demonstration, including use case examples, or for managed service, observability and process description, from the example customer references submitted.
CaaS
This category defines the CaaS specific practice requirements.
-
CAAS-001 - Data Management - CaaS
AWS CaaS partners must demonstrate experience in meeting regulatory compliance for end-customer implementations relevant to all applicable geographical regions. Examples include, but are not limited to: Payment Card Industry Data Standard Security (PCI), Personally Identifiable Information (PII), Health Insurance Personal Accountability Act (HIPAA), and General Data Protection Regulation (GDPR). In addition, evidence of regulatory compliance of proper handling, including encryption, storage, retention, deletion of interaction recordings of any media type, including, but not limited to voice, video and digital transcripts must be provided for all end-customer implementations. Evidence of regulatory compliance for outbound communications such as, but not limited to, Short Message Service (SMS), voice calls, and social media or digital channels, as well as adherence to requirements for recipients to opt-out of such communications to the extent of applicable, regional requirements.
Please provide the following as evidence:
- Documentation of appropriate data management processes which have been implemented and validated according to the required compliances.
Common Customer Example Requirements
If you have completed an AWS Well-Architected Framework Review (WAFR) for the customer example which shows zero outstanding high-risk issues (HRIs) in the Security, Operational Excellence, and Reliability pillars, you are not required to provide evidence for the following requirements. Please upload an exported WAFR report for each of the customer example instead.
All of the following requirements must be met by at least one of the four submitted customer examples. See specific evidence for each control. Refer to calibration guide for example responses.
Documentation
Requirements in this category relate to the documentation provided for each customer example.
-
DOC-001 - Provide Architecture diagram designed with scalability and high availability
AWS Partner must submit architecture diagrams depicting the overall design and deployment of its AWS Partner solution on AWS as well as any other relevant details of the solution for the specific customer in question.
The submitted diagrams are intended to provide context to the AWS Solutions Architect conducting the Technical Validation. It is critical to provide clear diagrams with an appropriate level of detail that enable the AWS Solutions Architect to validate the other requirements listed below.
Each architecture diagram must show:
- All of the AWS services used
- How the AWS services are deployed, including virtual private clouds (VPCs), availability zones, subnets, and connections to systems outside of AWS.
- Elements deployed outside of AWS, e.g. on-premises components, or hardware devices.
- how design scales automatically - Solution adapts to changes in demand. The architecture uses services that automatically scale such as Amazon S3, Amazon CloudFront, AWS Auto Scaling, and AWS Lambda.
- how design has high availability with multi-AZ or multi-region deployment. When intentional tradeoffs have been made (e.g. to optimize cost in favor of high availability), please explain the customer's requirements.
Please provide the following as evidence (required for all provided customer examples):
- An architecture diagram depicting the overall design and deployment of your solution on AWS.
- Explanation of how the major solutions elements will keep running in case of failure.
- Description of how the major solutions elements scale up automatically.
Secure Customer AWS Account Governance and Access
Any AWS accounts created by the AWS Partner on behalf of the customer or AWS accounts that the AWS Partner administers as part of the engagement must meet the following requirements.
-
ACCT-001 - Define Secure AWS Account Governance Best Practice
AWS expects all Services Partners to be prepared to create AWS accounts and implement basic security best practices. Even if most of your customer engagements do not require this, you should be prepared in the event you work with a customer who needs you to create new accounts for them.
Establish internal processes regarding how to create AWS accounts on behalf of customers when needed, including:
- When to use root account for workload activities
- Enable MFA on root
- Set the contact information to corporate email address or phone number
- Enable CloudTrail logs in all region and protect CloudTrail logs from accidental deletion with a dedicated S3 bucket
Please provide the following as evidence:
- Documents describing Security engagement SOPs which met all the 4 criteria defined above. Acceptable evidence types are security training documents, internal wikis, or standard operating procedures documents.
- Description of how Secure AWS Account Governance is implemented in one (1) of the submitted customer examples.
-
ACCT-002 - Define identity security best practice on how to access customer environment by leveraging IAM
Define standard approach to access customer-owned AWS accounts, including:
- Both AWS Management Console access and programmatic access using the AWS Command Line Interface or other custom tools.
- When and how to use temporary credentials such as IAM roles
- Leverage customer's existing enterprise user identities and their credentials to access AWS services through Identity Federation or migrating to AWS Managed Active Directory
Establish best practices around AWS Identity and Access Management (IAM) and other identity and access management systems, including:
- IAM principals are only granted the minimum privileges necessary. Wildcards in Action and Resource elements should be avoided as much as possible.
- Every AWS Partner individual who accesses an AWS account must do so using dedicated credentials
Please provide the following as evidence:
- Security engagement Standard Operation Procedure (SOP) which met all the 2 criteria defined above. Acceptable evidence types are: security training documents, internal wikis, standard operating procedures documents. Written descriptions in the self-assessment excel is not acceptable.
- Description of how IAM best practices are implemented in one (1) of the submitted customer examples.
Operational Excellence
Requirements in this category relate to the ability of the AWS Partner and the customer to run and monitor systems to deliver business value and to continually improve supporting processes and procedures.
-
OPE-001 - Define, monitor and analyze customer workload health KPIs
AWS Partner has defined metrics for determining the health of each component of the workload and provided the customer with guidance on how to detect operational events based on these metrics.
Establish the capability to run, monitor and improve operational procedure by:
- Defining, collecting and analyzing workload health metrics w/AWS services or 3rd Party tool
- Exporting standard application logs that capture errors and aid in troubleshooting and response to operational events.
- Defining threshold of operational metrics to generate alert for any issues
Please provide the following as evidence:
- Standardized documents or guidance on how to develop customer workload health KPIs with the three components above
- Description of how workload health KPIs are implemented in (1) of the submitted customer examples.
-
OPE-002 - Define a customer runbook/playbook to guide operational tasks
Create a runbook to document routine activities and guide issue resolution process with a list of operational tasks and troubleshooting scenarios covered that specifically addresses the KPI metrics defined in OPE-001.
Please provide the following as evidence:
- Standardized documents or runbook met the criteria defined above.
-
OPE-003 - Use consistent processes (e.g. checklist) to assess deployment readiness
Deployments are tested or otherwise validated before being applied to the production environment. For example, DevOps pipelines used for the project for provisioning resources or releasing software and applications.
Use a consistent approach to deploy to customers including:
- A well-defined testing process before launching in production environment
- Automated testing components
Please provide the following as evidence:
- A deployment checklist example or written descriptions met all the criteria defined above.
Security - Networking
Requirements in this category focus on security best practices for Virtual Private Cloud (Amazon VPC) and other network security considerations.
-
NETSEC-001 - Define security best practices for Virtual Private Cloud (Amazon VPC) and other network security considerations.
Establish internal processes regarding how to secure traffic within VPC, including:
- Security Groups to restrict traffic between Internet and Amazon VPC
- Security Groups to restrict traffic within the Amazon VPC
- Network ACL to restrict inbound and outbound traffic
- Other AWS security services to protect network security
Please provide the following as evidence:
- Written descriptions/documents on network security best practices met the criteria defined above.
- Description of how network security is implementation in one (1) of the submitted customer examples.
-
NETSEC-002 - Define data encryption policy for data at rest and in transit
Establish internal processes regarding a data encryption policy used across all customer projects
- Summary of any endpoints exposed to the Internet and how traffic is encrypted
- Summary of processes that make requests to external endpoints over the Internet and how traffic is encrypted
- Enforcing encryption at rest. By default you should enable the native encryption features in an AWS service that stores data unless there is a reason not to.
All cryptographic keys are stored and managed using a dedicated key management solution
Please provide the following as evidence:
- Data encryption and key management policy met the criteria defined above.
- Description of how data encryption is implementation in one (1) of the submitted customer examples.
Reliability
Requirements in this section focus on the ability of the AWS Partner solution to prevent, and quickly recover from failures to meet business and customer demand.
-
REL-001 - Automate Deployment and leverage infrastructure-as-code tools.
Changes to infrastructure are automated for customer implementation
- Tools like AWS CloudFormation, the AWS CLI, or other scripting tools were used for automation.
- Changes to the production environment were not done using the AWS Management Console.
Please provide the following as evidence:
- Written description of deployment automation and an example template (e.g., CloudFormation templates, architecture diagram for CI/CD pipeline) met the criteria defined above.
-
REL-002 - Plan for disaster recovery and recommend Recoverty Time Objective (RTO) and Recoverty Point Objective (RPO).
Incorporate resilience discussion and advise a RTO&PRO target when engaging with customer. Customer acceptance and adoption on RTO/RPO is not required.
- Establish a process to establish workload resilience including:
- RTO & RPO target
- Explanation of the recovery process for the core components of the architecture
- Customer awareness and communication on this topic
Please provide the following as evidence:
- Descriptions or documents on workload resilience guidance met the three criteria defined above
- Description of how resilience is implementation in one (1) of the submitted customer examples including reasons for exception when RTO&RPO is not defined
Cost Optimization
Requirements in this category relate to the AWS Partner's ability to help customers run systems that deliver business value at the lowest price point.
-
COST-001 - Develop total cost of ownership analysis or cost modelling
Determine solution costs using right sizing and right pricing for both technical and business justification.
Conducted TCO analysis or other form of cost modelling to provide the customer with an understanding of the ongoing costs including all the following 3 areas:
- Description of the inputs used to estimate the cost of the solution
- Summary of the estimates or cost model provided to the customer before implementation
- Business value analysis or value stream mapping of AWS solution
Please provide the following as evidence:
- Description of how to develop cost analysis or modeling with the critical components defined above
- Cost analysis example in one (1) of the submitted customer examples. Acceptable evidence types are: price calculator link, reports or presentations on business values analysis
Telecom Customer Example Requirements
The category-specific requirements are only applicable for customer examples submitted for that category.
Mobile Networks Customer Examples
-
MTEXM-001 - Customer Example Engagement Type
AWS Telco Mobile Network Service Partner must indicate one or more of the following service types provided to the customer:
- Build a new solution on AWS,
- Migrate an existing solution to AWS
- Integrate and deploy a solution on AWS
- Manage a solution on AWS
Please provide the following as evidence:
- Description of service type(s) of each of AWS Partner's customer case studies
-
MTEXM-002 - AWS Edge-Region Integration
Mobile Network often consists of AWS services and network functions in AWS Region and Edge. For example, a mobile network may use AWS IAM service and its management plane functions in AWS Region and AWS Outposts and Control Plane and Data Plane functions at AWS Edge. AWS Partner must be experienced in design, integration, deployment, or management of Mobile Network end to end across AWS Region and Edge.
Please provide the following as evidence:
- Mobile Network solution design or service documents involving both AWS Region and Edge end to end.
OSS Customer Examples
-
OSEXM-001 - OSS Example Engagement Type
AWS Telco OSS Service Partner must indicate one or more of the following service types provided to the customer:
- Build a new solution on AWS,
- Migrate an existing solution to AWS
- Integrate and deploy a solution on AWS
- Manage a solution on AWS
Please provide the following as evidence:
- Description of service type(s) of each of AWS Partner's customer case studies.
-
OSEXM-002 - OSS Domain Expertise
AWS Telco Service Partner must provide details of each function in the TMForum TAM Framework listed below per customer case (minimum of 8 for OSS):
- Service Inventory Management
- Service Test Management
- Service Order Management
- Service Problem Management
- Service Quality Management
- Resource Order Management
- Resource Performance Management
- Fault Management
- Resource Inventory Management
- Resource Test Management
- Workforce Management
- Location Management
- Network Number Management (incl. IP Address Management)
- Resource Domain Management
Please provide the following as evidence:
- Reference design documentation from customer examples where the described functions are implemented, migrated, integrated or managed
BSS Customer Examples
-
BSEXM-001 - Customer Example Engagement Type
AWS Telco BSS Service Partner must indicate one or more of the following service types provided to the customer:
- Build a new solution on AWS,
- Migrate an existing solution to AWS
- Integrate and deploy a solution on AWS
- Manage a solution on AWS
Please provide the following as evidence:
- Description of service type(s) of each of AWS Partner's customer case studies.
-
BSEXM-002 - AWS Edge-Region Integration
AWS Telco Service Partner must provide details of each function in the TMForum TAM Framework listed below per customer case (minimum of 6 for BSS):
- Sales and Care Customer Channels
- Customer Order Management
- Service Order Management
- Configure Price Quote
- Product Catalog
- Customer Relationship Management
- Partner Management
- Supplier Management
- Charging
- Billing & Revenue Assurance Please provide the following as evidence:
- Reference design documentation from customer examples where the described functions are implemented, migrated, integrated or managed.
CaaS Customer Examples
-
CSEXM-001 - Customer Example Engagement Type
AWS Telco CaaS Service Partner must indicate one or more of the following service types provided to the customer:
- Build a new solution on AWS,
- Migrate an existing solution to AWS
- Integrate and deploy a solution on AWS
- Manage a solution on AWS
Please provide the following as evidence:
- Description of service type(s) of each of AWS Partner's customer case studies.
-
CSEXM-002 - CaaS Specific Experience
AWS Telco Services Partner must be able to perform implementation, integration, migration or management of solutions in the CaaS domains of (1) Contact Center, (2) Unified Communications, and (3) Communication Platform as a Service. Each customer reference must demonstrate a minimum of three CaaS capabilities in one of the three CaaS domains:
(1) Contact Center * Workforce Management * Call Recording and Analytics * Interactive Voice Response * Automated Call Distribution or Routing * Real-time and Historical Contact Center Reporting * Conversational Bots * Natural Language Understanding or Automated Speech Recognition * AI/ML-based Solution
(2) Unified Communications * Enterprise telephony * Meetings (audio/video/web conferencing) * Unified Messaging * Instant messaging * Mobility * AI/ML-based Solution
(3) Communication Platform as a Service * Short Message Service (SMS) * Email * Push Notifications * Social Media * Outbound Voice * AI/ML-based Solution
Please provide the following as evidence:
- Architecture or services documentation illustrating clearly how the customer reference demonstrates development, migration, integration or management of solutions provide the above capabilities to the Telco customer.
Media & TV Customer Examples
-
MTEXM-001 - Customer Example Engagement Type
AWS Telco Media & TV Service Partner must indicate one or more of the following service types provided to the customer:
- Build a new solution on AWS,
- Migrate an existing solution to AWS
- Integrate and deploy a solution on AWS
- Manage a solution on AWS
Please provide the following as evidence:
- Description of service type(s) of each of AWS Partner's customer case studies.
-
MTEXM-002 - Media & TV Specific Experience -1
The reference example is to be within the video division of the telecom company, such as MVPD, channel aggregation or IPTV, as opposed to the broadband, mobile, enterprise, customer service division. The reference shall include the deployment of software (for update, migration or a new solution), solution integration or end to end solution managed services.
Please provide the following as evidence:
- Architecture or services documentation illustrating clearly how the reference provides specific Media&TV solutions and/or services to the customer, addressing functional areas such as MVPD, channel aggregation or IPTV.
-
MTEXM-003 - Media & TV Specific Experience - 2
The reference customer examples must be focused on at least one of the following:
- Ingest: processing, and/or presentation of metadata associated with live or on demand assets in preparation or as part of delivery to Telco subscribers
- Management of live or on demand assets: for the purpose of telco subscriber consumption including DVR (Digital Video Recording) and personalization solutions for telco subscribers
- Delivery of live or on demand video assets to telco subscribers
- UI (User Interface) / UX (User Experience) for video systems (for example STB (Set Top Box), OTT (Over The Top) applications, Smart TV, Mobile)
- Securing of asset delivery platform including: limiting asset access to authenticated and authorized users only, anti-theft solutions
- Capture and/or presentation of subscriber data related to telco video system performance measurement and analysis
Please provide the following as evidence:
- Architecture or services documentation illustrating clearly how the customer reference demonstrates development, migration, integration or management of solutions provide the above capabilities to the Telco customer.
Resources
- AWS Specialization Program Guide
- Provides step-by-step instructions when applying for an AWS Specialization.
- AWS Specialization Program Benefits Guide
- Provides a deeper description of the program benefits.
- AWS Competency Application Process
- Provides high-level visibility into the AWS Competency application process and timelines for associated process steps.
- AWS Competency & SDP Common Customer Example Requirement Calibration Guide
- Provides control-by-control best practices, resources to implement, good example responses.
- How to build a microsite
- Provides guidance on how to build a microsite to highlight your AWS Specialization.
- How to build a public case study
- Provides guidance on how to build a public customer case study that will showcase your success with AWS Customers.
- How to build an architecture diagram
- Provides guidance on how to build an architecture diagrams that will meet the prerequisites of the Program.
- Well Architected Website
- Learn about the Well Architected Framework and its approach.
- SaaS Best Practices
- Provides best practices on SaaS
- Changes between previous and current versions
- Change Log
- Deployment Pipeline Reference Architecture
- Learn about the stages and actions for different types of pipelines that exist in modern systems.