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

# Deploy Account

> Deploy a Fjall-managed AWS account with VPC, security groups, and baseline infrastructure using the Fjall CLI.

<AccordionGroup>
  <Accordion icon="book" title="Prerequisites">
    Install the [**Fjall CLI**](/deployment/cli-installation) and complete the previous steps:

    * [**Deploy Organisation**](/deployment/deploy-organisation)
    * [**Deploy Platform**](/deployment/deploy-platform)
    * [**Understanding Profiles**](/deployment/understanding-profiles)
  </Accordion>
</AccordionGroup>

Deploy a managed account to every AWS account other than the root or platform account. Managed accounts apply baseline best practices and produce outputs that feed reusable infrastructure patterns.

## Select the deployment target

In organisation mode, the active deployment target decides which AWS account the deploy lands in. Targets are derived automatically from your organisation config (account and region pairs), so there is no manual profile step.

List the available targets:

```bash theme={null}
fjall target list
```

The active target is marked with a `▸`. Set a specific target by its canonical name, `<account>-<region>` (for example `production-us-use1`):

```bash theme={null}
fjall target set production-us-use1
```

Confirm the active target:

```bash theme={null}
fjall target get
```

<Note>
  When your organisation has exactly one target, Fjall resolves it automatically and you can skip this step. To override the active target for a single deploy, pass `--target <name>` to the deploy command.
</Note>

## Deploy the account

From the root of your project, run:

```bash theme={null}
fjall deploy account
```

To deploy a specific target without changing the active one, override it inline:

```bash theme={null}
fjall deploy account --target production-us-use1
```

## What happens

Fjall provisions the account baseline: a VPC, security groups, and the shared infrastructure that applications build on. On success you see a summary like this:

```bash theme={null}
--- Deployment Summary ---

🎉 Success! Your AWS account has been deployed.

🔗 You can now create your first application with 'fjall create app'!

   /\
  /  \ /\
 /  _ _\ _\
   Fjall
```

## Options

| Flag                      | Description                                                                  |
| ------------------------- | ---------------------------------------------------------------------------- |
| `--target <name>`         | Override the active deployment target for this deploy.                       |
| `--region <region>`       | Deploy to a specific region within the target's account.                     |
| `--all-regions`           | Deploy to every region configured for the target's account.                  |
| `--skip-migrations`       | Skip database migrations during this deployment.                             |
| `-e, --environment <env>` | Optional free-form label for CI/CD. It does not select an account or region. |
| `-v, --verbose`           | Enable verbose logging.                                                      |
| `--non-interactive`       | Force plain CLI output with no interactive UI.                               |

## Next Steps

<CardGroup cols={2}>
  <Card title="Create Application" icon="cube" href="/deployment/create-application">
    Scaffold your first application's infrastructure.
  </Card>

  <Card title="Deploy Application" icon="rocket" href="/deployment/deploy-application">
    Deploy an application to your managed AWS account.
  </Card>
</CardGroup>