When I’m using docker compose in a hosted environment, generally the minimum requirement is to modify/add the following to the .env file. This essentially is doing what you would have done in that first set of export statements for the “Host it anywhere” quickstart, we’re just applying/uncommenting the values for use in docker.
# Update this to the public DNS
ZITI_CTRL_ADVERTISED_ADDRESS=ec2-3-143-246-113.us-east-2.compute.amazonaws.com
# Uncomment and update these appropriately, the defaults port values are what all doc generally uses
ZITI_CTRL_EDGE_IP_OVERRIDE=ec2-3-143-246-113.us-east-2.compute.amazonaws.com
ZITI_CTRL_EDGE_ADVERTISED_PORT=8441
ZITI_CTRL_ADVERTISED_PORT=8440
# I believe there is a bug here that's on my plate to fix, I'll double check this
# but this should say _ADDRESS, the one in the env says "_HOST"
ZITI_ROUTER_ADVERTISED_ADDRESS=ec2-3-143-246-113.us-east-2.compute.amazonaws.com
# Uncomment and update the following as needed
ZITI_ROUTER_PORT=8442
ZITI_ROUTER_IP_OVERRIDE=172.31.16.243
Here’s the fully edited .env file for review
# OpenZiti Variables
ZITI_IMAGE=openziti/quickstart
ZITI_VERSION=latest
# the user and password to use
# Leave password blank to have a unique value generated or set the password explicitly
ZITI_USER=admin
ZITI_PWD=
# controller name, address/port information
ZITI_CTRL_NAME=ziti-controller
ZITI_CTRL_EDGE_ADVERTISED_ADDRESS=ziti-edge-controller
ZITI_CTRL_ADVERTISED_ADDRESS=ec2-3-143-246-113.us-east-2.compute.amazonaws.com
ZITI_CTRL_EDGE_IP_OVERRIDE=ec2-3-143-246-113.us-east-2.compute.amazonaws.com
ZITI_CTRL_EDGE_ADVERTISED_PORT=8441
ZITI_CTRL_ADVERTISED_PORT=8440
# The duration of the enrollment period (in minutes), default if not set. shown - 7days
ZITI_EDGE_IDENTITY_ENROLLMENT_DURATION=10080
ZITI_ROUTER_ENROLLMENT_DURATION=10080
# router address/port information
#ZITI_ROUTER_NAME=ziti-edge-router
ZITI_ROUTER_ADVERTISED_ADDRESS=ec2-3-143-246-113.us-east-2.compute.amazonaws.com
ZITI_ROUTER_PORT=8442
ZITI_ROUTER_IP_OVERRIDE=172.31.16.243
#ZITI_ROUTER_LISTENER_BIND_PORT=8444
#ZITI_ROUTER_ROLES=public
Now, I can do a quick test and ping the controller’s edge
This should get you up to the point of having a functional, externally accessible hosted ziti network, let me know if this helps or if you’re still having issues.