airflow-postgres-fips

packaged by Chainguard

Chainguard Container for airflow-postgres-fips

FIPS-hardened Apache Airflow core with the Postgres provider.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/airflow-postgres-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

Chainguard's airflow-postgres-fips image packages Apache Airflow core together with the Postgres provider, so it can run any Airflow component (webserver, scheduler, or worker) backed by a PostgreSQL metadata database. It links psycopg and psycopg2 against the system's FIPS-validated OpenSSL rather than bundling their own crypto, so the metadata database connection stays inside the FIPS boundary end-to-end.

FIPS Support

This FIPS-compliant image includes OpenSSL FIPS provider and is built with FIPS-validated cryptographic modules. Key FIPS features include:

• FIPS-validated OpenSSL provider - Uses OpenSSL FIPS provider for cryptographic operations
• Approved algorithms only - Restricted to FIPS-approved cryptographic algorithms
• FIPS mode enforcement - Cryptographic operations automatically use FIPS-validated modules
• FIPS-compliant Postgres connectivity - The Postgres metadata database connection uses only FIPS-approved authentication and encryption

For more on FIPS support in Chainguard container images, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Known Limitations

No asyncpg driver: asyncpg is excluded because it bundles its own non-FIPS OpenSSL rather than linking the system FIPS provider. Airflow derives sql_alchemy_conn_async from sql_alchemy_conn automatically when it isn't set, but that derivation always targets asyncpg regardless of which driver the sync connection uses. Always set AIRFLOW__DATABASE__SQL_ALCHEMY_CONN_ASYNC to the same value as AIRFLOW__DATABASE__SQL_ALCHEMY_CONN, or Airflow will fail to start with ModuleNotFoundError: No module named 'asyncpg'.

Getting Started

Docker

Run an Airflow component against a FIPS-enabled Postgres metadata database (for example, Chainguard's postgres-fips image) with the psycopg v3 driver, setting both the sync and async connection variables to the same value:

docker run -d --name airflow-postgres-fips \
  -e AIRFLOW__CORE__EXECUTOR=LocalExecutor \
  -e AIRFLOW__DATABASE__SQL_ALCHEMY_CONN="postgresql+psycopg://airflow:PASSWORD@postgres-host:5432/airflow?sslmode=require" \
  -e AIRFLOW__DATABASE__SQL_ALCHEMY_CONN_ASYNC="postgresql+psycopg://airflow:PASSWORD@postgres-host:5432/airflow?sslmode=require" \
  cgr.dev/ORGANIZATION/airflow-postgres-fips:latest \
  db migrate

Documentation and Resources

• Apache Airflow Documentation
• Apache Airflow Postgres Provider
• FIPS-Enabled Chainguard Containers

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.