E'lon
Calling all AWS Partners! We are inviting you to build the next wave of conversational solutions on AWS Communication Developer Services (CDS)! AWS CDS enables AWS Partners to help customers engage users at a global scale through AWS End User Messaging (EUM) which includes Rich Communication Services (RCS), Short Message Services (SMS), and WhatsApp. It also includes Amazon Simple Email Service (SES). AWS CDS is the infrastructure that powers messaging across
Amazon.com
, Amazon Cognito, SNS, and Amazon Connect.
AWS CDS is often used for one-time passwords (OTP), notifications, and rules-based chatbots that follow rigid scripts. We challenge you to think beyond this. The future of customer engagement is conversational: reaching customers in the channel (i.e. email vs. RCS vs. WhatsApp) they prefer, picking up right where the last conversation left off, and using two-way communication so customers tell you directly what they want and share signals that improve your products and services.
Picture omnichannel experiences where a conversation starts in one channel and completes an action in another: a prescription refill reminder via SMS that lets the patient find and schedule the nearest pharmacy pickup through RCS with a tap, then sends dosage instructions via email, all without leaving the messaging experience.
Push the boundaries. Build agentic solutions where AWS CDS is the communications backbone, powered by AI such as Amazon Bedrock AgentCore.
Surprise us with your real cu
Talablar va baholash
Requirements
What to Build
Entrants must build, develop, and deploy an AI solution on AWS to address a real-world customer use-case that uses
at least one
AWS Communication Developer Service (CDS) (each a “Project”):
AWS End User Messaging (EUM) that includes Rich Communication Services (RCS) and Short Message Service (SMS)
AWS End User Messaging Social (WhatsApp)
Amazon Simple Email Service (SES)
Recommended but not required
: Incorporate Amazon Bedrock AgentCore to combine for an agentic AI powered solution
.
AWS End User Messaging Push does not count as CDS usage for eligibility.
Functionality:
The Project must be capable of being successfully installed and running consistently on the platform for which it is intended and must function as depicted in the video and/or expressed in the text description.
We will provide $50 in AWS Credits (1 per team) on a first come, first serve basis to support build cost.
We will also provide
Kiro
access codes
for participants (1 per individual) on a first come, first serve basis to support build cost. Refer to the
FAQ page
for code request form.
What to Submit
Include a Project built with the required developer tools and meets the above Project Requirements.
URL to your private or public code repository
for judging and testing on either GitHub or GitLab.
It must contain all source code, assets, and instructions needed for the project to run, and must demonstrate the use of AWS Communication Developer Services at runtime in your code.
The repository may be public or private. If the repository is public, the repository must be open source by including an open source license file. This license should be detectable and visible at the top of the repository page (in the About section). If the repository is private, share it with
[email protected]
and
[email protected]
.
More information provided in this
GitHub README
.
A
rchitecture Diagram
T
ext description.
~3- minute d
emonstration video of your Project.
URL to your deployed project or instructions on how to interact with it, if not a web application.
Create
d opportunity ID through
AWS Partner Central’s AWS Customer Engagement (ACE)
. It
must include the Marketing Campaign code "
AWS CDS Agentic AI Hackathon -Sept. 2026.
" See
FAQ page
on how to create an opportunity in ACE.
To be considered for the Meta WhatsApp Prize:
Description of how AWS End User Messaging Social (WhatsApp) was used
See
Full Rules
for Details
Judging Criteria
Potential Value/Impact - 20%
What customer problem/process is it solving/improving?
What (measurable) impact does it have?
Creativity - 10%
Novelty of problem
Novelty of approach
Technical Execution - 40%
Must use the technology/technologies mentioned in the What to Build section.
Is the solution well-architected?
Is it reproducible?
Are there multiple AWS CDS services utilized, and well integrated into broader AWS services, specific AI services?
Functionality - 10%
Are the AWS CDS services and other AWS services working as expected?
Is the solution scalable?
Is the solution leveraging AI to improve existing processes or experiences?
Demo Presentation - 20%
Does it include the end-to-end agentic workflow?
How is the demo quality and clarity?