Updated October 21, 2026. The AWS Communication Developer Services (CDS) Agentic AI Partner Hackathon invites eligible AWS Partners to build and deploy AI-powered customer communications on AWS. It has a October 28, 2026 submission deadline, a 40%-weighted technical-execution judging criterion, and a prize structure led by an $18,000 first-place award and a $10,000 WhatsApp bonus sponsored by Meta.

Unlike an open hackathon where anyone can submit a hobby project, this competition has a specific AWS Partner Network (APN) eligibility requirement, requires an actual communications-service invocation in code, and asks for a net-new AWS Customer Engagement (ACE) opportunity ID. These requirements are easy to miss when skimming the prize announcement. This guide unpacks the official rules and separates mandatory criteria from our practical engineering recommendations.

1. Official timeline and essential facts

EventPacific Time (as stated in rules)
Submission period opensSeptember 14, 2026, 6:00 a.m.
Submission deadlineOctober 28, 2026, 1:00 p.m.
Judging startsNovember 6, 2026, 9:00 a.m.
Judging endsNovember 12, 2026, 5:00 p.m.
Winners announcedOn or around November 19, 2026, 6:00 p.m.

The competition is sponsored by Amazon Web Services (AWS) and administered by Devpost. The page may display a visitor's local deadline, such as GMT+1; use the timestamp in the official rules and a date-aware time-zone converter rather than applying a fixed offset to Pacific Time. The rules can be amended, so verify the current closing time before submitting. Entry does not require a purchase, but using AWS services can still generate charges.

2. Who is eligible? The AWS Partner restriction

Eligibility is restricted to adults who are employed by or authorised to act on behalf of an organisation registered with the AWS Partner Network (APN) and bound by the APN Terms & Conditions. Teams must consist of eligible individuals registered with the same AWS Partner. Eligible organisations themselves may also enter.

The registered organisation name and a corporate email address using the domain associated with its APN registration must be supplied during registration. This corporate address does not have to match the email used to log in to Devpost. Teams or organisations need a properly authorised representative responsible for submission and communications.

The official rules also exclude certain locations and conflicts of interest, including organiser-related personnel, judges and associated groups. Geographic exclusions include named locations such as Brazil, Quebec, Russia, Crimea, Cuba, Iran, North Korea and Syria, subject to the full legal wording. A team's eligibility is not established merely because one person has an AWS account. Check the partner registration, the employer's permission and every team member's status before investing in a build.

3. What must the application do?

Entrants must build, develop and deploy a newly created AI solution on AWS for a real-world customer use case and use at least one qualifying AWS Communication Developer Service (CDS). The three qualifying groups are:

  • AWS End User Messaging: SMS and RCS communications.
  • AWS End User Messaging Social: WhatsApp messages.
  • Amazon Simple Email Service (SES): email.

Amazon Bedrock AgentCore is recommended but not required for agentic AI orchestration. Similarly, an AI feature should perform a useful task rather than be a decorative chatbot attached to a messaging template. The rules explicitly note that Amazon Pinpoint reaches end of support on October 30, 2026; builders should avoid designing a new submission around a service being retired.

Important exclusion: AWS End User Messaging Push does not count as qualifying CDS usage. Legacy Pinpoint clients also do not qualify under the repository requirements. Projects must be new work created during the September 14–October 28 submission window, although standard frameworks, libraries, starter templates and AI coding assistants may be used. Any incorporated pre-existing code or work must be disclosed.

4. Runtime calls: importing a package alone is not sufficient

The repository must demonstrate qualifying CDS usage at runtime: the relevant SDK must be imported and actually invoked in an application or backend entry point, or through a loaded agent, workflow or MCP configuration that performs that call. Merely mentioning the service in a README does not meet the rule.

ServiceQualifying examples named in the rules
SMS / RCSPinpoint SMS and Voice v2 SDK client; operations including SendTextMessage, SendMediaMessage, SendRcsMessage, SendVoiceMessage
WhatsAppSocial Messaging SDK client and SendWhatsAppMessage
EmailAmazon SES SDK v1 or v2 (v2 recommended), or SES SMTP

For example, the rules name boto3 clients pinpoint-sms-voice-v2, socialmessaging and sesv2, and JavaScript packages @aws-sdk/client-pinpoint-sms-voice-v2, @aws-sdk/client-socialmessaging and @aws-sdk/client-sesv2. Actual service invocation, account configuration and messaging permissions still matter; a code snippet that creates an SDK client but never sends or performs a qualifying operation is not enough.

One illustrative architecture is:

Customer request / approved event
           |
       Application API
           |
   Authentication and consent
           |
  AI reasoning / classification
           |
   Policy and output validation
           |
 AWS CDS service SDK invocation
 (SES / SMS-RCS / WhatsApp)
           |
    Delivery / status events
           |
  Audit log and human review

