AWS account is Critical after enabling an Account using the aws_accounts API

Products

• CloudHealth

Issue/Introduction

This can occur if an account is configured within CloudHealth immediately after it was first provisioned on the AWS side. 

In some cases AWS has not yet completed the backend configuration and the initial API call from CloudHealth is rejected by AWS.

Resolution

To prevent this occurring, it's recommended to introduce a wait/sleep period of several minutes to any scripting/automation of AWS > CHT account provisioning via APIs.