[Public] Is IronPdf compatible with AWS Lambda without Docker?
IronPdf requires native Linux dependencies that are not available in standard AWS Lambda environments. Use a Docker-based Lambda function to ensure compatibility and stability.
-
gcc-c++
-
glibc-devel.i686
-
glibc.i686
-
pango.x86_64
- etc..
These libraries are not available by default in standard AWS Lambda environments. If you attempt to run IronPdf in a Lambda function without Docker and without these dependencies, you may encounter:
-
Native errors related to missing libraries
-
Failures in PDF generation or rendering
-
Crashes or instability when calling IronPdf methods
Why this happens
IronPdf relies on the Chrome rendering engine internally, which itself depends on native Linux components. In minimal serverless environments like standard AWS Lambda runtimes, those components are not present and cannot be easily installed at runtime.
Recommended approach
To use IronPdf on AWS Lambda, we strongly recommend deploying it inside a custom Docker container image that includes all the required native dependencies. This ensures the environment is fully compatible.
Example Dockerfile snippet:
FROM public.ecr.aws/lambda/dotnet:8
# install necessary packages
RUN dnf update -y
RUN dnf install -y gcc-c++ pango.x86_64 libXcomposite.x86_64 libXcursor.x86_64 dbus-glib-devel
RUNdnfinstall-ylibXdamage.x86_64libXi.x86_64libXtst.x86_64cups-libs.x86_64libXScrnSaver.x86_64
RUN dnf install -y libXrandr.x86_64 alsa-lib.x86_64 atk.x86_64 gtk3.x86_64 ipa-gothic-fonts xorg-x11-fonts-100dpi
RUN dnf install -y xorg-x11-fonts-75dpi xorg-x11-fonts-cyrillic xorg-x11-fonts-Type1 xorg-x11-fonts-misc
RUN dnf install -y mesa-libgbm.x86_64
RUN dnf install -y nss-3.90.0-3.amzn2023.0.4.x86_64
WORKDIR /var/task
COPY "bin/Release/lambda-publish" .
CMD ["AWSLambdaNet8Container::AWSLambdaNet8Container.PrintPdf::FunctionHandler"]
Conclusion
IronPdf is not compatible with standard AWS Lambda environments without Docker, due to missing native dependencies.
To run IronPdf successfully in AWS Lambda, always use a Docker-based function that includes the required system libraries.
Here is the link for your reference:
Using IronPDF to Create PDF Files on AWS Lambda