← Back to all announcements
★★★★☆ 16/06/2026

AWS Partner Central agents now accelerate co-selling on every deal

Real-time AI agents now score, enrich, and route every co-sell deal automatically—unlocking AWS field engagement faster than ever.

View original announcement →

Visual Summary

graph TD A{{AWS Partner Central Agents}}:::announced B(Amazon Bedrock AgentCore):::compute C([Opportunity Quality Score]):::feature D([Co-sell Motions]):::feature E([MCP Server]):::feature F((AWS Partners)):::external G((Partner CRM)):::external H(Amazon Q & Kiro):::compute I([Sales Play Generation]):::feature F ==>|"submits deals"| A A -->|"powered by"| B A -->|"calculates"| C C -->|"determines"| D A -->|"exposes tools"| E E -.->|"JSON-RPC/SSE"| G F -->|"converses via"| H H -->|"connects to"| A A -->|"generates"| I classDef announced fill:#ff9900,stroke:#ec7211,color:#fff,font-weight:bold classDef compute fill:#e3f2fd,stroke:#1565c0,color:#1565c0 classDef storage fill:#e8f5e9,stroke:#2e7d32,color:#2e7d32 classDef feature fill:#fff3e0,stroke:#e65100,color:#e65100 classDef external fill:#f5f5f5,stroke:#616161,color:#616161

What's New

AWS Partner Central agents now qualify and enrich every co-sell opportunity in real time, eliminating the manual review bottleneck that previously slowed deal progression. Each opportunity is automatically matched to one of three co-sell motions—AWS field-engaged, Agent-engaged, or Partner-led—based on an Opportunity Quality Score that recalculates dynamically as deal details improve. Partners can interact with the agent conversationally inside Partner Central, through Amazon Q and Kiro, or via an MCP server integrated directly into their own CRM.

How It Works

  • Real-time opportunity qualification: The agent evaluates every submitted co-sell opportunity instantly, scoring it against co-sell readiness criteria rather than queuing it for human review.
  • Opportunity Quality Score (OQS): Each deal receives a numeric score that measures co-sell readiness; this score directly determines which engagement motion AWS applies and recalculates live as the partner enriches the opportunity.
  • Three co-sell motions: AWS field-engaged triggers direct AWS sales team collaboration; Agent-engaged means the agent works to strengthen the submission until it qualifies for field engagement; Partner-led means the partner drives the deal with agent-provided guidance.
  • Conversational opportunity creation and enrichment: Partners can describe a deal in plain language, upload meeting notes or proposals, or clone an existing opportunity; the agent extracts key fields, validates data, and populates the opportunity form automatically.
  • Agentic recommendations: Across all motions the agent surfaces customer insights, tailored sales plays, next-step action plans, funding program eligibility, and solution recommendations grounded in AWS co-sell standards.
  • MCP server integration: A fully managed, AWS-hosted MCP server exposes Partner Central tools over JSON-RPC 2.0/HTTPS with SigV4 authentication and Server-Sent Events (SSE), enabling any MCP-compatible AI client or CRM to interact with opportunity management natively.
  • Human-in-the-loop controls: All write operations (opportunity creation, progression, fund requests) require explicit partner confirmation before execution, preserving control while automating data entry.
  • Powered by Amazon Bedrock AgentCore: The underlying agent infrastructure runs on Amazon Bedrock AgentCore, providing multi-turn conversation support, file attachment analysis, and session management.

Why It's Important

  • Eliminates manual review delays: Previously, co-sell opportunities sat in a queue awaiting human qualification; real-time agent scoring means partners get immediate feedback and can act on deals the same day they are submitted.
  • Directly influences AWS resource allocation: The OQS is not advisory—it determines whether an AWS sales team engages at all, making score improvement a concrete lever for partners to unlock AWS field support.
  • Reduces pipeline hygiene burden: Automated field validation, missing-context detection, and business-problem-statement strengthening improve data quality at submission time rather than after rejection.
  • Shortens sales cycles: Tasks that previously required hours of manual customization—sales play generation, customer profiling, funding evaluation—now complete in minutes through conversation.
  • Meets partners in their existing tools: MCP integration means partner sales teams do not need to context-switch into Partner Central; they can manage co-sell workflows from Salesforce, HubSpot, or any MCP-compatible CRM.
  • Scales expertise across the partner organization: Smaller partners without dedicated AWS alliance managers gain on-demand access to the same co-sell guidance that previously required experienced personnel.

How It's Different

  • Always-on vs. periodic review: Traditional co-sell qualification relied on AWS partner development managers reviewing submissions in batches; the agent qualifies every opportunity instantly and continuously.
  • Dynamic scoring vs. static acceptance/rejection: Rather than a binary pass/fail, the OQS provides a continuous signal that recalculates in real time as the partner improves the opportunity, creating a feedback loop instead of a dead end.
  • Agentic enrichment vs. form completion: Prior tooling required partners to manually fill multi-screen forms; the agent extracts structured data from unstructured inputs like call transcripts and meeting notes.
  • Embedded in native AI tools: Unlike previous Partner Central features that were portal-only, this experience is accessible inside Amazon Q, Kiro, and third-party CRMs via MCP—a first for AWS partner tooling.
  • Motion-based engagement routing: The three-motion framework (field-engaged, agent-engaged, partner-led) is a new construct that makes AWS engagement criteria explicit and actionable rather than opaque.
  • Funding and marketplace integration: The same agent session that manages co-sell can also evaluate funding program eligibility and generate AWS Marketplace product listings, consolidating previously siloed workflows.

