AWS ACE (APN Customer Engagements): The Complete 2026 Guide for ISVs

If you sell software through the AWS Partner Network and you’re not living inside ACE every week, you’re leaving co-sell revenue on the table. That’s the blunt version. The longer version is what follows: what ACE actually is in 2026, who can use it, how the flow really works (not how the slideware says it works), where deals die, and how to run it without burning out your alliances lead.

This is written for ISV partner managers, alliance leads, and RevOps folks who own the AWS relationship. If you’re already fluent in ACE, skip to the failure modes.

What ACE actually is

ACE — APN Customer Engagements — is AWS’s deal registration and co-sell system for partners. It lives inside AWS Partner Central. Two jobs, one portal:

1. Deal registration. You tell AWS about an opportunity you’re working. AWS validates it, and if it’s real and net-new to them (or a legitimate expansion), you get credit toward Partner Program requirements, funding programs, and tier progression.
2. Co-sell. AWS routes qualified opportunities to the right AWS field seller (an ISV PDM, an account SA, an account executive, depending on the customer segment). From that point, you and the AWS rep are supposed to work the deal together — share updates, share the customer, close together.

The mental model that trips people up: ACE is not a CRM. It’s a ledger between you and AWS about who is working what, and it’s the source of truth AWS uses to decide whether your deals count. Treat it like accounting, not like Salesforce.

Who can use it

ACE eligibility keys off APN tier. As of 2026:

• Registered and Select tier partners can submit opportunities, but co-sell routing is limited. Select is the practical floor for meaningful co-sell — below Select, expect submissions but not much AWS-seller engagement.
• Advanced and Premier partners get full co-sell — opportunities are routed to AWS field reps, you get an assigned PDM (Partner Development Manager), and you’re eligible for the ISV Accelerate program if you’re software.
• ISV Accelerate members get the strongest treatment: AWS sellers are incentivized to co-sell your product because it retires their quota. This is the tier where ACE stops being a chore and starts being a growth channel.

You also need Partner Central users with the right ACE roles assigned — ACE Manager (can edit anything, manage users), ACE User (can create and update their own opportunities), and ACE Viewer (read-only). Get this permissioning wrong on day one and you’ll spend a quarter untangling ownership.

The flow, honestly

Here’s what actually happens end to end.

1. You submit an opportunity. Minimum fields: customer legal name, customer website, opportunity name, target close date, estimated AWS MRR or ARR, use case, next step, and — critically — the opportunity type. More on types below.

2. AWS validates. A validator (human, sometimes assisted) checks that the customer exists, that the opportunity looks real, that it’s not a duplicate of something AWS is already tracking, and that you’ve supplied enough detail to route it. Validation typically takes 5–10 business days. In practice: 2 days if you’re clean, 3 weeks if there’s a queue or your submission is thin.

3. Status moves to Approved. Now AWS decides whether to co-sell. If yes, the opportunity gets Launched (i.e., accepted into co-sell) and assigned to an AWS rep. If no, it stays Approved but not co-sold — you still get registration credit if it’s sourced by you.

4. Working the deal. You and the AWS rep are supposed to update ACE as the deal progresses — new contacts, milestone changes, close date slips, technical validation done, procurement started. AWS also updates from their side (their POV of the customer, their internal blockers).

5. Closed Won or Closed Lost. You report the final ACV, contract start date, and AWS revenue impact. Closed Won opportunities are what count toward tier requirements, ISV Accelerate metrics, and any co-sell incentive payouts.

That’s the theory. Now the reality.

The three opportunity types, and why partners screw them up

Every ACE opportunity has an origin, and this determines who gets credit and who’s on the hook to drive it:

• Partner Originated (Sourced). You found the deal. AWS wasn’t tracking this customer for this workload. You bring it, AWS helps close it. This is the highest-value type for you — it’s what most ISV Accelerate incentives are keyed to, and it’s what AWS PDMs will fight for you to get.
• AWS Originated. AWS found the deal and brought you in — usually because the customer asked for your product, or an AWS SA recommended you. Great for pipeline, weaker on incentives, and AWS drives the timeline.
• Co-Sell / Influenced (IP Co-Sell). You’re working it, AWS is working it, neither can cleanly claim they sourced it. This is where most fights happen. If you had a POC running before AWS engaged, argue Sourced. If AWS was already deep in and pulled you in for the ISV layer, it’s honestly AWS Originated.

