Setup Integrations

This guide details integrating AWS accounts with a CloudFormation stack and Azure subscriptions by creating a read-only Service Principal, enabling centralized management and visibility of your cloud resources.

AWS

1. Login to AWS CLI Ensure the AWS CLI is installed and configured with administrative privileges.

2. Prepare AWS Accounts

   If you prefer to perform these steps manually, click here.

   curl -fsSL https://raw.githubusercontent.com/opengovern/integration-automation/main/scripts/configure-aws-organization-accounts.sh | bash

3. Enter Credentials in Opengovernance

   • Go to Integrations -> AWS -> Add AWS Account.

   • Enter the following details in the wizard: AccessKeyID, SecretAccessKey -IAM Role Name: OpenGovernanceReadOnly

   Lease ExternalID and Role in Main Account blank.

Azure

1. Login to Azure CLI Ensure the AWS CLI is installed and configured with administrative privileges.

2. Prepare AWS Accounts

   If you prefer to perform these steps manually, click here.

   curl -fsSL https://raw.githubusercontent.com/opengovern/integration-automation/main/scripts/configure-azure-subscriptions.sh | bash

3. Enter Credentials in Opengovernance

   • Go to Integrations -> Azure -> Add Azure Subscriptions

   • Enter the following details in the wizard: Tenant ID, Application (Client) ID, Object ID, Client Secret

EntraID

DigitalOcean

In the left menu, click API, which takes you to the Applications & API page on the Tokens tab. In the Personal access tokens section, click the Generate New Token button. Scopes: Read Only grants the token read scope for all resources available based on the permissions of your team role.

GitHub

CIn the upper-right corner of any page on GitHub, click your profile photo, then click Settings.

1. In the left sidebar, click Developer settings.

2. In the left sidebar, under Personal access tokens, click Tokens (classic).

3. Select Generate new token, then click Generate new token (classic).

   1. Give this the following permission: notifications, read:audit_log, read:discussion, read:enterprise, read:gpg_key, read:org, read:packages, read:project, read:public_key, read:repo_hook, read:ssh_signing_key, read:user, repo, user:email
4. After selecting the above, click on "Generate Token"

5. Copy the Token and load in the OpenComply app [If you have SSO turned on for Organization, you will need to explicitly authorize the token as in the image below]