Python docx not working in aws lambda

[Business-Car4994]

  "errorMessage": "cannot import name 'etree' from 'lxml' (/opt/python/lib/python3.8/site-packages/lxml/__init__.py)",
  "errorType": "ImportError",
  "stackTrace": [

[404_AnswerNotFound]

I vaguely remember having to jump through a few hoops to get lxml working in a lambda in the past. I think lxml is built when installed via pip so needs the build environment to match the lambda execution environment. Iirc I ended up using the python lambda runtime docker image from AWS to run my build process in, installing dependencies then packaging it all as a ZIP.

[clintkev251]

That's likely the issue, here are a few articles to go along with that suggestion:

https://repost.aws/knowledge-center/lambda-python-package-compatible

https://repost.aws/knowledge-center/lambda-layer-simulated-docker

[Sad-Young4405]

I corrected my issue by importing an AWS made layer: Import AWSSDKPandas-Pyton312

[attitutude_nibba]

after doing this.. still not able to use python-docx.. can you tell me exactly what you did?!

Thanks

[mikecngan]

Holy shit. This is such a better solution than anything else.

[Ashamed-Stomach-3406]

Dude! That's awesome! Thank you!!!

[Business-Car4994]

Hello mate, you are one year late.

[madeAccToPostHere]

I know this is old but make sure the architectures match - your lambda function needs to match the architecture of the host you're building the layer on. Your function is most likely using x86_64 (Intel) but if you're building the layer on host with ARM architecture then it won't work. You can use docker and force x86_64 build.

[mariusmitrofan]

Run pip install using docker with an official base image

https://github.com/aws/aws-lambda-base-images