Skip to content

AWS Storage Gateway and File Share disappeared from web console overnight.

0

Yesterday, the Storage Gateway and its File Share showed up in the Storage Gateway web console and, today, they don't. The VM AWS Storage Gateway was never shutdown and still passes network, s3 connectivity and time is synched. Firewall ports are still open and no IPs have been changed. How do I add these back and make them stay? TiA!

asked a year ago215 views
2 Answers
2

It sounds like you might have the wrong region selected in the management console. You can find the region selection in the upper right-hand corner of the console screen. You can only see each gateway when the region where it resides in is selected.

EXPERT
answered a year ago
EXPERT
reviewed a year ago
  • Thank you for the quick reply! The wrong region was selected so I selected the correct region but they're still not showing up even after clicking refresh. Any other ideas?

  • The other alternative would be that you're in the wrong AWS account. You can see the 12-digit AWS account ID of the account where you're logged into also in the upper right-hand corner of the console. If you have multiple accounts, such as one for production and the other for non-production, or several accounts for different applications and infrastructure components, the Storage Gateway would only show in the combination of account and region where it resides. It can't disappear on its own, and we know it exists since you can still access it on the network.

  • I only have one AWS account (root), gateway, and file share. I am testing this at home and no one knows I'm doing it much less has access. Any other ideas?

  • I just recreated the gateway from scratch and created a file share. Green checks for both. This is the 3rd time now. Let's see what happens...

1

A gateway that was launched successfully can only disappear entirely from the account and region in which you created it by calling the DeleteGateway API of the AWS Storage Gateway service. I suggest you scan your CloudTrail logs to see if that API has been called recently. The logs in this view cover the past 90 days in the account and region.

In the management console, open the CloudTrail console. Make sure that you're in the same region where you created the gateway that disappeared. Open the "Event history" view in the console, and in the "lookup attributes" dropdown, choose "Event name" as the field to filter by. In the text box, enter "DeleteGateway" as the event to search for.

If any events show in the search results, you can click them open to see details on the API call. You'll see when it was called, if your credentials or some others were used, which IP address the call was made from, and in the userAgent field, you'll usually also see if the call was made with a web browser (via the console) or with the AWS command-line interface (CLI) or some other tool. Note that unlike most of the other fields, userAgent isn't fully reliable, because a bad actor or criminal could put any value they like in it, but if you called the API yourself, it's generally a useful indication of which client tool was used.

If no DeleteGateway events are shown in the CloudTrail event history, check if you can find CreateSMBFileShare or CreateNFSFileShare events, depending on whether you were creating Windows-compatible SMB file shares or NFS file shares more typically used on Linux. If those events also aren't shown, it's very likely that you deployed the gateway in a different region or account.

You can find all the Storage Gateways across all regions in your account by opening CloudShell in the console in your preferred/primary region and copying this set of statements and hitting Enter. It'll loop through all the regions that are enabled in your account and looks for storage gateways of any type in each one. If there are no gateways in the region, it'll output an empty "Gateways" array:

for region in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text)
do
	echo "** ${region}"
	aws storagegateway list-gateways --region ${region}
done
EXPERT
answered a year ago
EXPERT
reviewed a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.