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

Required permissions for onboarding¶

Permissions required to execute account onboarding vary depending on the cloud provider.

AWS¶

User executing the CloudFormation stack needs to have AdministratorAccess on the AWS account.

GCP¶

User executing the Cloud Shell script needs to have roles/owner on the GCP project.

Azure¶

User executing the Cloud Shell script needs to either be an Owner on the Azure subscription, or have the following roles: - User Access Administrator - Application Administrator

In addition, there are permissions required on the Azure AD level: - Privileged Role Administrator

Common Issues During Account Onboarding¶

AWS Load Balancer Controller Policy Already Exists¶

Problem: AWS accounts sometimes have the AWS Load Balancer Controller Policy already installed, which can result in CloudFormation stack errors due to duplicate policy creation attempts.

Solution: When onboarding your AWS account, if you encounter errors related to the AWS Load Balancer Controller Policy already existing, you need to configure the CloudFormation parameter to skip the policy installation.

During the AWS account onboarding process:

1. Set the CloudFormation parameter for AWS Load Balancer Controller Policy creation to false
2. This will skip the installation of the policy and avoid the duplicate resource error
3. The existing policy in your account will be used instead

Cloud Account already used in different Environment¶

Problem: You used a cloud account to one Omnistrate Organization and later attempted to add it to a different Omnistrate Organization, which resulted an error message.

Solution: This is expected behavior. The same cloud account can be used across different environments (dev, staging, prod) within the same organization, but cannot be used across different organizations. This is a security feature to prevent account conflicts and ensure proper isolation between organizations.

If you need to use the same cloud account across different organizations, you'll need to:

1. Remove the account from the first organization
2. Wait for the removal to complete
3. Add it to the second organization

Offboarding¶

When you no longer need a cloud account connected to Omnistrate, you can offboard it to remove all Omnistrate-managed resources and revoke access. The offboarding process is automated and handles cleanup of infrastructure artifacts that were created during onboarding.

Before you offboard¶

Before initiating the offboarding process:

1. Delete all deployment instances running in the cloud account. Active instances must be removed before offboarding can proceed.

Offboarding steps¶

Follow these steps to offboard a cloud account:

1. Navigate to System Settings > Cloud Accounts in the Omnistrate Console.
2. Locate the cloud account you want to offboard.
3. Click Delete on the account configuration.
4. Wait for the account configuration deletion to complete. Omnistrate automatically cleans up all platform-managed artifacts (deployment cells, control plane components, and networking resources) in the account.
5. After the account configuration is deleted, remove the onboarding artifacts from your cloud provider:

AWS¶

Delete the CloudFormation stack that was created during onboarding:

1. Open the AWS CloudFormation Console.
2. Locate the Omnistrate onboarding stack.
3. Select the stack and choose Delete.
4. Wait for the stack deletion to complete.

GCP¶

Run the offboarding script using Cloud Shell:

1. Open Google Cloud Shell.
2. Run the offboarding script provided during the onboarding process to remove the service account and IAM bindings.

Azure¶

Run the offboarding script using Azure Cloud Shell:

1. Open Azure Cloud Shell.
2. Run the offboarding script provided during the onboarding process to remove the service principal, role assignments, and related resources.

What offboarding cleans up¶

When you delete the account configuration, Omnistrate automatically removes all deployment cells and their underlying infrastructure (control plane, networking, and system components).

For any questions about the offboarding process, reach out to support@omnistrate.com.