Case study content requirements

When you create a case study in AWS Partner Central, AWS automatically validates the content against AWS marketing guidelines within minutes of submission. If the content does not meet a requirement, the case study status changes to Action required and the validation feedback identifies what to fix.

Review the following requirements before you submit. Each requirement lists what to avoid, correct and incorrect examples, and the error message that appears when the requirement is not met. These examples help your case study pass validation on the first try.

You can also ask the Partner Central Agent (Amazon Q) to help you understand any validation feedback and identify which requirement a flagged item relates to.

Throughout the following examples, replace bracketed placeholders such as [Customer Name], [Partner Name], and [Full Name] with your own details.

Tell the full challenge story

State the customer's business challenge in detail and describe how you helped address it. Include the specific business problem, why it mattered, and how your solution addressed it with measurable impact. Avoid vague statements such as "they had some issues" or "it went well." Add concrete details about the problem and your solution.

Correct

"[Customer Name] wanted to transform how it delivers managed print services to clients while removing the burden of on-premises print servers. Reliance on manual, per-client print server management led to delayed provisioning, inconsistent delivery, and rising operational costs that constrained growth. [Partner Name] developed a standard reference architecture that could be consistently delivered across the client base, removing the on-premises burden."

Incorrect

"[Customer Name] had some processing issues it wanted to fix."

Error message

"Your case study does not clearly explain the customer's business challenge and how your solution helped. Update it to include the specific problem, how your company solved it, and the impact on the customer."

Avoid unsubstantiated superlatives

Do not use superlatives or absolutes to claim that your product or company is superior without evidence. Watch for the following terms: best, first, only, leader, leading, always, every, exclusive, never, #1, and world's most. The same word is acceptable when you use it factually to describe scope, sequence, or a measured outcome rather than as a superiority claim.

Correct

• "All calls can now be categorized automatically."

• "Every record is encrypted."

• "Reduced errors to 12%, below the 15% target."

Incorrect

• "The best platform."

• "The only provider that never fails."

• "Industry-leading and unmatched."

• "The first and only solution of its kind."

Error message

"Remove or add third-party substantiation for any absolute or superlative claim before resubmitting."

Don't use fear, uncertainty, and doubt language

Avoid fear, uncertainty, and doubt (FUD) language, such as the security terms exploit, attack, breach, or hacker.

Correct

"Its 24/7 services are designed to help customers safeguard their facilities and comply with strict regulatory requirements about who can enter and under what circumstances."

Incorrect

"Before the project, hackers could exploit the system and a major breach was only one attack away."

Error message

"Remove Fear, Uncertainty, and Doubt (FUD) security language such as exploit, attack, breach, or hacker before resubmitting."

Spell out Amazon Web Services (AWS) on first mention

On its first appearance in the document, spell out the company brand as Amazon Web Services (AWS). After that, you can use the short form AWS freely. Full product and service names such as Amazon S3 or AWS Lambda are always acceptable.

Correct

"[Partner Name] wanted to modernize its data platform on Amazon Web Services (AWS). AWS gave the team the elasticity it needed to absorb seasonal demand."

Incorrect

Using the bare token "AWS" or "Amazon" as a company reference before "Amazon Web Services (AWS)" has appeared anywhere in the document.

Error message

"Spell out Amazon Web Services (AWS) on first mention, use AWS thereafter, and never use Amazon alone to refer to AWS before resubmitting."

Use approved language for your AWS relationship

Describe the relationship using approved terms such as AWS Partner, work with AWS, or collaboration. Do not use partnership, strategic alliance, strategic, alliance, agent, jointly, teamed with, acting on behalf of, or in cooperation with.

Correct

"As an AWS Advanced Tier Services Partner, [Partner Name] used AWS-native tools for security and scalability and secured partner-only funding, reducing project costs and accelerating delivery."

Incorrect

"Through its strategic partnership and alliance with AWS, [Partner Name] jointly delivered the solution while acting on behalf of AWS in the region."

Error message

"Describe the AWS relationship using approved terms such as AWS Partner, Work with AWS, or Collaboration, and remove terms like partnership or alliance before resubmitting."

Use approved language to describe AWS

When referring to AWS as a whole, use cloud provider, AWS, AWS Cloud, or AWS services. Do not describe AWS itself as an architecture, environment, infrastructure, gateway, ecosystem, platform, cloud platform, or AWS hybrid. These words are acceptable inside an AWS service name (for example, Amazon API Gateway) or when describing your own solution.

