Why Most Partners Stall at Select
Getting to AWS Select is the easy part. AWS designed it that way. The requirements are achievable, the documentation is clear, and AWS actively wants partners to reach Select because it signals a baseline level of commitment to the ecosystem.
Advanced is a different conversation entirely. The partners who stall, and most do, often for 12 to 24 months, are not failing because they lack the technology or the customers. They are stalling because they are treating the path to Advanced the same way they treated Select: as a checklist exercise.
It is not. Advanced tier is AWS signaling that it trusts you as a co-sell partner. Every requirement is designed to answer one question: is this partner ready to show up in front of our customers and represent us?
The partners who advance fastest are not necessarily the ones with the most certifications. They are the ones whose PDM is actively vouching for them internally, and that relationship is built deliberately, not passively.
The Advanced Tier Requirements, Explained
The AWS Partner Network updates its program requirements periodically, so always verify the current thresholds in your Partner Central portal. That said, the core categories have been stable for years and are unlikely to change significantly. Here is what you are working toward:
| Requirement Area | What AWS Looks For | Common Gap |
|---|---|---|
| AWS Certifications | Minimum number of active, validated certifications across your team | Certifications lapse or are held by people who have left the company |
| Customer References | Validated customer success stories showing real AWS deployments | Partners have customers but have not submitted them through the formal validation process |
| Annual Revenue | AWS-attributed revenue above the Advanced threshold | Revenue exists but is not being properly attributed through ACE or the Partner Portal |
| ACE Pipeline Activity | Active, healthy opportunity pipeline with consistent submission cadence | ACE is treated as an afterthought: submissions are sporadic and opportunities are stale |
| Training Completion | Partner-level training paths completed by your team | Training is started but not completed, or not logged to the correct PO |
The single most common reason we see partners fail to advance is not a hard requirement: it is revenue attribution. They have the customers, they have the AWS usage, but none of it is flowing through ACE in a way that AWS can credit to their partner account. Fix your attribution before you do anything else.
The Four Gaps That Block Advancement
After working through this process with dozens of partners, the blockers almost always come back to four things. None of them are technical. All of them are operational.
Gap 1: Invisible Revenue
You have customers using AWS. Your products run on AWS. But if that activity is not being submitted through ACE, with the opportunity properly linked to your AWS partner account and ideally co-owned with a field rep, AWS cannot credit it to you. This is the most fixable and most overlooked gap in the program. Start here.
Gap 2: Stale or Thin Customer References
AWS requires validated customer references, not just customer names. The validation process involves AWS reaching out to confirm the engagement. Many partners have satisfied customers who have not been submitted, or they have submitted customers whose engagements are too thin: a proof-of-concept that never went to production, for example. AWS wants to see substantive, ongoing AWS usage.
Gap 3: Certification Drift
AWS certifications expire. Team members leave. New hires join with different credential profiles. What was a clean certification count six months ago can silently fall below the Advanced threshold without anyone noticing. You need a living tracker, not a one-time count, that monitors expiration dates and maps credentials to headcount.
Gap 4: A PDM Who Does Not Know You
This one is not in the requirements document, but it matters more than most partners realize. Your Partner Development Manager reviews and approves tier advancement. If your PDM does not have context on who you are, what you are building with AWS, and why you deserve Advanced, your application goes in cold. Partners who advance quickly have almost always been in regular contact with their PDM for at least two quarters before applying.
Building the PDM Relationship That Accelerates Advancement
Your PDM is the single most important person in your AWS partner journey, and most partners treat them like a support ticket queue.
PDMs are overextended. A typical PDM manages 50 to 150 partners. They cannot proactively support everyone: they triage. The partners who get attention are the ones who make it easy: clear updates, active ACE pipelines, concrete asks, and a demonstrated understanding of how the co-sell motion works.
Here is what a good PDM engagement cadence looks like:
- Monthly email update: one paragraph on pipeline activity, one on any certifications or training completed, one ask or question. Keep it under 200 words.
- Quarterly call: 30 minutes, agenda sent in advance. Cover your ACE pipeline, any funding you have applied for, and your tier advancement timeline. Come with specific questions.
- Event touchpoints: if you are attending re:Invent or a regional AWS Summit, let your PDM know and try to get a face-to-face meeting. These carry disproportionate weight.
Do not wait until you are applying for Advanced to start building the PDM relationship. By then it is too late. The relationship needs to be warm before the application goes in.
Getting Your ACE Pipeline Right
ACE, the AWS Customer Engagements tool, is how AWS tracks your co-sell activity, validates your revenue attribution, and evaluates whether you are a partner worth investing in. It is also the thing most partners manage worst.
A healthy ACE pipeline for Advanced tier consideration means:
- Active opportunities being submitted regularly, not in batches at quarter end
- Opportunities with accurate stage, close date, ARR, and customer detail
- A meaningful percentage of opportunities that are co-owned with AWS (meaning a field rep has accepted the opportunity)
- Opportunities that progress through stages rather than sitting stale at the same status for months
- Win/loss data being captured: AWS uses close rates to evaluate co-sell quality
Partners often submit a batch of opportunities right before applying for Advanced tier. AWS can see your submission history. A sudden spike after months of inactivity does not look like program maturity: it looks like gaming the system. Build the habit over time.
The 90-Day Advancement Plan
If you are at Select and want to reach Advanced, here is the sequencing that works. This assumes you have a reasonable foundation: some certifications, some AWS customers, some ACE activity, and need to close the gaps systematically.
Days 1 to 14: Audit Your Current Standing
Pull your current partner scorecard from Partner Central. Document your exact position on every Advanced requirement: certifications (count, holders, expiration dates), customer references (submitted vs. eligible), revenue attribution, ACE pipeline health, and training completion. Do not guess: get the actual numbers.
Days 14 to 30: Fix Revenue Attribution
Identify every active customer where AWS is in the stack. For each one, check whether there is an ACE opportunity that captures that revenue. If not, create it. Work with your sales team to back-populate existing wins that should be in ACE but are not. This alone often moves the needle significantly on your attributed revenue count.
Days 30 to 45: Submit Customer References
Identify your three strongest AWS customer engagements: production workloads, meaningful ARR, willing to be contacted by AWS. Submit them through the customer reference process in Partner Central. Do not wait for this: it takes time for references to be validated, and you want them cleared before you apply.
Days 45 to 60: Close Certification Gaps
Based on your audit, identify which certifications you need and who on your team is best positioned to get them. Prioritize certifications that serve double duty: ones that count toward Advanced requirements and also toward any specializations you are targeting. Schedule exams, not study sessions.
Days 60 to 75: Engage Your PDM
Schedule a call with your PDM and share your advancement timeline. Do not ask permission: tell them what you are doing and ask for their input on anything that might be holding you back from their perspective. Ask directly: "Is there anything you would want to see before we apply for Advanced?" This conversation surfaces issues you cannot see from the portal.
Days 75 to 90: Apply and Follow Up
Once your scorecard is clean, submit your application through Partner Central. Notify your PDM that the application is in. Follow up within two weeks if you have not heard back. If you are rejected, ask your PDM specifically what needs to change: the feedback is almost always actionable.
What Changes When You Reach Advanced
Reaching Advanced tier is not just a badge. It changes what is available to you inside the AWS ecosystem in material ways:
- PDM access improves. Advanced partners typically get more PDM attention and a more senior contact. The relationship becomes more strategic.
- Funding eligibility expands. Many MAP, MDF, and co-investment programs have higher funding limits or exclusive availability for Advanced and Premier partners.
- Co-sell priority increases. AWS field reps are more willing to bring Advanced partners into deals. The tier signals credibility to people who do not know you.
- Marketplace and Specialization paths open up. Some Marketplace programs and AWS Competencies require Advanced tier as a baseline.
- Competitive differentiation sharpens. When a prospect is evaluating two partners, the one with Advanced tier has an edge: it is visible, it is third-party validated, and it signals investment in the AWS relationship.
Advanced tier is a platform, not a destination. The partners who get the most out of it are the ones who immediately start working toward the next thing: a Specialization, a Marketplace motion, or Premier tier, rather than treating it as the finish line.
The Bottom Line
Advancing from Select to Advanced is not complicated, but it requires discipline and it requires someone actively managing the process. The partners who stall are not missing something exotic: they are missing consistent execution on the fundamentals: clean ACE pipeline, validated customer references, current certifications, and an engaged PDM relationship.
If you are tired of sitting at Select and want a clear path forward, reach out to us. We have run this process for dozens of partners and know exactly where the leverage is.