Configuring Worker Services with `flightcontrol.json`

Worker Service Attributes

The type for all worker services is worker, and should be specified like the following:

type: 'worker'

Common Service Configuration

Before configuring the worker-specific options below, you should review the Common Service Configuration that applies to all service types. This includes important settings for:

Name
Environment variables
Build configuration
Pre & post deploy commands
Watch paths
And more…

Worker-Specific Options

The following attributes are specific to worker services:

Target

target.type: 'fargate' | 'ecs-ec2'

Example: "target": {"type": "fargate"}
Defaults to fargate
Fargate is a fully managed, pay-as-you-go compute engine that lets you focus on building apps without managing servers. It’s the easiest to use. The tradeoffs are that it does not support GPUs or custom instance types, and can be up to 1.5 times more expensive than ECS+EC2, depending on how well you optimize the EC2 compute.
ECS+EC2 is AWS’s version of Kubernetes. It gives you advance control over the cluster instance type and supports GPUs. It enables leveraging Reserved Instances for 50% or more savings. The tradeoffs are that 1) you have to manage the instance size to ensure there is enough CPU and memory for your app, 2) autoscaling is up to 2x slower if you don’t have empty EC2 instances on standby, and 3) you have to manage the config options optimize compute across instances to minimize wasted resources. See Understanding ECS-EC2 for more details.

If target is fargate: no other fields

If target is ecs-ec2:

target.clusterInstanceSize: string

Example: "clusterInstanceSize": "t3.medium"
Supported values: all non-ARM based instance sizes. See all instance options.

target.clusterMinInstances: number

Example: "clusterMinInstances": 1
Minimum 1
Fastest deploys are possible when this is at least 2x the number of app instances running
Faster autoscaling is enabled when this is higher than minimum app instances so that machines are already running

target.clusterMaxInstances: number

Example: "clusterMaxInstances": 5
Minimum same as clusterMinInstances
Must be high enough to accommodate 2x your app max instances count, otherwise deploys may fail
See Understanding ECS-EC2 for more explanation and best practices.

Worker CPU

cpu: number

Example: "cpu": 0.25
This is the AWS vCPU unit for each service instance. It does not correspond to number of cores. It’s an abstract unit of CPU power defined by Amazon
Supported values:
- If target fargate: 0.25, 0.5, 1, 2, 4, 8, 16
  - For more details on Fargate configuration, see AWS’s Fargate pricing page
- If target ecs-ec2: range: 0.125 to 10 or the vCPU of clusterInstanceSize, whichever is less

Worker Memory

memory: number

Example: "memory": 1
In gigabytes
Supported values:
- If target fargate:
  - With cpu: 0.25 - 0.5, 1, 2 With cpu: 0.5 - 1...4 (intervals of 1)
  - With cpu: 1 - 2...8 (intervals of 1)
  - With cpu: 2 - 4...16 (intervals of 1)
  - With cpu: 4 - 8...30 (intervals of 1)
  - With cpu: 8 - 16...60 (intervals of 4)
  - With cpu: 16 - 32...120 (intervals of 8)
  - For more details on Fargate configuration, see AWS’s Fargate pricing page
- If target ecs-ec2: range: 0.125 to 0.25 less than the memory of clusterInstanceSize. (0.25 GB is reserved for the ECS agent)

Worker GPU

gpu: integer

Optional, with default: 0
Range: 0 to 16
This is how many GPUs to expose to your container
Supported values:
- If target fargate: 0 or unset
- If target ecs-ec2: Range 0 to the GPU of clusterInstanceSize (requires a GPU compatible instance size)

Storage

storage: int

Example: "storage": 20
Support values: 20-200
This is the ephemeral storage available to all containers running on your task. For example, this storage will be shared between your main application container and any sidecar containers (like the DataDog agent) if you are using them.
By default, AWS sets this value to 20GB.
For more details, see AWS’s Fargate task storage page
Note: Storage is not permitted with ecs-ec2 target type

Number of Instances

minInstances: int

Example: "minInstances": 1
Optional with default: 1
Supported values: 1+
The minimum number of instances you want to be running. A minimum of 2 means there will be two containers running code from the same image.

maxInstances: int

Example: "maxInstances": 2
Optional with default: 1
Supported values: 1+
Must be greater than or equal to minInstances
The maximum number of instances you want to be running. ECS will autoscale the number of instances based on your traffic up to this maximum. This number effectively sets a limit on AWS cost you may incur.

Autoscaling

autoscaling: object

Example:

"autoscaling": {
    "cpuThreshold": 60,
    "memoryThreshold": 60,
    "cooldownTimerSecs": 300
},

