Initial set up of companies presence within AWS

Question

Hi,

I'm starting out in AWS and looking to 'claim' our companies identity/presence within AWS in a similar fashion to what we have in Azure. I'd like to know how to set up our organisations presence within AWS so that no-one else in the company can do the same and create resources and entities with AWS without our knowledge (effectively block anyone from registering 'ourdomain.com' in AWS

I have registered for a free AWS account using my business email address, then created an 'organization within this 'tenant' - I don't know if this is all is required or I need to do something else. Although it was a long time ago, I have recollection of going through a domain verification process with Azure to prove we were (I think by email and DNS TXT record verification). I'm looking to do the same in AWS, but can't seem to work out how to do it, or if what I've done already is enough.

Steps so far:

Registered for a free account using my business email address
Set up / enabled AWS organization component/feature (this seemed the logical thing to do)

We're not looking to host our domain within AWS, it's already hosted elsewhere or send/receive email via AWS, but rather claim our companies presence within AWS as we have done with Microsoft Azure and Google Cloud.

I'll admit I have asked this question ins a different way a couple of weeks back, but did not get any reply - so i'm asking again to see if I can get anything other than a generic AI response (pointing me in the direction of hosting my domain and registering email services, which I am not attempting to do)

In the future, we aim to host applications, servers and other services, but for now i'm just trying to get a 'foot in the door' for my company so we're ready to go when we need to.

Hopefully this makes sense,

Steve

re:Post Agent · Answer

When you create an AWS account using your business email address and set up an AWS Organization, you've already established your company's presence within AWS. Unlike Azure, AWS doesn't have a specific domain verification process to "claim" your company domain across the entire AWS ecosystem.

Here's what your current setup accomplishes:

1. By creating an AWS account with your business email, you've established the first account that can serve as the management account for your organization.

2. By enabling AWS Organizations, you've created a framework to centrally manage multiple AWS accounts, apply policies, and consolidate billing.

This setup allows you to:
- Create additional member accounts for your organization
- Organize accounts into Organizational Units (OUs) for better management
- Apply Service Control Policies (SCPs) to control what services and actions are allowed
- Centralize billing across all accounts in your organization

To further secure your company's presence and prevent unauthorized AWS usage:

1. Consider enabling AWS IAM Identity Center (formerly AWS Single Sign-On) to manage access centrally
2. Create a well-structured OU hierarchy based on your company's departments or environments
3. Implement SCPs to restrict what services can be used across your organization
4. Set up consolidated billing to monitor costs across all accounts

Unlike Azure's domain verification process, AWS's approach focuses on account management through Organizations rather than domain-level verification. Your current setup provides the foundation for managing your company's AWS presence, and you can expand from there as your needs grow.  
**Sources**  
[Community | Manage Security and Costs Across the Enterprise With AWS Organizations](https://community.aws/tutorials/practical-cloud-guide/manage-security-and-costs-across-the-enterprise-with-aws-organizations)  
[Community | Setting Up the AWS Organization, Identity Center, and the Amazon Q Developer Pro Subscription](https://community.aws/content/2gVkt0Ir5xLHGuhIWhhDycdo260/setting-up-the-aws-organization-identity-center-and-the-amazon-q-developer-pro-subscription)  
[Getting started with AWS Organizations - AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_getting-started.html)

Initial set up of companies presence within AWS

Add your answer

Relevant content