The “Sourced vs. Influenced” distinction is the single most common cause of partner-vs-AWS friction. Rule of thumb: if you can produce dated evidence (email, meeting notes, POC start date) that you were working the customer before the ACE submission date and before any AWS seller touched it, submit as Sourced. Attach the evidence in the notes field. Do not wait for the AWS validator to ask.

Common failure modes

After watching hundreds of ISVs run ACE, the same five failures show up over and over.

1. Rejected for insufficient info. The #1 reason. You submitted a customer name, a $50K guess, and “cloud migration” as the use case. Validators bounce it. Fix: write the use case like an AWS SA would — name the services (EKS, RDS Aurora, Bedrock, whatever), name the business problem, name the next concrete step with a date. Two-sentence use cases get rejected. Six-sentence use cases with services named get approved.

2. Ghost opportunities. You submit, it gets Launched, an AWS rep is assigned — and then nothing for six weeks. The rep changed roles, or is at re:Invent, or the customer went cold on their side. Fix: put a 14-day review cadence on every Launched opportunity. If your assigned rep hasn’t updated in 14 days, escalate to your PDM. If you don’t have a PDM, escalate to the ISV Success team via the Partner Central case system. AWS reps respond to nudges; they do not respond to silence.

3. Duplicate rejection. You submit a customer, and it comes back rejected because “an existing opportunity is already registered.” Sometimes that’s another partner (you’re locked out). Sometimes it’s AWS’s own direct pipeline (you can request to be attached). Fix: before submitting a big deal, ask your PDM to check the account for existing registrations. Ten minutes of prevention beats a formal dispute.

4. Sourced/Influenced downgrades. You submit as Sourced, AWS validator downgrades to Influenced, and now the deal doesn’t count toward your Accelerate incentives. Fix: as above — evidence in the notes field at submission time, not after the downgrade.

5. Close-out drift. Deal closes, and nobody updates ACE for two months. You miss the close date attestation window, and the deal doesn’t count toward your tier metrics for the quarter. Fix: tie ACE closeout to your own CRM’s Closed Won stage. If it can’t close in your CRM without ACE being updated, it will get updated.

The operational problem nobody talks about

Every ISV running ACE at any scale hits the same wall: ACE, your CRM, and your partner team’s spreadsheets are three different sources of truth, and they drift.

Your AE closes a deal in Salesforce. Nobody tells the partner manager. ACE never gets updated. Or your PDM emails you an update from the AWS side, you type it into a Notion doc, and it never makes it back to Salesforce so your AE walks into the customer meeting blind about what AWS just committed.

Manually, this is a full-time job at 20+ active opportunities. At 100+, it’s impossible.

Where Recordbook fits

Recordbook is built for exactly this problem. We sync ACE bidirectionally with your CRM (Salesforce, HubSpot, or your own system) and with your internal partner records, so:

• Opportunities created in your CRM with an AWS-relevant tag get proposed as ACE submissions, pre-filled with the fields AWS validators actually want.
• Stage changes, close date shifts, and ACV updates flow both directions — your CRM to ACE and ACE to your CRM — without a human retyping.
• AWS-side updates (new AWS contacts added, status changes, validator notes) surface in the same view your AEs already work in.
• You get an audit trail per opportunity — who submitted, when it was Launched, every Sourced/Influenced call — so quarterly business reviews with your PDM take an hour instead of a week.

You still own the strategic calls — whether to submit, how to argue Sourced, when to escalate. Recordbook removes the data-janitor work between them.

The 2026 punchline

ACE is the operating system for AWS co-sell. If you’re an ISV serious about the AWS channel, treat it like production infrastructure: staffed, monitored, and instrumented. The partners who win at AWS in 2026 are not the ones with the flashiest listing on Marketplace. They’re the ones whose ACE hygiene is boring, disciplined, and boringly disciplined every single week.

Get the submissions clean, get the origin right, escalate the ghosts on day 14, and don’t let your CRM and ACE drift. That’s the whole game.