Configure Aidbox and Multibox
Last updated
Was this helpful?
Last updated
Was this helpful?
is a full-featured single instance of the Aidbox FHIR server. If you are interested in multi-tenant Aidbox, consider using distribution.
All distributions can be used both on PostgreSQL distribution or managed PostgreSQLs. Basic Aidbox installation consists of two components: the backend and the database. Both are released as docker images and can be pulled from HealthSamurai . For each type of Aidbox license an individual backend image is available — either or .
is the custom build of the open source PostgreSQL database. It contains a number of extensions that are primarily used for search performance optimization. AidboxDB officially supports the latest minor releases of all major PostgreSQL versions starting from 11. Note that the database image is the same for all Aidbox backend license types.
By default, Aidbox and Multibox runs with 8 web workers and 8 DB connection pool size. That means that Aidbox can process at the same time 8 concurrent connections.
A good practice is stayed pool size the same as CPU count of your database. For example, if your database has 16 CPU cores, you can set BOX_DB_POOL_MAXIMUM__POOL__SIZE=16. Box web workers count is dependent on your load profile. For example, if you have a lot of fast read queries, you can set BOX_WEB_THREAD equal x2 or x3 of your DB pool size (32 or 48). Or if you have a lot of batch insert queries, we recommend stay web workers count as the same DB pool size.
You can configure this parameter using following environment variables.
Aidbox usually needs 2-4 Gb of memory:
Refer to the following pages for the specific image description and the list of available configuration options.
You can also see the environment variables in the Settings page in AidboxUI.
If you are looking for the latest versions of the docker images or general release cycle explanation go to the Versioning page.
See also deployment documentation: