Skip to main content
There is no fjall profile command. Fjall derives AWS profiles automatically. Nothing to add, set, or get.

​
How profiles work

Fjall derives one AWS profile per account and region from your organisation config. The CLI fetches that config from the API, then computes profiles at runtime. No profile is authored or stored on disk. Derived profiles appear in ~/.aws/config with the canonical name <org>-<account>-<region>, for example:
OIDC is preferred whenever an account carries its own oidcRoleArn. See Understanding Profiles for the full derivation rules.

​
Connect an AWS account

Connecting an account is what produces the profiles. Run:
This records the connection in your organisation config. Fjall derives the profiles from there.

​
Select which account a deploy lands in

In organisation mode, the active deployment target chooses the account and region for a deploy. Use the fjall target subcommands:
Target names follow the form <account>-<region>, for example production-us-use1. fjall target set persists the choice as activeTarget in fjall-config.json. At deploy time, a per-deploy --target <name> flag overrides the active target.
The -e, --environment flag on fjall deploy does not select an account or region. It is an optional free-form label for CI/CD that passes through to CDK synthesis. Use fjall target set to choose the deploy account.

​
Next Steps

Understanding Profiles

See the full account-mode and organisation-mode derivation rules.

fjall connect

Connect an AWS account via OIDC.

fjall deploy

Deploy an application to the selected target.

Deployment Targets

Choose which account a deploy lands in with fjall target.