Optional
Enables autoscaling for your service. For more, see our autoscaling guide.

For each service’s autoscaling configuration, you can configure the following attributes:

cpuThreshold - The CPU threshold at which to scale up or down. For example, 60 would mean that if the average CPU usage across all instances is greater than 60%, then we will scale up. If it is less than 60%, then we will scale down.
memoryThreshold - The memory threshold at which to scale up or down. For example, 60 would mean that if the average memory usage across all instances is greater than 60%, then we will scale up. If it is less than 60%, then we will scale down.
cooldownTimerSecs - The cooldown timer in seconds. This is the amount of time to wait after scaling up or down before scaling again. For example, 300 would mean that we will wait 5 minutes after scaling up or down before scaling again.

Container Insights

containerInsights: boolean

Example: "containerInsights": true
Optional with default: false
Enables AWS Container Insights for your service. This will send metrics to CloudWatch for your service. For more, see our Container Insights guide.

Docker Labels

dockerLabels: Record<string, string>

Example: "dockerLabels": {"com.example.vendor": "ACME"}
Optional
Will apply the set labels to the container

Version History Count

versionHistoryCount: number

Example: "versionHistoryCount": 15
Optional with default: 10
How many previous container images to keep in ECR. This determines how far back you can rollback. ECR storage is $0.10 per GB / month, so this configuration is balance between cost and rollback history.

Runtime-only Environment variables

includeEnvVariablesInBuild: boolean

Example: "includeEnvVariablesInBuild": false
Optional with default: true
Exclude environment variables from the build environment - see the Configuring Environment Variables page for more details.

Sidecars

sidecars: array

Example:

"sidecars": [
    {
        "name": "open-telemetry-collector",
        "image": "otel/opentelemetry-collector-contrib:0.83.0",
        "cpuAllotment": 0.1,
        "memoryAllotment": 0.25,
        "enableNetworking": true,
        "ports": [4318],
        "logging": false,
        "essential": false,
        "dockerLabels": {},
        "envVariables": {}
    }
]

Optional
Array of sidecar container configurations
Each sidecar container supports:
- name (required): string - The name of the sidecar container
- image (required): string - The URL to the image for the sidecar container
- cpuAllotment (required): number - The absolute amount of CPU to allocate (minimum 0)
- memoryAllotment (required): number - The absolute amount of memory to allocate in GB (minimum 0)
- enableNetworking: boolean - Whether to enable networking (default: true)
- ports: number[] - Array of ports to expose (optional)
- logging: boolean - Whether to enable logging (default: false)
- dockerLabels: Record<string, string> - Docker labels to set (optional)
- essential: boolean - Whether the container is essential (default: false)
- startCommand: string | string[] - Command to run when starting the container (optional)
- envVariables: object - Environment variables for the container (optional)

Logging

logging: object

Optional
Fields:
- cloudwatchLogsEnabled: boolean (default: true) - Whether to enable CloudWatch logging
- cloudwatchLogsRetentionDays: number (optional) - Number of days to retain logs
  - Must be one of: 1, 3, 5, 7, 14, 30, 60, 90, 120, 150, 180, 365, 400, 545, 731, 1096, 1827, 2192, 2557, 2922, 3288, 3653
- ecsLogsMetadataEnabled: boolean (default: false) - Whether to add ECS metadata to logs
- firelens: object (optional) - Firelens configuration
  - See Firelens docs and examples for more details
  - Fields:
    - configSource: string (required) - Either "inline" or "file"
    - configFilePath: string (required if configSource is "file") - Path to the config file in repo
    - config: array (required if configSource is "inline") - Array of plugin configurations:
      - name: string (required) - Name of the output plugin (e.g., “datadog”)
      - match: string (required) - Pattern to match from log stream (e.g., ”*”)
      - options: object (required) - Plugin-specific options (e.g., {"api_key": "1234"})
  - When using configSource: "inline":
```
{
  "firelens": {
    "configSource": "inline",
    "config": [
      {
        "name": "datadog",
        "match": "*",
        "options": {
          "api_key": "1234",
          "dd_tags": "project:fluentbit"
        }
      }
    ]
  }
}
```
  - When using configSource: "file":
```
{
  "firelens": {
    "configSource": "file",
    "configFilePath": "firelens.conf"
  }
}
```

Privileged Mode

privileged: boolean

Example: "privileged": true
Optional with default: false
Only supported for ecs-ec2 target type
When enabled, the container will run with elevated privileges

Extra options for Nixpacks build type

