datadog-serverless-init-fips

packaged by Chainguard

Chainguard Container for datadog-serverless-init-fips

FIPS-enabled Datadog serverless-init runs a containerized app and ships its logs, metrics, and traces to Datadog.

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/datadog-serverless-init-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

datadog-serverless-init-fips is the FIPS-enabled variant of datadog-serverless-init. It is identical in behavior — the same serverless-init binary at /datadog-init, run as root, wrapping your application and shipping telemetry to Datadog — but built with the FIPS-validated Go cryptographic module and the hardened OpenSSL FIPS provider.

The same two differences from upstream apply: tags follow the Datadog Agent version scheme (7.83, ...) rather than upstream's serverless 1.x, and the image ships no /bin/sh and no /dotnet.sh helper (use the manual Datadog .NET tracer installation for the Azure Container Apps .NET path).

FIPS Support

FIPS images are available to Chainguard customers on a FIPS-enabled tier.

This image uses a FIPS 140-3 validated cryptographic module for its cryptographic operations. It carries the OpenSSL FIPS provider stack and the hardened FIPS OpenSSL configuration so the serverless-init telemetry pipeline negotiates TLS with the Datadog intake using validated crypto. Refer to Chainguard's FIPS documentation for details on the compliance posture and how to verify it.

Getting Started

Usage is the same as the standard variant — see the datadog-serverless-init documentation. Build your application on top of the FIPS image and provide the command in exec form:

FROM cgr.dev/ORGANIZATION/datadog-serverless-init-fips:latest

ENV DD_API_KEY=<your-datadog-api-key>
ENV DD_SITE=datadoghq.com
ENV DD_SERVICE=my-app

COPY app /usr/local/bin/app
CMD ["/usr/local/bin/app"]

Configuration

Configuration is identical to the standard variant; serverless-init is driven by Datadog's DD_* environment variables (DD_API_KEY, DD_SITE, DD_SERVICE, DD_ENV, DD_VERSION). The sidecar exposes the APM trace receiver on 8126/tcp and DogStatsD on 8125/udp.

Documentation and Resources

• Datadog Serverless Monitoring
• Install serverless-init on Google Cloud Run
• Install serverless-init on Azure Container Apps
• Chainguard FIPS images

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.