# Self-hosted Mender - Config for Amazon CloudFront?

**URL:** <https://hub.mender.io/t/self-hosted-mender-config-for-amazon-cloudfront/960>\
**Category:** General Discussions\
**Created:** [August 23, 2019, 2:13pm UTC](https://hub.mender.io/t/self-hosted-mender-config-for-amazon-cloudfront/960 "2019-08-23T14:13:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![xulong.z](https://avatars.discourse-cdn.com/v4/letter/x/5f9b8f/32.png) [@xulong.z](https://hub.mender.io/u/xulong.z)\
**Post date:** [August 14, 2024, 4:52am UTC](https://hub.mender.io/t/self-hosted-mender-config-for-amazon-cloudfront/960/4 "2024-08-14T04:52:07Z")

</div>

Hi @will ,

Have you got it to work?

In my case, Mender prefixed the bucket name to the external URL. Do you know how to get rid of it by any chance?

> [@DEPLOYMENTS\_AWS\_EXTERNAL\_URI with CloudFront](https://hub.mender.io/t/deployments-aws-external-uri-with-cloudfront/7102):
>
> Hi, I’d like the devices to access the artefacts via AWS CloudFront domain. I’ve configured mender-deployments service with the following environment variables: In the client devices, I got an error: dial tcp: lookup [coolon-mender-artifacts.d342gnwfeb7kek.cloudfront.net](http://coolon-mender-artifacts.d342gnwfeb7kek.cloudfront.net) on 8.8.8.8:53: no such host" How to remove the “coolon-mender-artifacts” part from the CloudFront URL?

---

_[View the full topic](https://hub.mender.io/t/self-hosted-mender-config-for-amazon-cloudfront/960)._