Enabled Services

To use most Trusted Cloud by S3NS APIs and services, you must first enable them in a Trusted Cloud project. Enabling APIs and services in a Trusted Cloud project, results in the following changes:

  • Associates them with the project.
  • Adds monitoring pages in the Trusted Cloud console.
  • Enables billing for the APIs and services if billing is enabled for the project.
  • In some cases, Identity and Access Management roles only become visible when you enable the associated service.

Calling a service

The following list outlines the typical high-level requirements for using Trusted Cloud APIs and services:

  1. A Trusted Cloud project. For details on creating Trusted Cloud projects, see Creating and Managing Projects.
  2. To enable the service for the project. To learn how to enable APIs and services, see Enabling and Disabling Services.
  3. Authentication credentials for the enabled service you are using. To learn how to authenticate to a Cloud API, see Authentication methods.

The credentials you use to call Trusted Cloud APIs and services are associated with the project you use to create them.

IAM role visibility

Some IAM roles are only visible if the associated service is enabled in a Trusted Cloud project. For example, the roles/compute.admin role is only visible after the compute.googleapis.com API is enabled in a project. To learn how to list the available roles to grant in a project, see Viewing the Grantable Roles on Resources.

Services enabled by default

When you create a Trusted Cloud project using the Trusted Cloud console or Google Cloud CLI, the following APIs and services are enabled by default: