EAP AMI: Connect over SSL from a messaging client outside of AWS

Scenario: use a messaging client outside of AWS to connect over SSL to the EAP Broker of an EAP instance running inside AWS on our official AMI;

In "7.1.3. Securing the Transport", at some point you have to:

The socket-binding element for all HTTP connectors must be updated to use https instead of http.

But since we are using a different configuration in order to connect from a client outside of AWS:

/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=external-ip-address:add(host=$EXTERNAL_IP_ADDRESS,port=8080)
/subsystem=messaging-activemq/server=default/http-connector=http-connector-external-ip:add(socket-binding=external-ip-address,endpoint=http-acceptor)

This is no more valid: we need a working procedure to set this up;

This might probably involve setting up a different http-acceptor ...

The procedure should probably be added to "DEPLOYING JBOSS EAP ON AMAZON WEB SERVICES"