Cloud Account¶
Onboarding your Cloud Accounts¶
To configure your own account, you can grant us a security role through different mechanisms to provision infrastructure on your behalf. If you wish to host on our account, you can skip this step.
Here is how it looks like:
- For AWS, we have a 1-click integration to create your Cloudformation stack. For step-by-step instructions, here is a link to the video
- For GCP, we have a 1-click integration using Cloud Shell to create the security role. For step-by-step instructions, here is a link to the video
- For Azure, we have a 1-click integration using Azure Cloud Shell to create the security role. For step-by-step instructions, here is a link to the video
Note
If you encounter any error due to the already created AWSLoadBalancerControllerIAMPolicy policy in AWS, please select the option to onboard your AWS account without creating that policy
Note
Azure needs in addition to full subscription permissions the ability to bind AD roles. User running the onboarding script needs to have a role such as Privileged Role Administrator allowing binding of AD roles assigned at AD level ('Microsoft Entra ID' service).
Offboarding¶
To offboard a Cloud Account, please follow the steps in order:
- Delete the account config here to clean up all the Omnistrate created artifacts
- Wait for account config to be deleted on the Omnistrate Portal
- For AWS you can delete the CloudFormation used to onboard
- For GCP you can call the offboarding script using CloudShell
- For Azure you can call the offboarding script using CloudShell
For any questions, please reach out to us at support@omnistrate.com