# Mender deployment 2.5.0 correctly reading S3 configuration

**URL:** <https://hub.mender.io/t/mender-deployment-2-5-0-correctly-reading-s3-configuration/3052>\
**Category:** General Discussions\
**Tags:** deployment, aws\
**Created:** [January 7, 2021, 1:24pm UTC](https://hub.mender.io/t/mender-deployment-2-5-0-correctly-reading-s3-configuration/3052 "2021-01-07T13:24:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![deligatedgeek](https://avatars.discourse-cdn.com/v4/letter/d/4bbf92/32.png) [@deligatedgeek](https://hub.mender.io/u/deligatedgeek)\
**Post date:** [January 7, 2021, 1:24pm UTC](https://hub.mender.io/t/mender-deployment-2-5-0-correctly-reading-s3-configuration/3052/1 "2021-01-07T13:24:05Z")

</div>

After upgrading to 2.5.0 I found that the deployment container would not start.

Current working configuration is;  
aws uri, is set in the config.yml and replace the one in the container (via docker volume mount), docker env DEPLOYMENTS\_AWS\_URI appears to be ignored.

DEPLOYMENTS\_AWS\_REGION set in docker env, aws region set in config.yml appears to be ignored.

Would appreciate instruction on obtaining more detailed debug, I’m working from deployment docker logs and tcpdump.