basePath?: string (only supported when buildType: nixpacks)

Example: "basePath": "./apps/frontend"
Optional, defaults to .
The directory containing your application code, relative to the repository root
Allows you to specify in which folder the following build commands should run

installCommand: string

Example: "installCommand": "./install.sh"
Optional, intelligent default based on your language and framework detected at the basePath
What we use to install dependencies for your build

buildCommand: string

Example: "buildCommand": "blitz build"
Optional, intelligent default based on your language and framework detected at the basePath
What we use to build your app

postBuildCommand: string

Example: "postBuildCommand": "./postBuildCommand.sh"
Optional, Empty by Default
Used as a build hook to run any operation after your build is complete
Note: buildCommand must be set for postBuildCommand to be used

startCommand: string

Example: "startCommand": "blitz start"
Optional, intelligent default based on your language and framework detected at the basePath
What we use to start your app

Extra options for Dockerfile build type

dockerfilePath: string

Example: "dockerfilePath": "packages/web/Dockerfile"
Relative path to the Dockerfile from your repo root
It’s recommended to use ENTRYPOINT instead of CMD for your start command
You can authenticate with Docker Hub by adding your Docker Hub credentials as DOCKER_USERNAME and DOCKER_PASSWORD environment variables. If these env variables are present, we’ll run docker login with them. This will prevent Docker Hub rate limit issues.

dockerContext: string

Example: "dockerContext": "packages/web"
Optional with default: the directory containing the Dockerfile
The build context for the Docker build. This is the directory that will be sent to the Docker daemon for building the image.

startCommand: Array<string>

Optional
This will override the CMD in the docker image
If ENTRYPOINT in the Dockerfile is set to something like ENTRYPOINT ["/bin/bash", "-l", "-c"], then you can do startCommand: ["bundle exec sidekiq -C config/sidekiq.yml"]
Without ENTRYPOINT, you will need something like startCommand: ["/bin/bash", "-c", "node index.js"]
See Dockerfile docs for more details

injectEnvVariablesInDockerfile: boolean

Example: "injectEnvVariablesInDockerfile": false
Optional with default: true
Whether to inject environment variables automatically into Dockerfile or not
It’s recommended to use Docker build secrets to control how environment variable are used during build, check the guide here

Extra options for From Service build type

containerImage.fromService: string

Example:

"containerImage": {
  "fromService": "my-api"
}

Required (non-empty string)
The Given ID of the service that will be used as the source for the container image. The service specified here needs to be built by Flightcontrol.

startCommand: Array<string>

Optional
This will override the CMD in the docker image
If ENTRYPOINT in the Dockerfile is set to something like ENTRYPOINT ["/bin/bash", "-l", "-c"], then you can do startCommand: ["bundle exec sidekiq -C config/sidekiq.yml"]
- Nixpacks uses this as the default entrypoint.
Without ENTRYPOINT, you will need something like startCommand: ["/bin/bash", "-c", "node index.js"]
See Dockerfile docs for more details

Extra options for From Repository build type

Example:

"containerImage": {
  "registryId": "ecr-9l03731",
  "repository": "node:18-slim",
  "tag": "latest"
}

containerImage.registryId: string

Example: "registryId": "ecr-9l03731"
Required (non-empty string)
Registry ID in Flightcontrol, you can find this on the Registries page under Organization Settings

containerImage.repository: string

Example: "repository": "node:18-slim"
Required (non-empty string)
This is the URI of the image repository you wish to access

containerImage.tag?: string

Example: "tag": "latest"
Optional with default: "latest"
Must be non-empty string when provided
This is the tag of the image from the repository that you would like to use

startCommand: Array<string>

Optional
This will override the CMD in the docker image
If ENTRYPOINT in the Dockerfile is set to something like ENTRYPOINT ["/bin/bash", "-l", "-c"], then you can do startCommand: ["bundle exec sidekiq -C config/sidekiq.yml"]
Without ENTRYPOINT, you will need something like startCommand: ["/bin/bash", "-c", "node index.js"]
See Dockerfile docs for more details

Private Web Scheduler

Configuring Worker Services with flightcontrol.json

Worker Service Attributes

Common Service Configuration

Worker-Specific Options

Target

Worker CPU

Worker Memory

Worker GPU

Storage

Number of Instances

Autoscaling

Container Insights

Docker Labels

Version History Count

Runtime-only Environment variables

Sidecars

Logging

Privileged Mode

Extra options for Nixpacks build type

Extra options for Dockerfile build type

Extra options for From Service build type

Extra options for From Repository build type

Configuring Worker Services with `flightcontrol.json`