[Internal] Deployment issues (missing dependencies) in Lambda

When a customer reports issues with deploying a project that includes IronPDF, it's essential to request the following information to begin troubleshooting:

✅ Required for Diagnosis

1. IronPDF Log Files
   This is mandatory. Please request the actual log files—not just error messages or stack traces.
   If the customer is unsure how to retrieve them, kindly guide them using this article:
   👉 How to Get IronPDF Log Files in AWS

2. Dockerfile
   This helps verify whether the necessary dependencies are installed or configured properly.

3. IronPDF Version
   Knowing the exact version helps identify compatibility issues or known bugs.

These three items are crucial for identifying and resolving deployment-related issues.

🔍 Common Root Causes

Most deployment problems stem from one or more of the following:

• Missing Read/Write/Execute (RWX) permissions

• Absence of essential dependencies

• Required dependencies not included or specified in the Dockerfile

💡 Recommended Solution

In many cases, using the IronPdf.Slim package can simplify deployment. This version automatically downloads the appropriate native dependencies based on the Docker base image.

👉 Follow the guide here: Using IronPdf.Slim

⚠️ Important Note:
Customers must test this setup directly in AWS Lambda for an accurate result.
Using AWS Mock Test Tools locally may cause IronPDF to download Windows-native dependencies or local OS dependencies instead, leading to additional complications.

Happy debugging!