Our Site Reliability Guardian & Workflows incorporate the Cloud Automation use cases. As Cloud Automation support will be discontinued on December 31, 2024, we recommend a timely Upgrade from Cloud Automation to Site Reliability Guardian. Please contact your account team for additional information and assistance.
To work with the Cloud Automation UI (bridge) and API, you need permissions as described below.
Cloud Automation provides three default policies with view
, approve
, or admin
permissions. They can be bound to groups, but we don't recommend that you customize them. Instead, create a new policy as described below.
To define a custom policy for a certain user group
Go to Account Management. If you have more than one account, select the account you want to manage.
Select Identity & access management > Policies.
Select Add policy.
Enter a policy name and, optionally, a description of your policy. For example, to create an approver policy with a project restriction, you need to create two policies containing the following policy statements:
ALLOWcloudautomation:integrations:read,cloudautomation:logs:read,cloudautomation:metadata:read,cloudautomation:secrets:read,cloudautomation:projects:read,cloudautomation:events:read;
ALLOWcloudautomation:resources:read,cloudautomation:services:read,cloudautomation:stages:read,cloudautomation:events:write WHERE cloudautomation:project = "project-name";
optional Depending on the policy statement you have defined, you can select different conditions as shown in the example of an approver with project restriction. See below for the conditions allowed for each policy statement.
cloudautomation:events:read
cloudautomation:events:write
cloudautomation:project
, cloudautomation:stage
, cloudautomation:service
, cloudautomation:event
cloudautomation:projects:read
cloudautomation:project
1cloudautomation:projects:write
cloudautomation:project
cloudautomation:projects:delete
cloudautomation:project
cloudautomation:stages:read
cloudautomation:project
, cloudautomation:stage
cloudautomation:services:read
cloudautomation:project
, cloudautomation:stage
, cloudautomation:service
cloudautomation:services:write
cloudautomation:project
, cloudautomation:stage
, cloudautomation:service
cloudautomation:services:delete
cloudautomation:project
, cloudautomation:stage
, cloudautomation:service
cloudautomation:resources:read
cloudautomation:project
, cloudautomation:stage
, cloudautomation:service
cloudautomation:resources:write
cloudautomation:project
, cloudautomation:stage
, cloudautomation:service
cloudautomation:resources:delete
cloudautomation:project
, cloudautomation:stage
, cloudautomation:service
On account of a known limitation, this condition doesn't work in the Cloud Automation frontend. Do not set this condition if the policy should control user interactions.
cloudautomation:metadata:read
cloudautomation:logs:read
cloudautomation:logs:write
cloudautomation:integrations:read
cloudautomation:integrations:write
cloudautomation:integrations:delete
cloudautomation:secrets:read
cloudautomation:secrets:write
cloudautomation:secrets:delete
Select Save.
To define a group
You can add an existing or new user to a group.
After assigning a user to a user group that contains at least a viewer permission, the user can authenticate on the Cloud Automation bridge
Open https://<YOUR-CLOUD-AUTOMATION-INSTANCE>/bridge
, making sure to replace the placeholder (<YOUR-CLOUD-AUTOMATION-INSTANCE>
) with your own value.