The AWS Partner Network tier structure looks straightforward on paper. Registered, Select, Advanced, Premier. Each tier has a published requirements list. Partners read the list, check the boxes, and wait for the badge. Then they wonder why AWS sellers are not engaging and why the next tier seems further away than when they started. I spent over a decade inside this ecosystem, carrying a $28M annual partner quota and working with partners at every stage of the APN. The tier progression looks like a compliance exercise from the outside. It is actually a market signal exercise, and most partners execute it wrong.

The AWS Partner Path Structure

The APN organizes partners into a path based on type: Technology partners (ISVs building on AWS) and Services partners (consulting, systems integration, managed services). Each path has its own tier requirements, but the underlying logic is the same across both.

The four partner tiers are:

  • Registered: Entry-level status. Access to the partner portal and training resources. No formal co-sell support, no MDF eligibility, no AWS seller engagement at scale.
  • Select: The first meaningful tier. Requires FTR completion (Technology partners), a minimum number of certifications, and demonstrated customer success through launched opportunities in ACE. Select partners gain access to MDF, limited co-sell support, and partner program discounts.
  • Advanced: A significant step up. Requires additional certifications, more launched opportunities, validated customer references, and active engagement with an AWS PDM. Advanced partners receive higher MDF allocations, priority co-sell support, access to Partner-Originated opportunities, and eligibility for AWS competency designations that open additional market access.
  • Premier: The highest tier. Reserved for partners with deep specialization, verified customer success at scale, and strong measured AWS revenue contribution. Premier partners have dedicated AWS executive sponsorship, expanded MDF, and priority placement in major enterprise co-sell engagements.

The Technology (ISV) path weighs ARR growth, FTR completion, and ISV Accelerate enrollment rather than headcount certifications alone.

What Actually Moves You Up

Partners get stuck at Select for years. They pass the FTR, get the certifications, and nothing changes. The reason is almost always that the inputs AWS actually weights are not being generated at volume.

Launched Opportunities in ACE

Every tier review looks at launched opportunities: deals co-sold with AWS involvement that reached a closed or active state. This is the most important single metric, and it is the one most partners have the thinnest record on. We see Select tier partners with two or three launched deals after 18 months. To reach Advanced, you need a consistent quarterly cadence of launched deals with meaningful AWS consumption attached. If your co-sell motion is not generating that, tier advancement will not come regardless of how many certifications you hold.

AWS Certifications

Certifications are table stakes, not differentiators. Every tier requires a minimum certification count, with specific requirements around practitioner, associate, professional, and specialty credentials. The mistake is front-loading certifications to meet the minimum and then stopping. AWS weights the depth and mix, not just the count. Partners actively adding specialty certifications in security, machine learning, or data analytics signal technical depth that a generalist count does not.

Certifications also support competency applications, which are among the most powerful tier velocity tools in the APN. A competency designation in a relevant domain, security, government, financial services, healthcare, accelerates AWS seller engagement and opens co-sell doors that generic tier status does not.

Customer References and Validated Success

Customer references are required at Select and more rigorous at Advanced. Many partners delay the reference form process until it becomes a bottleneck in their tier review. References that map to AWS priority areas, generative AI, migrations, data and analytics, security, carry more weight than commodity workload references. If you are doing the work anyway, make sure your references are optimally positioned.

Active PDM Engagement

Above Select tier, your AWS PDM is the internal advocate who can accelerate or stall your tier review. Partners who bring qualified pipeline, close the loop on deals, and show up in joint activities advance faster. The PDM has discretion in how they represent your partnership internally. Give them real evidence to work with.

The Funding That Unlocks at Each Stage

Tier advancement is not just a badge. It is a funding eligibility event. Partners who do not understand what unlocks at each stage are leaving real money on the table.

Select Tier: MDF Entry Point

At Select, partners become eligible for Market Development Funds. MDF is co-investment from AWS in partner-led demand generation: events, content, digital campaigns, and similar programs. The allocation is limited, but it is real and it is claimable. The claim process requires a pre-approval request, activity execution, and proof of performance. Partners who do not run this process quarterly leave eligible funds unclaimed, and we see this consistently.

Advanced Tier: POA, Competency Investment, and Expanded MDF

Advanced partners gain access to Partner-Originated Arrangements, creating a structured path to bring net-new opportunities to AWS with defined economics. MDF allocations increase, and competency designations open additional AWS program investment including joint marketing support and Marketplace listing support.

EDP, the Enterprise Discount Program, also becomes relevant at Advanced tier. Partners who bring customers into EDP arrangements through co-sell gain credibility with AWS account teams and create stickier customer relationships.

Premier Tier: Full Stack Investment

At Premier, the investment profile looks materially different. Dedicated executive sponsorship, priority placement in AWS partner finder tools, expanded joint marketing funding, and early access to new AWS services for pre-GA testing are all available. This is where the partner relationship starts to look like a genuine joint go-to-market rather than a vendor-channel dynamic.

Checking Boxes vs. Building Real Tier Velocity

The key distinction is between managing tier requirements and building tier velocity. Managing requirements means executing toward the checklist. Velocity means generating the underlying outputs, launched pipeline, customer references, certification depth, active co-sell engagement, so that advancement becomes a byproduct of real program performance.

The difference comes down to three things: an active co-sell motion with real pipeline, a deliberate certification strategy tied to competency goals, and a customer success capture process that produces references on a regular cadence. All three require sustained operational discipline that most partner organizations do not have staffed correctly.

The Common Mistakes

After running this motion for over a decade and watching hundreds of partner organizations navigate the APN, the failure patterns are predictable.

  • Chasing tier for vanity, not strategy. Partners who want the Advanced badge without building the capacity to operate at that tier end up with a designation they cannot sustain. Tier maintenance has the same requirements as tier attainment. If you hit the threshold through a burst of activity and normalize at a lower output, you will lose the tier at renewal.
  • Ignoring certification and reference requirements until they become blockers. Both have lead times. Certifications require training and exam prep. Customer references require customer cooperation and sometimes legal review. Partners who treat these as 60-day sprint activities before a tier review end up delaying advancement by a full cycle. They need to be rolling programs.
  • Leaving funding on the table. MDF, co-sell investment, competency launch support, EDP influence: these are real dollars that reduce your effective cost of customer acquisition. Partners who do not actively manage the claims and opportunity cycles miss the window. AWS fund cycles do not roll over.
  • Not positioning competencies as a tier accelerant. Competency designations are the fastest legitimate path to AWS seller attention above Select tier. Partners who earn a competency in a high-priority domain get routed into co-sell conversations that standard tier status does not generate. That work should run in parallel with your tier advancement plan, not sequentially after it.

What a Functioning Tier Strategy Looks Like

The partners who advance consistently treat tier strategy as a quarterly business review item, not an annual compliance event. They review ACE pipeline health, certification roster, MDF cycle status, and reference pipeline at the same cadence they review revenue. They set advancement milestones with clear owners and track them the same way they track sales targets.

If your tier advancement has stalled, if you are not sure what funding you are eligible for at your current tier, or if you want a roadmap from Select to Advanced to Premier grounded in what actually moves the needle, book a discovery call. This is the work we do, and we bring the inside perspective to do it right.