Make sure Boundary workers are functional in AWS and Azure. Workers should
have a Last Seen status within seconds when you view it in the admin console.
Also check that the boundary systemd service is running in the VM.
sudo systemctl status -l boundary
sudo journalctl -xfe -u boundary.service
Once all infrastructures are functionality. Test out the target connection using
the demo scripts in the scripts folder. Remember to export the BOUNDARY_ADD
env variable and the target ID before executing the script.
TODO
Added Multi-Hop workers by connecting self-managed workers in a private subnet with HCP workers.