AWS Partner Central business planning: eligibility and permissions

Separate partner eligibility from account access

On 10 November 2026, AWS announced a new Business Plan experience in AWS Partner Central in the AWS Console. It is for AWS Partners actively engaged with AWS Partner management teams. Eligible partners can start plans for growing their AWS business or join plans initiated by AWS teams. The announcement does not say that an AWS account or partner label alone automatically enables the entry.

Keep business eligibility separate from sign-in authorization. Eligibility concerns the partner's relationship with AWS Partner management; AWS Identity and Access Management (IAM) controls user access. Even when an organization fits the announced audience, an administrator may still need to grant the individual user appropriate permissions. Being able to sign in to AWS does not establish that the organization meets the partner-engagement condition.

Business plans support shared partner goals

AWS describes collaboration with partner development, technology, marketing and specialist teams. Participants can work on plan narratives, goals and initiatives, then use real-time goal tracking, attachments and exports to prepare for business reviews. This is a planning workspace; it is not a promise of sales results, program admission or funding.

The announcement also describes AI-assisted plan readiness scores that help partners identify areas to improve. It does not publish the scoring factors, calculation method or thresholds. Treating a score as an approval decision, program acceptance or guaranteed business outcome would go beyond the published information.

AWS also mentions APIs, SDKs and programmatic notifications. The public API Reference Welcome page reviewed here does not specify business-plan request formats, endpoints, SDK versions or notification schemas. Obtain the corresponding business-plan interface documentation before integration; the feature announcement alone does not define how to call it.

A service Region is not a full country-eligibility list

The announcement lists US East (N. Virginia) as the AWS Partner Central service Region. That describes a service location; it does not establish that partners must be US citizens or US-registered businesses, nor does it provide a complete list of eligible countries or territories.

The announcement does not list all participating countries or territories, fees, account-by-account rollout status or a date when every partner account will show the entry. If eligibility depends on a specific partner relationship or location, confirm it with the AWS Partner management team responsible for that relationship. The service Region alone is not enough to decide.

The public IAM guide names four business-plan actions

AWS's access guide says an IAM Administrator provisions user access. It describes CreateBusinessPlan as a ReadWrite action for creating plans and PutBusinessPlan as a ReadWrite action for updating them. ListBusinessPlans supports ListOnly, ReadOnly and ReadWrite; GetBusinessPlan supports ReadOnly and ReadWrite.

For each of these four actions, the public guide says a resource ARN cannot be specified in the Resource element and that Resource: "*" is required. This describes the Resource element for those actions. It does not mean Action: "*" or grant general administrator access, and the guide does not provide a per-plan ARN scope.

These action names and access groups can help an IAM administrator review a policy, but they do not by themselves prove that a particular user has access to the full experience. They are not a universal policy to copy. An authorized IAM administrator should review the identity, roles and assigned policies against the team's responsibilities.

The announcement and admin guide describe different entry behavior

The 10 November announcement says to sign in to AWS Partner Central and choose Business Plan. The current public Partner admin navigation page still says that Business plan redirects to the legacy Partner Central experience. The two public sources differ, so keep that difference visible instead of silently rewriting one to match the other.

That documentation difference does not prove that the new experience failed to launch or that it is enabled for a particular account. No partner account was accessed, no live menu was checked and no Business Plan API was called, so the rollout state for an individual account is unknown.

Make a bounded check with the partner lead and IAM administrator

A partner lead can first confirm whether the organization is actively engaged with AWS Partner management. An authorized IAM administrator can then verify which AWS identity the user signed in with and review the policies and roles assigned to that identity. Compare the announcement with the Partner admin navigation page, and note the page name, access time, service Region and exact error message.

If the difference remains, share page and error context without keys, tokens or other credentials with the AWS team responsible for the partner relationship or an official support channel. Do not treat unpublished scoring criteria, fees, country lists or account rollout dates as known. Changing network egress or creating duplicate accounts cannot establish partner eligibility.