Skip to content
Guide

How to submit an ACE opportunity in AWS Partner Central, step by step

Logging a partner-originated opportunity tells AWS about a deal you found and, if you ask, brings an AWS seller in to help. This guide walks through a first submission in AWS Partner Central, from setup to the review statuses and the API calls behind it.

9 min readUpdated By the HabileLabs CoSell team

A partner-originated opportunity is a deal you found and share with AWS through the APN Customer Engagements (ACE) program. You create it in AWS Partner Central, attach what you sell, and submit it for AWS review. This guide follows AWS documentation as of November 2026. Once it is submitted, Action Required explained covers what to do when AWS asks for changes.

Before you start

  1. A Partner Central account linked to an AWS account. Since 30 November 2025 Partner Central runs inside the AWS Management Console. You sign in to the AWS account tied to your Partner Central account and open Partner Central from there. Partners still on the older portal move over with a migration feature in that portal.
  2. ACE terms accepted. Whoever registered your company in Partner Central agreed to the APN Customer Engagements terms.
  3. Permissions. Access is managed in IAM. AWS recommends the AWSPartnerCentralOpportunityManagement managed policy for people who register and work opportunities, and AWSPartnerCentralFullAccess for alliance leads. Developers building an integration start with AWSPartnerCentralSandboxFullAccess.
  4. Something to attach. Every opportunity needs at least one partner solution or AWS Marketplace product in Limited or Public status. Create one before your first opportunity.
  5. A deal that is ready. AWS takes opportunities at Qualified or later, with a target close date in the future. Don't submit a deal that has already launched or closed.

The fields AWS asks for

Open Sell, then Opportunities, and choose Create opportunity. Create using wizard opens a multi-step form: customer details, project details, APN programs, deal size, optional details and customer contacts, then a review. Create using agent lets AWS's Partner Central agent draft the opportunity from a description or uploaded meeting notes; you check its fields before you approve. In the API the same data sits in Customer, Project, LifeCycle and Marketing, with solutions attached separately.

GroupFieldsWhat AWS requires
Customer (Customer.Account)Company name, website, industry, country, postal code, address, DUNSEverything except DUNS is required in the console. A Government customer also needs the national security answer (NationalSecurity).
Project (Project)Title, customer business problem, use case, delivery model, sales activities, opportunity typeThe business problem takes 20 to 2,000 characters. Pick a real use case and industry rather than Other, so AWS can route the deal.
Help from AWSCo-Sell with AWS, partner-specific needs (PrimaryNeedsFromAws)Choose at least one need if you ask to co-sell.
SolutionPartner solution, AWS Marketplace solution, AWS Marketplace productAt least one. Up to 10 solutions and 10 Marketplace products.
Spend (Project.ExpectedCustomerSpend)Expected monthly AWS spendMonthly, in US dollars or euros (euros only in the AWS European Sovereign Cloud). The deal size step can work it out from total contract value or an AWS Pricing Calculator link.
Timing (LifeCycle)Stage, target close date, next stepsThe close date must be in the future. Next steps take up to 255 characters.
Marketing (Marketing)Sourced from marketing activity, campaign, channels, marketing funds usedIf the deal came from a marketing activity, say whether AWS marketing funds paid for it.
ContactsCustomer contact, up to two partner contactsOptional. Partner contacts receive AWS's notifications about the opportunity.

Fields with a fixed list, such as industry, use case, delivery model and sales activities, accept only AWS's own values. If your CRM picklists use other wording, map them before you submit.

CoSell has also seen AWS refuse a submission that lacked a delivery model, sales activities or a customer use case, and refuse a US customer with no state. Treat those as required.

Write a customer business problem AWS can act on

AWS scores every submitted opportunity out of 100, and the completeness of the customer business problem is the main driver of that Opportunity Quality score. AWS's guidance asks you to describe the customer, not your product. Cover:

  • what is broken or slow today, what it costs, and at what scale;
  • why the customer has to act now, and by when;
  • who approves the budget and who champions the project;
  • how the customer will choose, and the alternative, even if it is doing nothing;
  • how the deal will be contracted: through AWS Marketplace, directly or through a reseller;
  • dated milestones for evaluation, decision and signature.

Leave out text reused across customers, descriptions of your product, the AWS services your own product runs on, and anything the customer told you in confidence. The field is locked once AWS approves the opportunity, so get it right before you submit.

A short example:

A 40-clinic dental group books appointments on an on-premises system that fails during Monday peaks, losing about 300 bookings a week. Its server-room lease ends in March, so it must move by then. The COO owns the budget and the IT lead champions the project. They are comparing our scheduling platform on AWS with renewing the current system, judged on uptime at peak and migration time. Contracting through an AWS Marketplace private offer, decision by 15 January. Next step: joint architecture review with their IT lead on 2 December.

Choose the stage

Pick the stage that is true today, using AWS's definitions:

