BusyBot

Reference · Credentials

Venafi TLS Protect Cloud credentials

Used by 2 BusyBot nodes.

Type venafiTlsProtectCloudApi 2 fields

The Venafi TLS Protect Cloud credential holds an API key from your Venafi tenant plus the region it lives in. Region is not cosmetic — US and EU tenants are separate deployments, and a key from one never authenticates against the other.

Fields

FieldTypeRequiredNotes
Region
region		 string Yes "cloud" for US or "eu" for EU.
API Key
apiKey		 password Yes Your Venafi TLS Protect Cloud API key.

Getting your credentials

  1. Sign in to your Venafi TLS Protect Cloud tenant.
  2. Open your user preferences or account settings and locate the API key for your user, generating one if needed.
  3. Copy the key into the credential’s API Key field.
  4. Set Region to cloud for a US tenant or eu for an EU tenant, matching where your tenant is hosted.

Permissions and scopes

The key acts as the Venafi user it belongs to, with that user’s roles and team memberships. Certificate issuance in particular is governed by policy and by which applications and issuing templates the user can reach — a valid key still cannot request a certificate outside its permitted policy.

Troubleshooting

  • 401 Unauthorized on a key you just copied — the region is wrong. US and EU are separate deployments with separate keys.
  • 403 on issuance — the user lacks access to the application or issuing template, or the request violates the applicable policy.
  • Object not found — the resource belongs to a different tenant than the key does.

Frequently asked questions

What does the Region field control?

Which Venafi deployment requests are sent to — US (`cloud`) or EU (`eu`). They are separate, so a key from one tenant always fails against the other.

Where is the API key found?

In your user preferences within the Venafi TLS Protect Cloud tenant, as a per-user key.

Why is a certificate request rejected even though the key works?

Issuance is governed by policy plus the user's access to the application and issuing template. Authentication succeeding does not imply the request is permitted.

Nodes that use Venafi TLS Protect Cloud

One credential works across every node below — create it once and reuse it.

Last updated . Spotted something wrong? Tell us.