Skip to content

Claim my companies identity within my AWS account/instance

-1

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. Although it was a long time ago, I have recollection of going through a verification process with Azure to prove we weer who we wer pertaining to be (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. The idea is that no-one else can 'pretend' to be us and we are the only users who can build/utilise stuff within the companies name/identity.

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)

I'd like to know if those couple of steps stops anyone else doing the same within our company, as I've already registered with my company address, or if there's extra steps to carry out so that no-one else within our company can do the same without our knowledge.

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

Hopefully this makes sense,

Steve

asked 10 months ago165 views
2 Answers
0

To establish your company's identity within AWS, the steps you've taken so far are a good start, but there are additional considerations for fully "claiming" your company's presence.

When you created your AWS account using your business email address, AWS sent a verification email to confirm you own that email address. This is part of the initial verification process.

Setting up AWS Organizations is indeed a logical step as it allows you to centrally manage multiple AWS accounts. However, this alone doesn't prevent others in your company from creating separate AWS accounts using different business email addresses.

To more comprehensively establish your company's identity in AWS and prevent unauthorized use of your company name, you should consider:

  1. Verifying your domain in Amazon SES (Simple Email Service). This involves adding a TXT record to your domain's DNS settings to prove ownership of the domain. This is similar to the DNS verification you mentioned doing in Azure.

  2. For email receiving capabilities through AWS, you would need to configure MX records to point to Amazon SES.

  3. If you want to consolidate AWS usage across your company, you should establish a formal AWS account structure using AWS Organizations, and create a policy requiring all AWS usage to go through this official structure.

  4. Consider implementing AWS IAM Identity Center (formerly AWS SSO) to connect your existing identity source to AWS, which would provide a centralized way to manage access.

These steps will help establish your company's presence in AWS and create a more controlled environment for AWS usage within your organization.
Sources
SES identity question | AWS re:Post
Creating and verifying identities in Amazon SES - Amazon Simple Email Service
Email address verification with AWS Organizations - AWS Organizations
Trusted identity propagation overview - AWS IAM Identity Center

answered 10 months ago
0

Having been away for a week and not seeing any responses, i'm unsure if where I posted this question is the right place or if I've explained correctly what we're trying to achieve. I have however received one down vote, but with no reply or indication as to why.

Is the AI generated response correct? Do I need to provide more context? Or am I simply trying to achieve something which is not possible?

Any help would be greatly appreciated.

Steve

answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.