Our Site Reliability Guardian incorporates the Cloud Automation use cases. To ensure an optimal experience, we recommend upgrading your environment or contacting your account team for assistance.
For more information, see Upgrade from Cloud Automation to Site Reliability Guardian.
Cloud Automation provides its own API. For details, see Keptn API.
You can connect third-party integrations to your Cloud Automation instance. To authenticate the integration, the OAuth 2.0 client credentials flow is used.
Make sure that you trust the integration, verify its developers, and check what kind of information the integration is going to access.
Generate an OAuth 2.0 client
To generate an
OAuth 2.0 client
- Go to Account Management. If you have more than one account, select the account you want to manage.
- Select Identity & access management > OAuth clients.
- Select Create client.
Enter a client description and the user email.
- Under Cloud Automation, select at least the following scopes for a typical third-party integration.
- View resources—
- View events—
- Send events—
- Create and edit logs—
- View integrations—
- Create and edit integrations—
- Delete integrations—
- View secrets—
- View resources—
- Scroll down and select Create client.
- Copy your client ID, client secret, and Dynatrace account URN. These settings are required for the Client credentials flow.
OAuth 2.0 client cannot have wider permissions than the user who requested the client.
Test the OAuth 2.0 client for retrieving an access token
Token-based Authentication (deprecated)
In the Cloud Automation UI (bridge), go to your user menu in the upper-right corner and copy the API token, which is used for authenticating API calls.
To access the token, the user needs to be assigned the
cloudautomation:metadata:read policy statement. For details about the API, see API.
Migrate to OAuth 2.0-based authentication
Token-based authentication is deprecated. Adapt your integrations to use OAuth 2.0-based authentication instead.
API interaction in automation code
If you are sending HTTP requests to communicate with the API, you potentially add the
x-token header to authenticate the request with the provided token. Please adapt your HTTP requests to leverage OAuth 2.0-based authentication.