> ## Documentation Index
> Fetch the complete documentation index at: https://docs.niteshift.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Connect an environment to cloud services and private networks with AWS, Azure, GCP, Tailscale, OIDC, or stored secrets.

An integration gives a task access to a service outside its [environment](https://docs.niteshift.dev/environment-configuration/overview.md).
Each integration is configured per environment.

| Integration | What tasks get |
| - | - |
| [AWS](https://docs.niteshift.dev/integrations/aws.md) | Refreshed credentials for AWS CLIs and SDKs, one or more named profiles |
| [Azure](https://docs.niteshift.dev/integrations/azure.md) | Workload identity credentials for Azure CLIs and SDKs |
| [GCP](https://docs.niteshift.dev/integrations/gcp.md) | Application Default Credentials for `gcloud` and Google Cloud client libraries |
| [Tailscale](https://docs.niteshift.dev/integrations/tailscale.md) | An ephemeral, tagged node on your tailnet |
| [OIDC tokens](https://docs.niteshift.dev/integrations/oidc.md) | Short-lived tokens for any service that supports workload identity federation |
| [Secrets](#environment-variable-secrets) | API keys stored as environment variables outside the repository |

AWS, Azure, GCP, and Tailscale use Niteshift-issued [OIDC tokens](https://docs.niteshift.dev/integrations/oidc.md), 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](https://docs.niteshift.dev/environment-configuration/overview.md#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](https://docs.niteshift.dev/environment-configuration/services#environment). 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.

```yaml settings.yaml theme={"dark"}
version: 1
integrations:
  aws:
    - profile: default # A list needs exactly one default profile
      roleArn: arn:aws:iam::111122223333:role/NiteshiftDevelopment
      audience: sts.amazonaws.com
      region: us-east-2
  azure:
    tenantId: 11111111-1111-1111-1111-111111111111
    clientId: 22222222-2222-2222-2222-222222222222
  gcp:
    provider: projects/123456789/locations/global/workloadIdentityPools/id-pool/providers/niteshift
    serviceAccountEmail: workload@example-project.iam.gserviceaccount.com # Optional
  tailscale:
    clientId: <tailscale-client-id>
    tags: [tag:niteshift]
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.