This is an editorial design pattern, not an official AWS deployment blueprint. Security, data residency, opt-in and messaging permissions must be evaluated for the selected channel and destination. Keep credentials out of your repository and never use a demo to send unsolicited messages.

5. Three practical project concepts

AI customer-support triage via email

Use SES as the communication channel for a customer-support workflow: receive an authorised customer request through an approved intake mechanism, classify its urgency, propose an answer and have a human confirm before sending a reply through SES. Measure response latency, classification accuracy and cases escalated to an agent. The required SES runtime operation should be visible in the code and demo.

Opt-in WhatsApp service assistant

Use AWS End User Messaging Social for an opt-in customer workflow, such as rescheduling service appointments, requesting an update or routing a complex question to staff. The AI layer handles intent and context; the WhatsApp SDK sends the authorised message. This could also satisfy the additional WhatsApp prize condition if the rules and submission description are fully met, but merely adding a WhatsApp logo would not.

Multichannel customer notifications

Build a consent-aware system that chooses email or SMS/RCS based on user preferences, delivery needs and context. A model could classify the type of update and draft text while deterministic business rules control the channel and approval. Because technical execution is heavily weighted, multiple genuinely integrated CDS services may strengthen the engineering story. They are not required for basic eligibility, however: one qualifying service is sufficient.

All three ideas are suggestions, not officially mandated project themes, and each must be implemented within the new-project rule.

6. AWS credits, Kiro and avoiding surprise bills

Registered teams with a valid idea may request $50 in AWS Promotional Credits per team for a qualifying AWS Partner account while supplies last. The rules do not promise automatic approval: the organisers may restrict credits to entrants who demonstrate a viable idea. These promotional credits expire on October 31, 2026, 11:59 p.m. PT and exclude Kiro.

Eligible individuals may separately request Kiro credits, also while supplies last and subject to approval. Those credits expire October 30, 2026, 11:59 p.m. PT. The amount of Kiro credits is not specified in the provided rules; do not assume it equals $50. Both programmes are subject to AWS Promotional Credit terms.

The rules explicitly make entrants responsible for additional AWS charges. Use account budgets and alerts, set concurrency and rate limits, disable unused resources and remove test infrastructure after judging requirements have been met. A credit balance is not a guarantee that your account cannot be billed.

7. What needs to be submitted on Devpost?

  1. Working deployed project: newly built on AWS, using a qualifying CDS service and an AI-powered customer use case.
  2. Code repository: link to GitHub or GitLab with source, assets and reproducible instructions. Public or private repositories are permitted.
  3. Access for private code: share a private repository with [email protected] and [email protected], as specified in the rules.
  4. Open-source licence if public: the public repository must carry a visible open-source licence. A private repository is not required to be public or automatically open-sourced.
  5. Architecture diagram: show services, data movement, AI components, CDS SDK operations, secrets and trust boundaries.
  6. Project description: explain features, user problem, deployed architecture and the communications workflows.
  7. Demo video: approximately three minutes, hosted publicly on YouTube or Vimeo, showing the actual project working; judges need not watch beyond three minutes.
  8. Deployment URL: provide a deployed application link. A non-web email or WhatsApp agent can instead provide its repository URL and practical interaction instructions, including the address or number judges can use.
  9. Net-new ACE opportunity ID: create an AWS Customer Engagement opportunity in Partner Central on or after September 14, 2026 and record the required campaign code.
  10. WhatsApp prize description: if aiming for the Meta-sponsored award, explain clearly how AWS End User Messaging Social was used.

All submitted materials must be in English, or accompanied by an English translation of the video, description, testing steps and other submission assets. Make the project freely available for evaluation until the judging period ends. Judges may rely on the video and description without testing, so a reproducible demo and clear explanation are both important.

8. The ACE opportunity: a less obvious mandatory step

Unlike many hackathons, this one requires an opportunity ID from Partner Central's AWS Customer Engagement (ACE). The opportunity must be new, created on or after September 14, 2026, and include the exact Marketing Campaign code:

AWS CDS Agentic AI Hackathon -Sept. 2026

Do not leave this until the final submission hour. The official rules refer developers to the event FAQ for detailed opportunity-creation instructions. The field is a stated submission requirement, not an optional marketing bonus. Ask the relevant APN administrator to confirm your team's access to Partner Central and its opportunity workflow early.

9. Judging criteria: why architecture matters so much

Judging begins with a pass/fail eligibility and viability review, including whether the required SDKs and services are genuinely used. Qualifying entries then receive weighted assessment:

CriterionWeightWhat to demonstrate
Technical Execution40%Well-architected, reproducible solution with effective CDS and wider AWS integration
Potential Value / Impact20%A specific customer problem and measurable benefit
Demo Presentation20%End-to-end workflow and clear explanation
Creativity10%Novelty of the problem and approach
Functionality10%Correct service behaviour, scalability and practical AI improvements

