AWS organization

Account Limits:

AWS Organizations imposes limits on the number of accounts you can have in an organization based on your usage history. Initially, new organizations might be limited to a small number of accounts. If you are a new customer or haven't requested a limit increase, this could be the reason. You can request a limit increase by contacting AWS Support.

2. Root vs. Member Account: Ensure that you are inviting accounts from the master (root) account of the organization. Only the master account can invite other AWS accounts to join the organization.

3. Region-Specific Restrictions:

While AWS Organizations is a global service, ensure that you are operating in the correct region where your organization’s settings and resources are managed. For example, if your organization's region is set to us-east-1, that should be the region you are managing your organization from. 4. Service Control Policies (SCPs): Check if there are any SCPs (Service Control Policies) in place that might restrict your ability to invite new accounts.

5. Pending Invitations: If there are any pending invitations that have not been accepted or declined, you might be unable to send new invitations until the pending ones are resolved.

6. Billing and Payments: Make sure your AWS account's billing and payments are up to date. If there are billing issues, AWS might restrict your ability to manage your organization.

7. Account Trust and Safety: In some cases, AWS might restrict organization activities if there are trust and safety concerns, such as suspicious activity on your account.

8. AWS Support:

If none of the above factors seem to be the issue, contacting AWS Support directly can help resolve the issue. They can provide specific insights into why the invitation process is failing and guide you through the necessary steps to resolve it.