# Awscli can't find libz share object file when running nextflow workflow on AWS Batch

**URL:** https://community.seqera.io/t/awscli-cant-find-libz-share-object-file-when-running-nextflow-workflow-on-aws-batch/1208
**Category:** Ask for help
**Tags:** aws, nf-core
**Created:** [September 20, 2024, 3:54pm UTC](https://community.seqera.io/t/awscli-cant-find-libz-share-object-file-when-running-nextflow-workflow-on-aws-batch/1208 "2024-09-20T15:54:18Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![emiller](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/emiller/32/79_2.png) [@emiller](https://community.seqera.io/u/emiller)
#### Post date: [October 13, 2025, 4:10pm UTC](https://community.seqera.io/t/awscli-cant-find-libz-share-object-file-when-running-nextflow-workflow-on-aws-batch/1208/4 "2025-10-13T16:10:57Z")

</div>

> [@Libz.so missing for AWS CLI in AWS batch tasks](https://community.seqera.io/t/libz-so-missing-for-aws-cli-in-aws-batch-tasks/1869/4):
>
> 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.

This might be the answer!

---

_[View the full topic](https://community.seqera.io/t/awscli-cant-find-libz-share-object-file-when-running-nextflow-workflow-on-aws-batch/1208)._