Enabled services

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

  • Associates them with the project.
  • Adds monitoring pages in the Cloud de Confiance 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 Cloud de Confiance APIs and services:

  1. A Cloud de Confiance project. For details on creating Cloud de Confiance 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 Cloud de Confiance 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 Cloud de Confiance 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 Cloud de Confiance project using the Cloud de Confiance console or Google Cloud CLI, the following APIs and services are enabled by default: