Skip to main content
Connect GreenNode to inspect IAM, VKS, vLB, vMonitor, and vServer resources. CloudThinker can update VKS metadata or start, stop, and reboot a vServer after you approve the change.

​
Prerequisites

  • A GreenNode client ID and client secret from a service account.
  • The GreenNode region containing the resources you want to read: HCM-3 or HAN.
  • A project ID for vLB or vServer reads.
  • A portal user ID for vServer and block-volume reads or actions.
VKS reads work with Client ID, Client secret, and Default region. vServer and block-volume reads require both Portal User ID and Project ID. GreenNode does not auto-detect a project.

​
Setup

1

Create a GreenNode service account

Open GreenNode IAM → Service accounts, then:
  1. Click Create a Service account.
  2. Enter a name, such as cloudthinker.
  3. In the scope picker, search for vserver and select the vServer scopes you need.
  4. Click Create Service account in the upper-right corner.
  5. Copy the generated Client ID and Client secret.
2

Copy your Portal User ID

Open the GreenNode dashboard. In the upper-right corner, click your avatar, then hover over the Currently signed in as card.The card shows two values:
  • Account email: alice@gmail.com
  • Account ID: 123456
Copy the numeric Account ID into CloudThinker’s Portal User ID field. Do not use the account email.
3

Copy your Project ID when needed

In the GreenNode dashboard, open vServer, then open Limit. Copy User Project ID for the project you want CloudThinker to access.
4

Add the connection

In CloudThinker, open Connections, choose GreenNode, and enter the values in the order below. Click Connect and wait for the connection to show Connected.

​
Connection details

The connection does not auto-detect a project. Enter Project ID for vLB reads, and enter both IDs for vServer and block-volume operations.

​
Required permissions

Use a service account with access to the GreenNode resources you want CloudThinker to inspect or manage. The available provider documentation does not specify the exact roles or scopes for each resource type.
Use credentials limited to the resources this connection needs. CloudThinker asks for approval before every provider change.

​
Agent capabilities

​
Verify the connection

​
Example prompts

​
Troubleshooting

Enter both Client ID and Client secret, then reconnect.
Choose HCM-3 or HAN for Default region, then reconnect.
Enter Project ID, then reconnect.
Enter both Portal User ID and Project ID, then reconnect.
Confirm that Project ID identifies the project you want to inspect. GreenNode does not auto-detect a project.
Use a positive numeric value for Portal User ID.

​
Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.

Connections

See all available provider connections.

Kubernetes Connection

Connect a Kubernetes cluster directly for workload-level operations.