# Foundation + docker public access

**URL:** <https://forums.foundationdb.org/t/foundation-docker-public-access/1658>\
**Category:** Using FoundationDB\
**Tags:** performance\
**Created:** [September 30, 2019, 4:19pm UTC](https://forums.foundationdb.org/t/foundation-docker-public-access/1658 "2019-09-30T16:19:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mbhaskar](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/mbhaskar/32/277_2.png) [@mbhaskar](https://forums.foundationdb.org/u/mbhaskar)\
**Post date:** [September 30, 2019, 5:10pm UTC](https://forums.foundationdb.org/t/foundation-docker-public-access/1658/2 "2019-09-30T17:10:43Z")

</div>

This looks like an issue with AWS private/public IP confusion. There seems to be some relevant discussion here - [Setting up remote access to FDB Server hosted on EC2, with AWS Private IP Addresses](https://forums.foundationdb.org/t/setting-up-remote-access-to-fdb-server-hosted-on-ec2-with-aws-private-ip-addresses/1465)

---

_[View the full topic](https://forums.foundationdb.org/t/foundation-docker-public-access/1658)._