Anomaly Detection
Perks
Powered By GitBook
Invite Existing AWS Account
Adding existing AWS accounts to DoiT International consolidated billing
You can add existing AWS accounts to DoiT International's consolidated billing using the Cloud Management Platform.
Required Permission: Licenses Manager
Please note that you must be assigned access to the specific Billing Profile under which the domain is managed in order to invite an existing account.
Start with you logging into the Cloud Management Platform, and select the 'Invite AWS Account' from the menu on the left-hand side of the page and clicking on Assets.
A screenshot showing the location of the Invite AWS Account menu item
Once you're at the Assets page, go to the right-hand side of the page and click on 'Invite Account'.
A screenshot showing the location of the Invite Account option
Choose the Billing Profile to which you'd like to have the existing AWS account now be a part of. Enter the 12-digit AWS Account ID and any optional notes before clicking 'Invite'.
A screenshot of the Invite Existing Account form
An email will be sent on behalf of AWS.
A screenshot of an example email from AWS
If within five minutes you haven't received the above email, please re-enter your AWS Account ID in the DoiT Cloud Management Platform and invite once again.
To complete the process, sign in to the AWS Organizations Console. On the Invitations page in the console, you can see your open invitations to join organizations. Finally, click the "Accept" button to accept the invitation.
A screenshot of the AWS Invitations page
Afterward, you will be redirected to the Organization overview page with details about the organization that your account is now a member of. You can view the organization's ID and the owner's email address.

Multiple Accounts Under a Master Organization

In the event that you have multiple accounts under a Master account / organization, you will get an error trying to accept the invitation.
In order to successfully accept the invitation, you must remove each linked AWS account from your master account.
Note: This will prompt you to input payment details for each linked account if you didn't do so while initially creating them.
For each account you must:
    1.
    "Leave" the Organization (no new invites will appear before you do this)
    2.
    Accept the invite from DoiT International in each linked account

Completing IAM Access for CloudHealth

After signing in to the AWS Console and accepting the invitation, a final email will be sent instructing how to complete the IAM access for CloudHealth.
A screenshot of an example email sent by DoiT

Frequently asked questions

I’ve performed all the requested steps, I have spends on my AWS billing account, but my information is still not there. What could be the reason ?

Once successfully completed it takes 24-72 hours for the data to start flowing through from AWS, then our Cloud Management Platform will update.

I have not received any invitation email. What could have gone wrong?

On your organization's page, check if you can see the invite:
Invite on your AWS Organizations page
If you can't see that invite, check if you have left your organization as specified in the above "Multiple Accounts Under a Master Organization" steps.
If you can see the invite on the organization's page, consider the following:
Is the invite in your spam folder? Did you enter the correct AWS account id when inviting the account?
If you are still having issues, you can open a support ticket.

My CloudHealth status shows as "critical" or "unknown", what does it mean?

My payer account is showing as N/A, what does that mean?

"CloudHealth Status: Unknown"
It means that your Cloudhealth configuration was not done properly.
Actions to take: please open a support ticket if you see the CloudHealth status as "critical" or "unknown", or if you see Payer Account: N/A.
The consequences are the following:
    Our Cloud Management Platform is not able to properly reflect your reservation data, and you cannot use the FlexRI and Spot0 services.
    It also means you will not be able to run reports on this asset, the reason being that the data is not flowing to our platform.\
Last modified 6d ago