Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

The article instructs on adding explains how to add cloud accounts to Cloudaware using APIs. Cloudaware uses the OAuth standard to identify users who send requests to Cloudaware API. A current user should get a specific token to add or see accounts, depending on their permissions.

Table of Contents

Get OAuth token


1. Log in to your Cloudaware account → Admin.

...

Expand
titleIP Relaxation Tip

8.1. Log in to your Cloudaware account → Setup:

adding cloud accounts - setup.png

8.2. Type Apps in the Search bar → Connected Apps → Manage Connected Apps → click on the Cloudaware OAuth2 app:

adding cloud accounts - oauth - connected apps - select the app.png

Click Edit Policies:

adding aws accs - oauth - the app - edit policies.pngImage Removedadding cloud accounts - oauth - the app - edit policies.pngImage Added

8.3. Select 'Relax IP restrictions' in 'IP Relaxation':

adding cloud accounts - oauth - the app - relax ip restrictions.png

Click Save.

Get API key


The API key is required for performing requests to Cloudaware API.


1. Create a Google Cloud Project account.


2. Submit an access request to support@cloudaware.com providing the full e-mail of the associated Google Cloud Project account.


3. Activate access to Cloudaware API using API Manager. Go to https://console.cloud.google.com → open a navigation menu (hamburger button) → select 'APIs & Services' in the menu on the left.

...

Select 'Library' → filter by Private.

...


4. Select external.endpoints.cloudaware-vm.cloud.goog Enable.

...

5. Go back to 'APIs & Services' → Credentials → Create credentials → API Key.

...

6. Copy the API Key to the clipboard:

...

Setup in API Explorer


The Google APIs Explorer allows customers to explore and test APIs. Below is an example of adding AWS accounts to Cloudaware using public APIs:

...

WHERE
token - insert the OAuth token generated before. Select fields in ‘Request body’ to make it look like below:

sandbox - select ‘true’ 'true' if your Salesforce org is a sandbox, otherwise select ‘false’'false'

Request body - select properties successively as role, trustedAccount, accountId, externalId, usages, name

...

5. Click Authorize and Execute. 

List of APIs

external.amazon.accounts.create
external.amazon.accounts.list
external.amazon.accounts.remove
external.amazon.accounts.update
external.applications.batch.upsert
external.applications.list
external.applications.remove
external.applications.tiers.remove
external.azure.activeDirectories.create
external.azure.activeDirectories.list
external.azure.activeDirectories.remove
external.azure.activeDirectories.update
external.azure.applications.list
external.azure.applications.remove
external.azure.applications.update
external.azure.subscriptions.create
external.azure.subscriptions.list
external.azure.subscriptions.remove
external.azure.subscriptions.update
external.compliance.policies.executeTests
external.compliance.policies.generate
external.compliance.schema.list
external.compliance.types.filter
external.compliance.types.get
external.compliance.types.list
external.incidents.create
external.newRelic.accounts.create
external.newRelic.accounts.getAll
external.newRelic.accounts.remove
external.newRelic.accounts.rotateApiKey
external.newRelic.accounts.update
external.session.create
external.tunhub.tunnels.getAll
external.tunhub.tunnels.routes.getAll
external.tunhub.tunnels.swapChannels
external.tunhub.tunnels.update