Storage Gateway not Exposing HTTP or HTTPS ports

Hello magic-moremagic, When activating a new gateway, you have a couple of options. You can use the AWS Console. In this case, the AWS Console will allow you to activate the gateway by specifying the newly created gateway's IP address. As long as the host running the AWS Console has port 80 (HTTP) connectivity to the gateway IP address, the AWS Console will automatically retrieve the activation key and activate the gateway. If the host running the AWS Console browser session does not have port 80 connectivity to the gateway or you are using the API to activate the gateway, you can manually retrieve the activation key from the gateway using the instructions here: https://docs.aws.amazon.com/storagegateway/latest/tgw/get-activation-key.html.

As for your comment about "No HTTP or HTTPS ports are being exposed on the on premises storage gateway!"; the HTTP port is only active on the gateway while it is in an un-activated state. Once activation completes, the HTTP port is disabled. If you are unable to connect port 80 (HTTP) on a newly deployed, not yet activated gateway, please verify your firewall rules. Alternatively, use the instructions to retrieve a key through the local console (https://docs.aws.amazon.com/storagegateway/latest/tgw/get-activation-key.html#using-local-console). Thank you

The simple answer is that you need two (2) KVM gateway instances running locally. One for S3 File and another Tape. If you want a volume gateway as well, you will need yet another local KVM Gateway instance. BTW, substitute KVM with 'your choice of virtual machine technology'.

Amazon Q lead me down the wrong path as it told me I could use the same KVM instance to add a tape gateway on the AWS console. So wrong.