When to Prefer It

  • High-volume partner organizations: Partners submitting many opportunities per week benefit most from automated qualification, as the agent removes the per-opportunity manual overhead that previously created bottlenecks.
  • Partners targeting AWS field engagement: When the goal is to get an AWS sales team actively collaborating on a deal, the OQS feedback loop provides a clear, actionable path to meeting the threshold for field-engaged motion.
  • Teams without dedicated alliance managers: Smaller ISVs or regional partners that lack experienced AWS co-sell staff can use the agent as an on-demand expert to generate sales plays, customer profiles, and next-step guidance.
  • CRM-centric sales teams: Organizations that live in Salesforce or other MCP-compatible CRMs should use the MCP server integration to avoid context-switching and keep co-sell activity inside existing workflows.
  • Deals with incomplete or unstructured data: When opportunity details exist in meeting notes, email threads, or proposal documents rather than structured fields, the agent's document-upload and extraction capability is the fastest path to a complete submission.
  • Partners pursuing AWS funding programs: When a deal may qualify for AWS co-sell funding, the agent's ability to evaluate eligibility, estimate amounts, and create fund requests within the same session makes it the preferred workflow over manual program research.

Availability

  • General Availability: The enhanced agentic co-sell experience is generally available as of June 16, 2026; it builds on the initial AWS Partner Central agents release from March 16, 2026.
  • Supported regions: Available to AWS Partners in all commercial AWS Regions globally.
  • Access point: Partners access the feature by logging into AWS Partner Central and navigating to opportunity management; no separate enrollment is required.
  • Native AI tool support: The agentic experience is also available inside Amazon Q and Kiro without additional configuration.
  • MCP server: The Partner Central agents MCP server is a fully managed, AWS-hosted service; partners follow the MCP server guide to connect MCP-compatible clients or CRMs.
  • Pricing: Pricing details are not explicitly stated in the announcement; partners should consult the AWS Partner Central pricing page or their AWS partner agreement for applicable costs.
  • Limitation – write operation approval: All agent-initiated write operations require explicit human confirmation; fully autonomous execution without approval is not supported by design.

Tags

Servicesother-aws
Typenew-featurega-launch
Conceptsagentic-aigenaiconversational-ai
Use Casesenterprisedeveloper-tools
GeographyGlobal

Related Resources

AI Radar AWS

AWS AI/ML news — curated, researched, explained

An automated intelligence platform that curates, researches, and analyzes AWS AI/ML/GenAI announcements daily. Every report is backed by real research — the system reads linked blog posts and documentation to provide accurate, in-depth analysis.

How Each Report Is Generated

  1. Collection — Daily monitoring of the AWS "What's New" RSS feed
  2. Filtering — AI-powered relevance detection for AI/ML/GenAI topics
  3. Taxonomy Tagging — LLM-based classification across 6 dimensions
  4. Importance Scoring — Point-based system with tag bonuses (1-5 stars)
  5. Research Phase — Follows links to blog posts and documentation
  6. Report Generation — Claude Sonnet produces structured 6-section analysis
  7. Visual Summary — Claude Opus generates Mermaid diagrams for key items
  8. Publishing — Static website rebuilt and deployed via CloudFront

Features

  • Faceted filtering by service, type, concept, and more
  • Multi-dimensional taxonomy with 80+ tags across 6 dimensions
  • Geographic availability badges (Global, APJ, EMEA, AMER) with filtering
  • Timeline visualization of announcement volume
  • PDF export for offline reading
  • Mermaid visual summaries for key announcements
  • Daily automated updates — no manual curation
What makes this different: Each report involves a dedicated research phase where the system reads linked blog posts and AWS documentation pages. This produces analysis that goes beyond the original announcement text.

Technology

Built with Python, AWS Lambda, Amazon Bedrock (Claude Sonnet 4.6, Opus 4.6, Haiku 4.5), S3, CloudFront, WAF, EventBridge, and CDK.

Open Source

This project is open source. Fork it, customize it for your needs, and deploy your own instance.
📦 github.com/bbonik/ai-radar-aws

How Importance Scoring Works

Each announcement receives a point score based on multiple factors. The total score maps to a 1-5 star rating:

1★ < 2 pts 2★ ≥ 2 pts 3★ ≥ 3.5 pts 4★ ≥ 5 pts 5★ ≥ 6.5 pts

Point Breakdown

FactorPointsWhen
Core AI service (Bedrock, AgentCore, SageMaker AI)+4Service named in title
Key AI service (SageMaker, Kiro, QuickSight)+2Service named in title
Other AI-related service+1Default
Blog post link+3Link to aws.amazon.com/blogs/
GitHub samples link+2Link to github.com/aws*
Documentation link+1Link to docs.aws.amazon.com/
New model+1.5Tagged as "new-model"
New service+1Tagged as "new-service"
New feature+0.5Tagged as "new-feature"
Anthropic / OpenAI provider+2Provider explicitly mentioned
Instance / notebook announcement-2Hardware/capacity, not feature
Performance / pricing / security-0.5Incremental updates
Region expansion to APJ+1Expands to Asia Pacific
Region expansion (non-APJ only)-1.5Only expands to other regions

Geographic Relevance Badges

Each announcement card shows a small badge indicating whether the feature is available in your region:

🌐 Global Available in all regions
🌏 APJ Asia Pacific
🌍 EMEA Europe / Middle East / Africa
🌎 AMER Americas (US, Canada, South America)
No badge Geography unknown
How geography is detected: The system detects ALL geographies mentioned in each announcement. If the text mentions specific regions (Tokyo, Frankfurt, Oregon, etc.), the corresponding geography badges are shown. If it says "all regions" or is a new feature with no region specified, it gets the Global badge. Geography is also filterable — click a geo chip to see only announcements available in that region.