# Libz.so missing for AWS CLI in AWS batch tasks

**URL:** https://community.seqera.io/t/libz-so-missing-for-aws-cli-in-aws-batch-tasks/1869
**Category:** Ask for help
**Tags:** nextflow, aws
**Created:** [March 3, 2025, 6:49am UTC](https://community.seqera.io/t/libz-so-missing-for-aws-cli-in-aws-batch-tasks/1869 "2025-03-03T06:49:32Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Andrew\_Patterson](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/andrew_patterson/32/1568_2.png) [@Andrew\_Patterson](https://community.seqera.io/u/Andrew_Patterson)
#### Post date: [March 18, 2025, 3:00am UTC](https://community.seqera.io/t/libz-so-missing-for-aws-cli-in-aws-batch-tasks/1869/4 "2025-03-18T03:00:50Z")

</div>

As a closure for this - we did some analysis by using `ldd` and it seems the `aws` v2 CLI does not locate the libz.so.1 that is distributed with its binary. And on a (slim) docker image with no existing libz - the AWS CLI then fails.

We have fixed this by manually adding a LD\_LIBRARY\_PATH in nextflow config that explicitly points the directory of the mounted AWS CLI.

---

_[View the full topic](https://community.seqera.io/t/libz-so-missing-for-aws-cli-in-aws-batch-tasks/1869)._