Secured remote docker API port is available, and access is appropriately firewalled based on user input.
Remote API is unsecured, and only available tunneled over SSH with a recent version of SSH not readily available on may clients.
Ideally I’d like to see this capability emulate some of the convenience features for docker-machine, in particular remote, secure API access from a client machine and the management of certs on behalf of the customer.
This would make use of this project for development work – in particular service connectivity and orchestration between containerized micro services – much more convenient than currently.
I’ve started hacking a bit to include AccessRange parameter for the CFN template.
Steps to reproduce the behavior