StageWhat it means
ProspectAn opportunity has been identified. Mature it to Qualified before you submit.
QualifiedYou have engaged the customer, who agrees the need is real. The earliest stage AWS accepts.
Technical ValidationEveryone understands the implementation plan, often after a proof of concept.
Business ValidationPricing has been proposed and all parties agree the steps to close.
CommittedThe customer has signed, but AWS billing has not started.
LaunchedThe workload is live and AWS billing has started.
Closed LostThe deal is lost and there are no steps forward.

CoSell has seen AWS refuse a stage change while an opportunity is still a draft, so set the stage before you create it.

Submit for AWS review, or keep it as a draft

An opportunity you create starts as a draft with the review status Pending Submission. You can edit it freely, and AWS does nothing with it until you submit. A lead converted with Create draft opportunity also stays a draft until you choose Submit.

When you submit, you choose how much AWS is involved:

  • Co-Sell (InvolvementType set to Co-Sell). You want deal help from AWS sellers. In the console this is the Co-Sell with AWS option, and it needs at least one partner-specific need.
  • For Visibility Only (For Visibility Only). AWS sees the opportunity, but you won't get deal assistance.

A second setting, Visibility, controls how much AWS sales can see: Full, the default, or Limited.

As of November 2026, AWS's own advice is to ask for seller engagement only when a specific seller action would change the outcome. Name the action, such as Technical Consultation, Architectural Validation, Pricing Assistance or Business Presentation. AWS says Deal Support on its own does not count as a specific need.

What happens after you submit

AWS validates the opportunity, and its review status moves through these values:

  1. Submitted: waiting for AWS. You can't edit it.
  2. In review: AWS is validating it. You can't edit it.
  3. Action Required: AWS needs more information. The alliance lead and the opportunity contacts get an email, and the review comments say what to fix. Only some fields open up, including the address, website, target close date, expected spend, business problem and your CRM identifier. Fix them and submit again.
  4. Approved: the opportunity is in the AWS seller's pipeline. You can keep editing, except the title, the customer's country, postal code, industry and website, the business problem and your CRM identifier.
  5. Rejected: disqualified and read-only.

Since 16 June 2026 AWS also gives every submitted opportunity a co-sell motion along with its quality score. In the AWS Field-engaged motion an AWS sales team is matched to the opportunity, and your updates pass through an AWS review step. In the Agent-engaged and Partner-led motions, AWS's Partner Central agents support the deal and your updates are accepted straight away. The motion also depends on how strategically important AWS judges the opportunity to be.

Keep it current until it closes

  1. Update next steps at every stage change. Name a specific action, an owner, a customer contact and a date. AWS uses next steps in the quality score.
  2. Move the stage with Change Stage on the opportunity page once it is Approved.
  3. Attach a solution before Committed or Launched. Since 1 July 2026 an opportunity needs an AWS Marketplace solution, AWS Marketplace product or partner solution attached before it can move to either stage.
  4. At Launched, update the close date, add the customer's AWS account ID if you have it, and set the stage. CoSell has seen AWS lock the stage once an opportunity has launched.
  5. If the deal is lost, move it to Closed Lost with a reason from AWS's list, such as Price, Partner Gap or No Opportunity, and update the close date.

If the AWS seller closes the deal in AWS's own CRM, the Additional details tab shows AWS Stage, AWS Close Date and AWS Closed/Lost Reason. They don't change your own fields.

The same steps through the API

  1. CreateOpportunity creates the draft from Customer, Project, LifeCycle and Marketing, with a unique ClientToken. Use Catalog set to Sandbox for testing and AWS for real deals. In the AWS catalog, Origin must be Partner Referral.
  2. AssociateOpportunity attaches what you sell, with RelatedEntityType set to AwsMarketplaceSolutions, AwsMarketplaceProducts or Solutions. AWS says the legacy Solutions type, with its S- IDs, will be deprecated. You can also attach up to 20 AwsProducts.
  3. StartEngagementFromOpportunityTask submits it, with AwsSubmission holding InvolvementType and Visibility. The task creates the engagement and its snapshot, then calls SubmitOpportunity, which takes the same two settings if you call it yourself.
  4. Watch for Opportunity Updated events in Amazon EventBridge, then call GetOpportunity to read LifeCycle.ReviewStatus and LifeCycle.ReviewComments.
  5. Change it with UpdateOpportunity. Any field you omit is set to null, so start from GetOpportunity, send the whole record, and include LastModifiedDate so you don't overwrite a change made in Partner Central meanwhile.

Where CoSell fits

CoSell watches the deals in your CRM (Salesforce, HubSpot, Microsoft Dynamics 365, Zoho CRM, LeadSquared or CoSell's built-in CRM), and a deal that reaches your gate stage becomes an ACE opportunity. Before anything goes to AWS, CoSell checks the deal against AWS's rules and lists what is missing. It attaches your solutions, submits the opportunity and writes AWS's answer, including the review status and comments, back to the deal. CoSell runs hosted by HabileLabs or in your own AWS account, from USD 10 a month on AWS Marketplace; the offer is currently for AWS accounts in India. See features and pricing.

Sources

More guides

All guides

Available in AWS Marketplace

Try CoSell free for 30 days

Start the free trial on AWS Marketplace with your AWS account. Your workspace is ready in minutes, and you connect your CRM yourself.