Why is my AWS Storage Gateway file share stuck in a "creating" state?

There are several reasons why a Storage Gateway share might be stuck in the creating state:

  • The AWS Identity and Access Management (IAM) role given to the file share does not have the proper access. Storage Gateway requires access to upload files into your Amazon Simple Storage Service (Amazon S3) bucket. The IAM role that you use to create the share must have permissions on your Amazon S3 bucket. For more information, see Adding a File Share.
  • The IAM trust policy is not allowing the Storage Gateway service to assume the role. The Storage Gateway service must be allowed to assume the IAM role associated with the file share. For more information, see Managing Your File Gateway.
  • The AWS Security Token Service (AWS STS) is disabled for the region that the file gateway is activated in. For more information, see Activating and Deactivating AWS STS in an AWS Region.
  • There is an error in the S3 bucket name that occurred when the file share was created. For more information, see Rules for Bucket Naming.

For more information, see Troubleshooting File Share Issues.

Follow these instructions to create a file share with the proper access, and then verify that AWS STS is enabled.

  1. Open the AWS Storage Gateway console. In the navigation pane, choose File shares, and then choose your File share ID.
  2. Choose Actions, choose Delete file share, select the check box to confirm deletion, and then choose Delete.
  3. Open the IAM console. In the navigation pane, choose Account settings, and then, in Security Token Services Regions, verify that the region Status is Active for the location where you want to create the file share.
  4. From the Storage Gateway console, choose Create file share, select your Gateway, type a name in the Amazon S3 bucket field, and then choose Next.
  5. Under Review, accept the defaults, and then choose Create file share.
    Note: This process might take several minutes to complete.
  6. Choose your File share ID, and then, in the Details tab, note the sample mount commands for your OS distribution.

The file share is now enabled in the correct region with the proper access.

Note: If the file share is not available, check the S3 bucket policy to verify access. For more information, see Bucket Policy Examples.


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center.

Published: 2018-04-11