WorkMail Organization Alias Conflict

The conflict you're experiencing is likely due to the similarity in the URL structure between your AWS Organization's custom access portal URL and the WorkMail organization URL you're trying to create. However, these are separate systems and cannot share the same alias.

1. Yes, the conflict is most likely caused by your previously created AWS Organization with the custom AWS access portal URL (myorg.awsapps.com/start). The WorkMail system is trying to create a similar URL structure (myorg.awsapps.com/mail) and is detecting a conflict.

2. Unfortunately, you cannot reuse organizations or aliases between AWS Organizations and Amazon WorkMail. These are separate services with distinct purposes. AWS Organizations is for managing multiple AWS accounts, while WorkMail is an email and calendaring service. They use similar URL structures but operate independently.

3. The reason for not allowing reuse of aliases across these services is to maintain separation and avoid confusion. Each service needs its unique identifier within the AWS ecosystem to ensure proper routing and access control.

4. For a sensible alias, you could consider using a variation of your organization name or add a prefix/suffix to make it unique. For example, if your organization is "myorg", you could try:

   • myorg-mail
   • mail-myorg
   • myorgmail
   • myorg-wm (for WorkMail)

Remember, the alias must be between 1 and 62 characters long, can contain letters, numbers, and hyphens, but cannot start with a number or "d-".

When creating your WorkMail organization, you'll need to choose a unique alias that doesn't conflict with your existing AWS Organization or any other WorkMail organization. This will ensure a smooth setup process for your email service while maintaining the separate identity of your AWS Organization.

Sources
CreateOrganization - Amazon WorkMail
OrganizationSummary - Amazon WorkMail