Why is my Storage Gateway file share stuck in the CREATING, UPDATING, or DELETING state?

4 minute read

My AWS Storage Gateway file share is stuck in the CREATING, UPDATING, or DELETING state.

Short description

The status of a file share summarizes the health of the file share. There are several reasons why a Storage Gateway file share might be stuck in the creating, updating, or deleting state:

  • The AWS Identity and Access Management (IAM) role given to the file share doesn't grant sufficient access. This IAM role must have permissions for your Amazon Simple Storage Service (Amazon S3) bucket. Additionally, the IAM role's trust policy must grant the Storage Gateway service permissions to assume the role.
  • AWS Security Token Service (AWS STS) is deactivated for the AWS Region that the file gateway is activated in.
  • There's an error in the S3 bucket name that's associated with the file share.
  • When you delete a file share from the file gateway, the share is removed from the associated S3 bucket. However, the contents of the bucket aren't deleted. If data was uploading to the bucket from the gateway when the share was deleted, then the delete process completes only after all the data is uploaded. During this process, the file share shows a DELETING status until after all the data has been uploaded.


Confirm that the Storage Gateway service has permissions for assuming the IAM role associated with the file share

1.    Open the IAM console.

2.    From the navigation pane, choose Roles.

3.    Choose the IAM role that's associated with your file share.

4.    Choose the Trust relationships tab.

5.    Confirm that Storage Gateway is listed as a trusted entity. If Storage Gateway isn't a trusted entity, choose Edit trust relationship, and then add the following policy:

  "Version": "2012-10-17",
  "Statement": [
      "Sid": "",
      "Effect": "Allow",
      "Principal": {
        "Service": "storagegateway.amazonaws.com"
      "Action": "sts:AssumeRole"

Prevent a file share stuck in the CREATING or UPDATING states

To avoid a file share stuck in the CREATING or UPDATING states, create a file share with sufficient access, and then verify that AWS STS is turned on:

1.    Open the Storage Gateway console.

2.    In the navigation pane, choose File shares, and then choose your File share ID.

3.    Choose Actions, choose Delete file share, select the check box to confirm deletion, and then choose Delete.

4.    Open the IAM console.

5.    In the navigation pane, choose Account settings.

6.    In Security Token Services Regions, verify that the Region Status is Active for the location where you want to create the file share.

7.    From the Storage Gateway console, choose Create file share.

8.    Select your Gateway, enter a name in the Amazon S3 bucket field, and then choose Next.

9.    Under Review, accept the defaults, and then choose Create file share.

Note: This process might take several minutes to complete.

10.    Choose your File share ID.

11.    In the Details tab, note the sample mount commands for your OS distribution.

Note: If the file share is not available, check the S3 bucket policy to verify access.

Delete a file share stuck in the DELETING state

Important: Follow these steps only if you don't want to wait for all in-progress uploads to finish writing to the S3 bucket.

1.    Open the Storage Gateway console.

  1.    From the navigation pane, choose File shares. Then, choose the file share ID that you want to delete.

3.    Choose the Details tab, and then review the This file share is being deleted message.

4.    Verify the ID of the file share in the message. Then, select the confirmation box.

Warning: You can't undo the force delete operation.

5.    Choose Force delete now.

Note: If you're using the new console, and the force delete option isn't available, then use the old console. Or you can use the AWS Command Line Interface (AWS CLI) delete-file-share command with force-delete set to true.

Related information

Create a file share

Troubleshooting file share issues

AWS OFFICIALUpdated a year ago