Fjall Docs — Deploy Production-Ready AWS Infrastructure in Minutes

Prerequisites

Complete these before deploying:

Create an application (an infrastructure.ts exists in your project)
Authenticated with Fjall (run fjall login, or set FJALL_API_KEY for CI/CD)
Connected an AWS account (run fjall connect)

fjall deploy enforces both gates. An unauthenticated user sees Authentication required. Run 'fjall login' first.

Deploy your application

Run from your project root:

fjall deploy api

Replace api with your application name. The same command builds the container, synthesises infrastructure, and applies the changes.

What happens during a deploy

The interactive deploy runs an automatic pipeline and streams live progress. There is no separate “preview then confirm” step for applications.

Phase	Activity
Auth gate	Confirms Fjall login and AWS connection
Build	Builds and pushes the Docker image
Infrastructure	Provisions network, storage, messaging, database, compute, and CDN resources
Service	Starts the ECS service and reports the application URL
Complete	Shows outputs, the website URL, and next steps

Progress streams per phase with a live operation box for each resource group:

Building image ............ done
Network ................... created
Database .................. created
Compute ................... created
Deployment complete
  Website: https://api.example.com

If nothing changed since the last deploy, Fjall reports Already up to date — no changes since last deploy.

Confirmations

Fjall does not show an unconditional yes/no prompt for application deploys. Two prompts appear only when relevant:

Missing secrets: if expected SSM secrets are absent, Fjall lists each one and asks Deploy anyway? (defaults to No).
Infrastructure changes: when changes are detected, Fjall asks Infrastructure changes detected. Deploy now?.

Pass --skip-confirmation to bypass both.

Deployment options

Skip confirmations

fjall deploy api --skip-confirmation

For CI/CD pipelines, force plain output:

fjall deploy api --non-interactive

Infrastructure only

Apply infrastructure changes without rebuilding the container:

fjall deploy api --infra-only

Code only

Rebuild and redeploy the container without touching infrastructure:

fjall deploy api --deploy-only

Skip the build

Reuse an already-pushed image (pair with --deploy-only):

fjall deploy api --deploy-only --skip-build

Roll forward or back to a known image

Deploy an existing image tag (skips build, implies --deploy-only):

fjall deploy api --image-tag v1.4.2

Pass a CI/CD environment label

The -e, --environment flag is a free-form label passed through to CDK synthesis as a context value. It does not select an AWS account or region.

fjall deploy api -e production

To choose which AWS account a deploy lands in, set the active deployment target with fjall target set <name>, or override per deploy with --target <name>.

Verbose output

fjall deploy api --verbose

All deploy options

Option	Description
`--infra-only`	Deploy only infrastructure (skip code deployment)
`--deploy-only`	Deploy only code (skip infrastructure)
`--skip-build`	Skip the Docker build (use with `--deploy-only`)
`--skip-migrations`	Skip database migrations during this deployment
`--skip-confirmation`	Skip deployment confirmation prompts
`--non-interactive`	Force plain CLI output (no UI)
`-e, --environment <env>`	Free-form CI/CD label passed to CDK synthesis
`-f, --force`	Redeploy all stacks even when no infrastructure changes are detected
`-v, --verbose`	Enable verbose logging
`--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 all regions for the target’s account
`--image-tag <tag>`	Deploy an existing image tag (skips build, implies `--deploy-only`)
`--deployment-id <id>`	Deployment record ID for progress tracking
`--no-cascade`	Skip automatic platform and account deployment after an organisation deploy

After deployment

Inspect your resources

List the resources declared in the application’s infrastructure.ts:

fjall list --app api

For an application and organisation overview, use fjall apps and fjall status.

View logs

Stream logs from the AWS Console (ECS service, Logs tab), or find the log group and tail it:

aws logs describe-log-groups --log-group-name-prefix fjall
aws logs tail <your-log-group> --follow

Monitor costs

Track spending in the AWS Cost Explorer, or query it from the CLI:

aws ce get-cost-and-usage \
  --time-period Start=$(date -v-30d +%Y-%m-%d),End=$(date +%Y-%m-%d) \
  --granularity MONTHLY --metrics BlendedCost

Updating applications

Change	Command
Application code only	`fjall deploy api --deploy-only`
Infrastructure (after editing `infrastructure.ts`)	`fjall deploy api`

Troubleshooting

When a deploy fails, Fjall rolls back automatically and CloudFormation reports the failing resource.

Read the error message. CloudFormation names the resource that failed.
Re-run with --verbose for detailed logs.
Fix the underlying issue and redeploy.

Common issues

Error	Fix
`User does not have permission to create IAM roles`	Confirm your AWS role has the required IAM permissions (the SSO `AdministratorAccess` role covers this).
`You have reached the maximum number of VPCs`	Request a quota increase, or deploy to a different region with `--region`.
`Stack with name '...' already exists`	Choose a different application name, or destroy the existing stack first.

Next Steps

A first deployment typically takes 10 to 15 minutes while AWS provisions resources. Later updates are faster.

Add Resources

Extend your application with databases, storage, and more

List Resources

Inspect resources in your infrastructure.ts

Set Up CI/CD

Automate deployments from your pipeline

Install & Setup

Application Deploy

Organisation Setup

Organisation Deploy

Deploy Application

Prerequisites

Deploy your application

What happens during a deploy

Confirmations

Deployment options

Skip confirmations

Infrastructure only

Code only

Skip the build

Roll forward or back to a known image

Pass a CI/CD environment label

Verbose output

All deploy options

After deployment

Inspect your resources

View logs

Monitor costs

Updating applications

Troubleshooting

Common issues

Next Steps

Add Resources

List Resources

Set Up CI/CD

​Prerequisites

​Deploy your application

​What happens during a deploy

​Confirmations

​Deployment options

​Skip confirmations

​Infrastructure only

​Code only

​Skip the build

​Roll forward or back to a known image

​Pass a CI/CD environment label

​Verbose output

​All deploy options

​After deployment

​Inspect your resources

​View logs

​Monitor costs

​Updating applications

​Troubleshooting

​Common issues

​Next Steps

Add Resources

List Resources

Set Up CI/CD

Prerequisites

Deploy your application

What happens during a deploy

Confirmations

Deployment options

Skip confirmations

Infrastructure only

Code only

Skip the build

Roll forward or back to a known image

Pass a CI/CD environment label

Verbose output

All deploy options

After deployment

Inspect your resources

View logs

Monitor costs

Updating applications

Troubleshooting

Common issues

Next Steps