Skip to main content
  • Fjall CLI installed, Node.js 22 or later.
  • Signed in. Run fjall login, or set FJALL_API_KEY for CI. Credentials live at ~/.fjall/auth.json (or $FJALL_CONFIG_DIR/auth.json).
  • At least one AWS account in your organisation with status disconnected. Run fjall connect status to see every connection, disconnected ones included.
  • Permission to create a CloudFormation stack in the target AWS account. The command opens the AWS console in your browser.

​
Restore a disconnected account

Reconnect the only disconnected account. The CLI auto-selects it and prints which account it picked.
Reconnect a specific account by its 12-digit AWS account id.
Reconnect with extra step detail.
fjall reconnect restores an account whose status is disconnected. fjall connect --force does something different: it re-issues a fresh CloudFormation stack for a connection that already matches on region and environment. Use fjall connect for a brand-new account, fjall reconnect to recover an existing one.

​
What happens

The command runs four steps and prints progress for each. Key behaviours:
  • The existing record is preserved. Reconnect is OIDC-only. The account’s name, tier and stage stay exactly as they were, so recovering from a connector teardown does not re-tier or rename anything.
  • The browser opens automatically. The Quick Create URL is also printed as Open in browser: <url>, so you can open it by hand if the automatic launch fails.
  • Already-connected accounts short-circuit. If OIDC trust turns out to be intact, the CLI reports that, marks every step complete and exits without creating a stack.
  • Validation failure is not fatal. If the role cannot be validated straight after the stack completes, the CLI warns that the connection was re-established but validation failed, and suggests waiting a moment before retrying.
  • Account-tier connections get a deploy hint. After a restored account-tier connection, the CLI probes whether that account’s infrastructure stack is deployed and points at fjall account deploy to deploy or update it.
  • Cancelling is safe. Ctrl+C reports Reconnect cancelled by user and runs signal cleanup.

​
Target resolution

​
Output

On success the CLI prints a summary carrying the account id, the resulting status, and the region when one is resolved. On failure it marks the active step as errored and prints the masked failure message.

​
Agent mode

fjall reconnect has no machine-readable output. Passing --agent, --fields, --budget or --full is refused rather than silently ignored, and the refusal names the alternative: run the command without the flag, then read the resulting state with fjall connect status --agent.

​
Options

​
Next Steps

fjall connect

Connect a new AWS account and check connection status.

Deploy account infrastructure

Run fjall account deploy after trust is restored.

fjall drift

Detect and repair drift once the account is reachable again.

fjall deploy

Deploy your applications into the reconnected account.