Skip to main content

EC2 AMI Restore Fails with Error "More than 50 Tags Specified"

EC2 AMI Restore Fails with Error "More than 50 Tags Specified"

Updated this week

Problem Description

When attempting to restore an EC2 AMI with less than 50 tags( visible tags in Druva CloudRanger), the restore operation fails still failed with the following AWS error:

"status_message": "More than 50 tags specified."

"status_code": "InvalidParameterValue"

Cause

Although the AMI appears to have less than 50 tags in the JSON file and CloudRanger console, the actual number of tags being passed during restore exceeds AWS’s maximum limit of 50 tags per resource. There were four default tags(not appear in Cloud ranger console) added by Cloudranger while restoring the EC2

The following 4 tags are automatically added by Druva CloudRanger at the time of restore:

  • craccountname

  • craction

  • crcreatedby

  • Created at

Additionally, the backup policy adds the following 3 default tags to each recovery point:

  • Created by policy id

  • Created by policy

  • Created by application

This brings the total to 7 additional tags, which, when combined with the 45+ existing tags, totals 52 tags, exceeding the AWS limit.

Resolution/Recommendation:

To avoid hitting the AWS 50-tag limit during EC2 AMI restores:

  • Review the total tag count, including:

    • User-defined tags

    • Auto-added CloudRanger tags (4)

    • Policy-related tags (3)

  • Remove unnecessary or empty tags from the recovery point before initiating a restore.

  • Optionally remove policy-related tags (Created by policy id, Created by policy, Created by application) during the restore process, if they are not required.

Additional Notes

AWS imposes a hard limit of 50 tags per resource. Exceeding this during restore operations will result in a failure. This is a platform limitation and cannot be overridden.

Did this answer your question?