Correct

"Our solution built on AWS capabilities to ensure data sovereignty and compliance, providing a clear, auditable trail of data locality and access."

Incorrect

"[Partner Name] built the solution on the AWS platform, migrating the customer's infrastructure and environment into the AWS ecosystem."

Error message

"Refer to AWS using approved terms such as cloud provider, AWS, AWS Cloud, or AWS services, and remove terms like platform or infrastructure before resubmitting."

Describe solutions as running "on AWS," not "in AWS"

Describe where the solution runs as running on AWS, powered by AWS, or building on AWS. Do not use in AWS, runs in AWS, or in the AWS Cloud.

Correct

"The platform runs on AWS and scales automatically to absorb seasonal demand."

Incorrect

• "The platform runs in AWS."

• "Deployed entirely in AWS."

• "Hosted in the AWS Cloud."

Error message

"Describe the solution as running on AWS, powered by AWS, or building on AWS, and remove phrasings like in AWS or runs in AWS before resubmitting."

Do not use "private cloud" or "public cloud"

Use hybrid architecture or on-premises environments instead of private cloud or public cloud.

Correct

"The company had long relied on an on-premises server to support its day-to-day business systems."

Incorrect

"[Customer Name] migrated from its private cloud to the public cloud."

Error message

"Replace the terms private cloud and public cloud with hybrid architecture or on-premises environments before resubmitting."

Follow job-title capitalization rules

In the body narrative (paragraphs and prose), write job titles in sentence case. In attribution lines, bylines, and quote signatures, write job titles in title case.

Correct

• Body: "[Full Name] is the head of security at [Customer Name]."

• Attribution: "[Full Name], Cyber Cloud Managed Services Leader, [Partner Name]."

Incorrect

• Body: "[Full Name], the Chief Technology Officer, led the project."

• Attribution: "[Full Name], chief technology officer, [Customer Name]."

Error message

"Write job titles in the body narrative in sentence case before resubmitting."

Do not include personally identifiable information (PII)

Do not include contact information (email, phone, or physical address), account numbers, usernames, user IDs, or IP addresses of real people. An attributed pull quote with a person's name, job title, and company is the approved quote format.

Correct

An approved pull quote attributed to "[Full Name], Software Development Lead, [Customer Name]."

Incorrect

"For details, contact project lead [Full Name] at [email] or [phone], account number [number]."

Error message

"Remove personally identifiable information of real people beyond the approved public quote attribution before resubmitting."

Do not make market-share claims

Do not make claims about market, market share, market segment share, or market position. The terms "go-to-market" and "going to market" are acceptable.

Correct

"With [Customer Name]'s annual growth rate of 20%, the focus was on identifying and managing the right AWS solutions to reliably support and grow with the company."

Incorrect

"[Customer Name] captured the largest market share in its market segment within a year."

Error message

"Remove market-share or market-position claims before resubmitting; go-to-market phrasing is acceptable."

Do not name other public-cloud providers

Do not mention another public-cloud provider's name or logo.

Correct

"GPU-enabled Amazon EC2 G5 instances support real-time inference, while Amazon EKS orchestrates microservices for detection, enrichment, and automated response at scale."

Incorrect

"[Customer Name] migrated its workloads off another public cloud provider onto AWS," naming that provider directly.

Error message

"Remove the names and logos of other public-cloud providers before resubmitting."

Name AWS and Amazon services correctly

Name services correctly and carry the Amazon or AWS prefix on first mention. For services where the prefixed short form is the product name (for example, AWS Lambda, Amazon Bedrock, or Amazon EKS), that short form is acceptable on first mention. When you use a long form, use the official expansion. For the official list of AWS service names, see the AWS Cloud Products page.

Correct

"GPU-enabled Amazon EC2 G5 instances support real-time inference, while Amazon EKS orchestrates microservices at scale. The team also used AWS Lambda and Amazon Bedrock."

Incorrect

• "Bedrock" or "Lambda" with no prefix.

• Incorrect capitalization such as "dynamoDB."

• Invented expansions such as "Amazon Elastic Container Service for Kubernetes (EKS)."

• Unofficial abbreviations such as "DDB."

Error message

"Use correct service names with the full name plus short name in parentheses on first use and keep the Amazon or AWS prefix before resubmitting."