Menu item missing from Storage Gateway Console

Hello,

I'm Mike with the SGW team. A couple of questions...

1. Sounds like you've deployed on EC2, were the previous deployments also done on EC2?
2. What region are you deploying in?
3. What kind of gateway were you trying to deploy? File? Volume/Tape? (They have different images.)

It almost sounds to me like you may have accidently deployed a Volume/Tape image or that you may have deployed from an older image. I suggest quickly deploying another gateway from the most recent image and verify you've chosen the correct type of gateway in the console.

If you continue to have issues, please let me know or open a support case with our Premium Support team. A developer support contract requires minimal outlay and can be turned back off, if desired, so you're only charged for the single month.

Hi Mike,

Thanks - Yes EC2 instance in eu-west-2. Previous ones are a mixture of EC2 in eu-west-2 and locally hosted ones on Hyper-V, all file gateways.

I have re-deployed as suggested. I think the issue was the image. I'd forgotten how I'd deployed the EC2 image previously, and just went to EC2 - launch image - searched for it and select the ami from the marketplace. Have re--deployed now using the launch ami option from the storage gateway page and it looks better! Have configured it the same as the previous one I have deployed and it's now passing connectivity tests.

While I have this open - a couple of other quick questions, if you don't mind;

1. Previous documentation suggests that these file gateways have to run through a web proxy if they dont have public internet access, and need to go through a storage gateway endpoint. Is still the case? Whilst playing with that marketplace image, it seemed to talk directly to an storage gateway endpoint, without a proxy.

2. Will the file storage gateways talk to S3 via the new interface endpoints for S3 (rather than gateway s3 endpoint)? if so do they just need to resolve s3.eu-west-2.amazonaws.com in DNS or do they need to be able to resolve individual bucket FQDNs?

Thanks again,

Martin

Hello, my responses are in-line below:

1. Previous documentation suggests that these file gateways have to run through a web proxy if they don't have public internet access, and need to go through a storage gateway endpoint. Is still the case? Whilst playing with that marketplace image, it seemed to talk directly to an storage gateway endpoint, without a proxy.
   ---Yes, this is still the case for on-premise file gateways that need to talk to a VPC endpoint for private communication. The HTTP proxy is still needed. For EC2-based file gateways, the http proxy is not required.

2. Will the file storage gateways talk to S3 via the new interface endpoints for S3 (rather than gateway s3 endpoint)? if so do they just need to resolve s3.eu-west-2.amazonaws.com in DNS or do they need to be able to resolve individual bucket FQDNs?
   --->The file gateway doesn't yet support the new interface endpoints for S3 but you are not the only customer asking this question and we're discussing internally how to best get it on our roadmap. Once implemented, the gateway would need to resolve and communicate with the S3 interface endpoint (along with the SGW endpoints).

Good questions, let me know if you have more. Mike H.