Controller node cannot be reached after install

If the web interface never comes up after your first deployment, the problem is almost always in the controller node's bootstrap logs. Connect to the controller instance with SSM Session Manager or SSH, then inspect those logs.

Start with the bootstrap logs

cd /root/edh_bootstrap_<INSTANCE_ID>/logs
grep -riE "error|fatal|critical" .

Note

<INSTANCE_ID> is the EC2 instance ID of the controller. The folder name uses an underscore, edh_bootstrap_, not a dash.

Useful files

File	What it tells you
bootstrap_ERROR.log / bootstrap_WARNING.log / bootstrap_INFO.log	Bootstrap messages grouped by severity. Start here.
03_setup.sh.log	Main controller configuration step
filesystems_mount.log	Shared filesystem (/apps, /data) mount failures
install_required_packages.sh.log	Package installation failures
create_admin_group.log / create_new_user.log	Initial admin and user creation
cloud-init-output-*.log	Raw cloud-init output snapshots

To open a single file, list the folder first, then print or scroll through the file you want:

# List everything in the logs folder first
ls -l /root/edh_bootstrap_<INSTANCE_ID>/logs/

# Print the whole aggregated error log
cat /root/edh_bootstrap_<INSTANCE_ID>/logs/bootstrap_ERROR.log

# Print the main setup step log
cat /root/edh_bootstrap_<INSTANCE_ID>/logs/03_setup.sh.log

# Check the filesystem mount log
cat /root/edh_bootstrap_<INSTANCE_ID>/logs/filesystems_mount.log

# Scroll through a long log page by page (press q to quit)
less /root/edh_bootstrap_<INSTANCE_ID>/logs/03_setup.sh.log

# Show only the last 100 lines of a log
tail -n 100 /root/edh_bootstrap_<INSTANCE_ID>/logs/03_setup.sh.log

Did the controller finish bootstrapping?

A completion marker is written on success:

ls -l /root/.edh_bootstrap_controller_<EDH_CLUSTER_ID>_completed

If the marker is missing, bootstrap did not complete. The failing step is in the logs above.

Bootstrap completed but the interface is still unreachable?

Check the web interface logs:

cd /opt/edh/<EDH_CLUSTER_ID>/cluster_manager/web_interface/logs
tail -n 100 web_interface.log uwsgi.log

Common causes here are authentication failures, database connectivity problems, API errors, or request timeouts.