Why do I receive the error "You can only join an organization whose Seller of Record is same as your account" when I'm trying to join an organization?

2 minute read
0

When I try to join an AWS Organization, I receive the error "You can only join an organization whose Seller of Record is same as your account." What does this error mean?

Resolution

This error indicates that your seller of record or AWS partition is not the same as the management account in the AWS Organization.

The seller of record refers to whether your account is with Amazon Web Services, Inc. (AWS Inc.), Amazon Web Services EMEA SARL (AWS Europe), Amazon Web Services India Private Limited (AWS India), or another seller of record. Due to billing constraints, AWS India accounts can't be in the same organization as accounts with other AWS sellers of record.

An AWS partition is a group of Regions. The AWS supported partitions are AWS Regions, AWS China Regions, and AWS GovCloud (US) Regions. Due to legal and billing constraints, you can join an organization only if it's in the same partition as your account. Accounts in the AWS Regions partition can't be in an organization with accounts from the AWS China Regions partition or AWS GovCloud (US) Regions partition.

For example, in an AWS Europe organization, you can have both an AWS Inc. and an Amazon Web Services Canada, Inc. (AWS Canada) account.

If you're not sure the seller of record that your account is with, see Determining which company your account is with.

If you're not sure the seller of record that the management account of the organization is with, contact the owner of the management account. To see the contact details of the management account:

  1. Sign in to the AWS Management Console.
  2. On the navigation bar, choose your account name, and then choose My Organization.

Related information

Why can't I join an organization in AWS Organizations?

AWS GovCloud (US) compared to standard AWS Regions

AWS OFFICIAL
AWS OFFICIALUpdated 2 years ago
4 Comments

There is no resolution given, only explanation. Then, how to resolve?

edwin
replied 6 months ago

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

profile pictureAWS
MODERATOR
replied 6 months ago

Echoing the comment that this is an excellent description of the problem, but there is no discussion of how to resolve the issue.

replied 2 months ago

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

profile pictureAWS
MODERATOR
replied 2 months ago