How do I troubleshoot errors when I create an Amazon EBS volume from a snapshot?
I receive errors when I try to create an Amazon Elastic Block Store (Amazon EBS) volume from a snapshot.
Resolution
Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshooting errors for the AWS CLI. Also, make sure that you're using the most recent AWS CLI version.
Choose a resolution based on the error message that you receive.
Tip: To identify detailed error information about failed CreateVolume API calls, review the AWS CloudTrail Event history. Filter by the event name CreateVolume to find error codes and messages.
Resolve the "UnauthorizedOperation" error
You receive the following error message when you don't have the required AWS Identity and Access Management (IAM) permissions to create volumes from snapshots:
"An error occurred (UnauthorizedOperation) when calling the CreateVolume operation: You are not authorized to perform this operation."
To create an Amazon EBS volume from a snapshot, your IAM user or role requires the following permissions:
- ec2:CreateVolume
- ec2:DescribeSnapshots
- kms:CreateGrant and kms:Decrypt for encrypted snapshots
To test permissions before you create the Amazon EBS volume, run the following create-volume AWS CLI command with the --dry-run parameter:
aws ec2 create-volume \ --snapshot-id SNAPSHOT-ID \ --availability-zone AVAILABILITY-ZONE \ --dry-run
Note: Replace SNAPSHOT-ID with your snapshot ID and AVAILABILITY-ZONE with your Availability Zone.
If dry-run succeeds, then you have the required permissions. If dry-run fails, then add the following permissions to your IAM policy:
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "ec2:CreateVolume", "ec2:DescribeSnapshots" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "kms:CreateGrant", "kms:Decrypt" ], "Resource": "arn:aws:kms:REGION:ACCOUNT-ID:key/KEY-ID" } ] }
Note: Replace REGION with your AWS Region, ACCOUNT-ID with your AWS account ID, and KEY-ID with your AWS Key Management Service (AWS KMS) key ID.
For more information, see Add and remove IAM identity permissions.
Resolve the "snapshot is archived" error
You receive the following error message when you try to create an Amazon EBS volume from a snapshot in the Archive tier:
"The snapshot is archived and cannot be used to create a volume."
To resolve this error, restore the snapshot to the Standard tier.
Complete the following steps:
- Open the Amazon EC2 console.
- In the navigation pane, choose Snapshots.
- Select the archived snapshot.
- Choose Actions, and then choose Restore snapshot from archive.
- Choose either a temporary restore, with a minimum 24 hours, or a permanent restore.
- Wait for the restore operation to complete.
Note: The restore operation can take 24-72 hours. - Create an Amazon EBS volume from the snapshot.
Note: You can incur additional costs when you restore snapshots from the Archive tier. For more information, see Archive Amazon EBS snapshots.
Resolve the "snapshot does not exist" error
You receive the following error message when you reference a snapshot from a different Region:
"The snapshot 'snap-EXAMPLE12345' does not exist."
To resolve this error, copy the snapshot to the destination Region.
Complete the following steps:
- To confirm the snapshot doesn't exist in the destination Region, run the following describe-snapshots AWS CLI command:
Note: Replace SNAPSHOT-ID with your snapshot ID and REGION with your Region.aws ec2 describe-snapshots \ --snapshot-ids SNAPSHOT-ID \ --region REGION
If the snapshot doesn't exist in the destination Region, then copy it using the following copy-snapshot AWS CLI command:
Note: Replace SOURCE-REGION with the source Region, SNAPSHOT-ID with your snapshot ID, and DESTINATION-REGION with the destination Region.aws ec2 copy-snapshot \ --source-region SOURCE-REGION \ --source-snapshot-id SNAPSHOT-ID \ --destination-region DESTINATION-REGION \ --description "Copy of snapshot" - Create an Amazon EBS volume from the copied snapshot in the destination Region.
Resolve the "snapshot does not exist" error for shared snapshots
You receive the "snapshot does not exist" error when you try to create an Amazon EBS volume from a shared snapshot that the source account deleted.
To resolve this error, complete the following steps:
- Verify the snapshot status in your account.
- Contact the owner of the source account to confirm the snapshot still exists. If the snapshot was deleted, then ask the owner to recreate and reshare the snapshot.
- Verify that the shared snapshot exists in the same Region where you want to create the Amazon EBS volume.
Resolve the "InvalidParameterCombination" error
You receive the following error message when you try to create an unencrypted Amazon EBS volume from an encrypted snapshot:
"An error occurred (InvalidParameterCombination) when calling the CreateVolume operation: EncryptedVolume parameter [false] is inconsistent with snapshot encryption state [true]"
To resolve this error, complete the following steps:
- To check whether an AWS KMS key encrypted the snapshot, run the following describe-snapshots AWS CLI command:
Note: Replace SNAPSHOT-ID with your snapshot ID.aws ec2 describe-snapshots \ --snapshot-ids SNAPSHOT-ID - Review the Encrypted field in the output. If the value is true, then you must create an encrypted Amazon EBS volume from this snapshot.
Resolve AWS KMS key authentication failures
You create an encrypted Amazon EBS volume from an encrypted snapshot, but the volume transitions to an unusable state and no longer appears in your account. This happens when AWS KMS key authentication fails asynchronously after the initial API call succeeds. For more information, see Amazon EBS encryption.
This failure occurs when:
- The AWS KMS key used to encrypt the snapshot is turned off or deleted.
- The AWS KMS key policy doesn't grant the required permissions to the user or role creating the volume.
- The AWS KMS key is in a different AWS account and cross-account access isn't configured.
To resolve this issue, complete the following steps:
- Verify that the AWS KMS key used to encrypt the snapshot is active. For more information, see How Amazon EBS uses AWS KMS.
- Confirm that your IAM user or role has kms:CreateGrant and kms:Decrypt permissions on the AWS KMS key.
- If the AWS KMS key belongs to a different account, then verify that the key policy allows cross-account access.
- Create the Amazon EBS volume again.
For more information, see Amazon EBS encryption examples.
Resolve volume size failures
Amazon EBS can't create a volume smaller than the original volume used to create the snapshot.
To resolve this issue, complete the following steps:
- To check the original volume size, run the following describe-snapshots AWS CLI command:
Note: Replace SNAPSHOT-ID with your snapshot ID.aws ec2 describe-snapshots \ --snapshot-ids SNAPSHOT-ID - Review the VolumeSize field in the output to identify the minimum volume size.
- Set the volume size to at least the same size as the original volume.
- Verify that the volume size is within the supported storage capacity for the volume type. For more information, see Amazon EBS volume types.
Resolve incomplete snapshot status
Volume creation fails when the snapshot is still in the pending or error state.
To resolve this issue, complete the following steps:
- To verify that the snapshot state, run the following describe-snapshots AWS CLI command:
Note: Replace SNAPSHOT-ID with your snapshot ID and REGION with your Region.aws ec2 describe-snapshots \ --snapshot-ids SNAPSHOT-ID \ --region REGION - Review the State field in the output. The value must be completed before you can create an Amazon EBS volume from the snapshot.
- Create the Amazon EBS volume again.
- Language
- English

This article was reviewed and updated on 2026-05-26.
Relevant content
asked 8 years ago
asked 4 years ago