Skip to main content
An integration gives a task access to a service outside its environment. Each integration is configured per environment. AWS, Azure, GCP, and Tailscale use Niteshift-issued OIDC tokens, so no long-lived cloud credential is stored.

Quick start

The agent can configure AWS, Azure, GCP, and Tailscale for you:
  1. Start a task in the environment you want to connect.
  2. Ask the agent to connect AWS, Azure, GCP, or Tailscale. Specify the account, project, or tailnet, the resources, and the operations it needs. For example:
    Connect this environment to AWS so tasks can read objects in my reports S3 bucket.
  3. The agent writes the Niteshift configuration, helps you configure cloud-side trust and permissions scoped to this environment, and verifies access with an intended resource operation.
Each provider page covers the configuration and cloud-side trust details.

Environment variable secrets

You can also integrate with systems by having Niteshift store API keys or secrets. You can store secrets as environment variables in Niteshift settings, outside the repository. The Setup script scope is available to .niteshift/setup and .niteshift/resume. The separate Agent scope is available to the agent and its terminal, including commands it runs. Services do not inherit either scope. To give a managed service a secret, store it in Setup script and reference its name with secret in the services.yaml file. Service secret references cannot read Agent scope variables.

Settings reference

AWS, Azure, GCP, and Tailscale are declared under integrations in the environment’s committed .niteshift/settings.yaml. Each provider page covers the cloud-side setup.
settings.yaml