API Error Codes
From Amazon Elastic Compute Cloud: 2008-12-01
API Error Codes
Overview
There are two types of error codes: client and server.
Client error codes suggest that the error was caused by
something the client did, such as an authentication failure or
an invalid AMI identifier. In the SOAP API, These error codes
are prefixed with Client. For example:
Client.AuthFailure. In the Query API, these
errors are accompanied by a 400-series HTTP response code.
Server error codes suggest a server-side issue caused the error
and should be reported. In the SOAP API,
these error codes are prefixed with Server.
For example: Server.Unavailable. In the
Query API, these errors are accompanied by a 500-series
HTTP response code.
Summary of Client Error Codes
| Error Code | Description | Notes |
|---|---|---|
AddressLimitExceeded
| User has the maximum number of allowed IP addresses. | Each user has an IP address limit. For new users, this limit is 5. If you need more than 5 Elastic IP addresses, please complete the |
AttachmentLimitExceeded
The limit on the number of Amazon EBS volumes attached to one instance has been exceeded.
AuthFailure
User not authorized.
You might be trying to run an AMI for which you do not have permission.
IncorrectState
Volume is in incorrect state
To attach to an instance, it must be in the 'available' state.
InstanceLimitExceeded
User has max allowed concurrent running instances.
Each user has a concurrent running instance limit. For
new users, this limit is 20. If you need more than 20 instances,
please complete the
Amazon EC2 Instance Request Form and your request will be considered.
InvalidAMIAttributeItemValueThe value of an item added to, or removed from, an image attribute is invalid.If you are specifying a userId, check that it is in the form of an AWS account ID.
InvalidAMIID.Malformed
Specified AMI ID is not valid.
InvalidAMIID.NotFound
Specified AMI ID does not exist.
InvalidAMIID.Unavailable
Specified AMI ID has been deregistered and is no longer available.
InvalidAttachment.NotFound
The instance cannot detach from a volume to which it is not attached.
InvalidDevice.InUse
The device to which you are trying to attach (i.e. /dev/sdh) is already in use on the instance.
InvalidInstanceID.Malformed
Specified instance ID is not valid.
InvalidInstanceID.NotFound
Specified instance ID does not exist.
InvalidKeyPair.NotFound
Specified key pair name does not exist.
InvalidKeyPair.Duplicate
Attempt to create a duplicate key pair.
InvalidGroup.NotFound
Specified group name does not exist.
InvalidGroup.Duplicate
Attempt to create a duplicate group.
InvalidGroup.InUse
Specified group cannot be deleted because it is in use.
InvalidGroup.Reserved
Specified group name is a reserved name.
InvalidManifest
Specified AMI has an unparsable Manifest.
InvalidParameterValue
The value supplied for a parameter was invalid.
Requests that could cause this error include (for example) supplying an invalid image attribute to the
DescribeImageAttribute request or an invalid version or encoding value
for the userData in a RunInstances request.
InvalidPermission.Duplicate
Attempt to authorize a permission that has already been authorized.
InvalidPermission.Malformed
Specified permission is invalid.
InvalidReservationID.Malformed
Specified reservation ID is invalid.
InvalidReservationID.NotFound
Specified reservation ID does not exist.
InvalidParameterCombination
RunInstances was called with minCount and maxCount set to 0 or minCount > maxCount.
InvalidSnapshotID.Malformed
The snapshot ID that was passed as an argument was malformed.
InvalidSnapshotID.NotFound
The specified snapshot does not exist.
InvalidUserID.MalformedThe user ID is neither in the form of an AWS account ID or one of the special values accepted
by the owner or executableBy flags in the DescribeImages call.
InvalidVolumeID.Malformed
The volume ID that was passed as an argument was malformed.
InvalidVolumeID.NotFound
The volume specified does not exist.
InvalidVolumeID.Duplicate
The volume already exists in the system.
InvalidVolumeID.ZoneMismatch
The specified volume ID and instance ID are in different Availability Zones.
InvalidZone.NotFound
The specified zone does not exist.
NonEBSInstance
The instance specified does not support EBS.
Please restart the instance and try again. This will ensure that the code is run on an instance with updated code.
PendingSnapshotLimitExceeded
The limit on the number of Amazon EBS snapshots in the pending state has been exceeded.
SnapshotLimitExceeded
The limit on the number of Amazon EBS snapshots has been exceeded.
UnknownParameter
An unknown or unrecognized parameter was supplied.
Requests that could cause this error include supplying a
misspelled parameter or a parameter that is not supported
for the specified API version.
VolumeLimitExceeded
The limit on the number of Amazon EBS volumes has been exceeded.
Summary of Server Error Codes
| Error Code | Description | Notes |
|---|---|---|
InternalError
|
Internal Error. | This error should not occur. If it does, please try to reproduce it and let us know by posting a message on the AWS forums. |
InsufficientAddressCapacity
|
Not enough available addresses to satisfy your minimum request. | Reduce the number of addresses you are requesting or wait for additional capacity to become available. |
InsufficientInstanceCapacity
|
Not enough available instances to satisfy your minimum request. | Reduce the number of instances in your request or wait for additional capacity to become available. |
Unavailable
|
The server is overloaded and cannot handle the request. |