The largest share is engineering. Show why services are connected, how failures are handled, how the system can be reproduced and how the CDS operation contributes to customer value. An attractive slide deck cannot substitute for functioning infrastructure.

10. Prize breakdown and important restrictions

AwardPrize
First place$18,000, plus optional AWS Marketplace enablement, go-to-market support and a joint case study
Second place$8,000, plus optional enablement and marketing support
Third place$4,000, plus optional enablement and marketing support
Best WhatsApp Solution (Meta-sponsored)$10,000

A project can win only one prize. The WhatsApp award is not an automatic additional payout for a project that also wins first place. The rules allow the sponsor to withhold an award where no eligible submission qualifies. Winners must complete eligibility and identity verification and provide required paperwork. Taxes, banking and conversion fees can apply, and team representatives are responsible for prize allocation.

11. Practical development plan

The following plan is editorial advice, not an organiser-provided timeline:

  1. First: verify APN eligibility, corporate email, representative authority, ACE opportunity access and the required channel.
  2. Next: make the CDS SDK call from a working test environment. Confirm permissions, identity verification, destination eligibility and rate limits.
  3. Then: add AI reasoning, human review where appropriate, meaningful logs, retries and delivery-status visibility.
  4. After that: deploy, run safe tests using consented recipients and capture measurable results.
  5. Finally: write the README, architecture diagram, description, demo script and ACE details; verify repository access and submit well before the deadline.

For a demo, show a real customer journey: an inbound request or authorised business event, the AI decision, validation, the actual service invocation and the communication outcome. Where external delivery is slow, show an appropriate status and explain it rather than pretending a send operation has succeeded.

12. Compliance and operational safeguards

Communication systems interact with personal data and channels that can be abused. For a strong engineering submission, build consent management, clear opt-out handling where appropriate, message templates, permission checks, secret rotation and audit trails into the design. Assess the applicable AWS messaging policies, WhatsApp requirements and laws before sending real messages. These are practical safeguards; the official rules do not prescribe a single implementation for all customer use cases.

Keep demonstration credentials out of screenshots and public source. For private repositories, share access only as specified for evaluation. If evaluators need to interact with an agent through an email alias or telephone number, provide controlled test access and sufficient instructions without exposing unrelated customers or staff.

13. Intellectual property, publicity and legal terms

The official rules say submissions remain the intellectual property of their creators, while granting the sponsor a non-exclusive licence to use entries for judging. The sponsor and Devpost also obtain promotional rights over submitted projects and contributor names and likenesses for the event period and three years afterward, under the terms described. Existing third-party code or datasets must be used lawfully. The competition is not described as a confidential development arrangement.

Entrants also accept provisions on eligibility, liability, indemnification, disputes and publicity. The rules refer to arbitration under the American Arbitration Association and New York governing law, subject to applicable limitations. This article is informational and does not replace legal advice for a commercial partner project.

14. Mistakes most likely to derail an entry

  • Applying without an eligible APN-registered organisation or matching corporate address.
  • Using Push or a legacy Pinpoint client rather than an eligible CDS operation.
  • Explaining AWS messaging in slides without an actual runtime SDK invocation.
  • Repackaging an existing product without newly developing the submitted project.
  • Forgetting the new ACE opportunity ID and exact marketing campaign code.
  • Providing a private repository but not granting the specified evaluation access.
  • Leaving a public repository without its required open-source licence.
  • Using a video or demo with no functioning end-to-end message workflow.
  • Assuming $50 in cloud credits has been automatically assigned or is a spending cap.
  • Assuming the $10,000 WhatsApp prize can be stacked with an overall award.

15. Final checklist before the deadline

  • APN organisation and eligible team confirmed.
  • Devpost registration completed using corporate partner details.
  • New project built and deployed during the official submission window.
  • One or more qualifying SES, SMS/RCS or WhatsApp operations actually called in code.
  • AI is meaningful to a specific customer use case.
  • GitHub/GitLab repository prepared with code, assets, instructions and proper access/licence.
  • Architecture diagram and English-language project description ready.
  • Public three-minute-ish YouTube/Vimeo demonstration completed.
  • Working deployment or non-web agent interaction instructions provided.
  • ACE opportunity created with the exact campaign code.
  • All fields submitted before October 28, 2026, 1:00 p.m. Pacific Time.

Conclusion

The AWS CDS Agentic AI Partner Hackathon is best approached as a product-engineering challenge for AWS Partners, not a generic AI contest. Its most distinctive requirements are genuine communication-service integration, an AWS deployment, proof of customer impact, and ACE opportunity registration. With technical execution worth 40%, a narrow, demonstrably reliable workflow offers a stronger foundation than an expansive demo that cannot be reproduced.

Read the official rules immediately before submitting: they take precedence over secondary summaries and can change.

Official sources