Skip to main content
Niteshift obtains and refreshes credentials for AWS tools and libraries using OIDC.
Ask the agent in a task to connect AWS. It writes the configuration, walks you through the cloud-side setup below, and verifies access. See the quick start.
Within Niteshift, the configuration lives within settings.yaml. You can declare each AWS profile that you want to configure:
settings.yaml
You need to have at least one default profile. For each AWS profile, run ns oidc-token --inspect --audience '<configured-audience>' in the Niteshift terminal tab with that profile’s audience (for example, sts.amazonaws.com). This shows the exact iss, aud, and environment-specific sub without printing the token. In each role’s AWS account, configure an OIDC identity provider using the inspected iss and register the inspected aud as an allowed audience. Each role’s trust policy should require both the exact inspected aud and sub, as shown in the example below. Trusting only the shared issuer and audience does not restrict access to your Niteshift environment. Use this trust policy, replacing <role-account-id> with the role’s AWS account ID and <inspected-aud> and <inspected-sub> with the exact inspected values. The sub has the form org:<org_id>:environment:<environment_id>; copy the entire inspected value without wildcards.
Repeat this setup for every configured role and account. AWS’s OIDC role guide covers trust and separate role permissions policies.