Messages and limitations of the Amazon EC2 connector

Message code list of AMAZONEC2 category
Exception messages of AMAZONEC2 category
Limitations of AMAZONEC2 category

Message code list of AMAZONEC2 category

The following message codes correspond to errors that occur in Amazon EC2 Connector.

AMAZONEC20000E

This message code is output when an undefined error occurs.

Cause	Solution
An undefined error occurred.	Check the error message or the help of the operation in which the error has occurred.

Corresponding error

None

AMAZONEC20001E

This message code is output when connection to Amazon EC2 fails.

Cause	Solution
The cause differs according to each error message.	Check whether the cause/solution of the error is described in "Exception messages" below.

Corresponding error

com.amazonaws.AmazonServiceException

AMAZONEC20002E

This message code is output when the endpoint settings is incorrect, or when some error occurred during communicating with Amazon EC2, such as connection timeout.

Cause	Solution
The cause differs according to each error message.	Check whether the cause/solution of the error is described in "Exception messages" below.

Corresponding error

com.amazonaws.AmazonClientException

AMAZONEC20003E

This message code is output when starting/stopping instances isn't completed within Timeout for the connection resource specified in Destination after the completion of sending a start/stop request.

Cause	Solution
After the completion of sending a start/stop request, starting/stopping instances wasn't completed within Timeout for the connection resource specified in Destination.	Check the Timeout settings for the connection resource specified in Destination.

Corresponding error

AmazonEC2OperationTimeoutException

Exception messages of AMAZONEC2 category

Operation environment

Notes

The behavior described in the help pages is subject to change depending on specification changes in the destination.

Start Instances

Specification limits

When starting multiple instances, if any single instance fails to start and an error occurs, start requests aren't issued for the other instances.
If "AmazonEC2OperationTimeoutException" is thrown, the start request for the instance has been completed. Although a runtime error occurs, the start processing is performed for the instance.

Notes

HTTPS is used in communication between Amazon EC2 and this connector.
Only instances whose state is "stopped" are started.
Only instances whose root device type is "ebs" are started.
Spot instances can't be started.

Stop Instances

Specification limits

When stopping multiple instances, if any single instance fails to stop and an error occurs, stop requests aren't issued for the other instances.
If "AmazonEC2OperationTimeoutException" is thrown, the stop request for the instance has been completed. Although a runtime error occurs, the stop processing is performed for the instance.

Notes

HTTPS is used in communication between Amazon EC2 and this connector.
Only instances whose state is "running" or "pending" are stopped.
Only instances whose root device type is "ebs" are stopped.
Spot instances can't be stopped.

Describe Instances

Specification limits

None.

Notes

HTTPS is used in communication between Amazon EC2 and this connector.

Exception name	Cause	Solution
AmazonEC2OperationTimeoutException Instance status has not been changed within <timeout> milliseconds.	After sending a start request, the starting of the instance isn't completed within Timeout for the connection resource specified in Destination.	Check Timeout for the connection resource specified in Destination.
Status Code: 400, AWS Request ID: XXXXXXXXXXXXXXXX, AWS Error Code: IncorrectInstanceState, AWS Error Message: The instance '<instance ID>' is not in a state from which it can be started.	The specified instance isn't in a state from which it can be started.	Check the state of the specified instance.
Status Code: 400, AWS Request ID: XXXXXXXXXXXXXXXX, AWS Error Code: InvalidInstanceID.Malformed, AWS Error Message: Invalid id: "<instance ID>"	The instance ID specified in Instance list/Instance ID (Name) is invalid.	Check the instance ID specified in Instance list/Instance ID (Name).
Status Code: 400, AWS Request ID: XXXXXXXXXXXXXXXX, AWS Error Code: InvalidInstanceID.NotFound, AWS Error Message: The instance ID '<instance ID>' does not exist	The instance with the instance ID specified in Instance list/Instance ID (Name) doesn't exist.	Check the instance ID specified in Instance list/Instance ID (Name).
Status Code: 400, AWS Request ID: XXXXXXXXXXXXXXXX, AWS Error Code: InvalidParameterValue, AWS Error Message: Invalid value '<IP address>' for PublicIp. Not a valid IPv4 address.	The IP address specified in Instance list/Elastic IP address is invalid.	Check the IP address specified in Instance list/Elastic IP address.
Status Code: 400, AWS Request ID: XXXXXXXXXXXXXXXX, AWS Error Code: AuthFailure, AWS Error Message: The address '<IP address>' does not belong to you.	The IP address specified in Instance list/Elastic IP address doesn't exist.	Check the IP address specified in Instance list/Elastic IP address.
Status Code: 400, AWS Request ID: XXXXXXXXXXXXXXXX, AWS Error Code: Resource.AlreadyAssociated, AWS Error Message: resource <Allocation ID> is already associated with associate-id <Association ID>	The IP address specified in Instance list/Elastic IP address is already associated to the instance in another VPC.	Check the IP address specified in Instance list/Elastic IP address.
Status Code: 400, AWS Request ID: XXXXXXXXXXXXXXXX, AWS Error Code: Resource.AlreadyAssociated, AWS Error Message: resource <instance ID> is already associated with public address <IP address>	The instance of the instance ID specified in Instance list/Instance ID (Name) is one in VPC and another IP address is already associated with that.	To associate a different IP address with the instance in VPC, remove the existing association temporarily.
Status Code: 400, AWS Request ID: XXXXXXXXXXXXXXXX, AWS Error Code: InvalidParameterCombination, AWS Error Message: You must specify an IP address when mapping to a non-VPC instance	The IP address specified in Instance list/Elastic IP address can't be associated with an instance not in VPC.	Check the IP address specified in Instance list/Elastic IP address.
Status Code: 400, AWS Request ID: XXXXXXXXXXXXXXXX, AWS Error Code: InvalidParameterCombination, AWS Error Message: You must specify an allocation id when mapping an address to a VPC instance	The IP address specified in Instance list/Elastic IP address can't be associated with an instance in VPC.	Check the IP address specified in Instance list/Elastic IP address.
AmazonEC2OperationTimeoutException Instance status has not been changed within <timeout> milliseconds.	After sending a stop request, the stopping of the instance isn't completed within Timeout for the connection resource specified in Destination.	Check Timeout for the connection resource specified in Destination.
Status Code: 400, AWS Request ID: XXXXXXXXXXXXXXXX, AWS Error Code: IncorrectInstanceState, AWS Error Message: The instance '<instance ID>' is not in a state from which it can be stopped.	The specified instance isn't in a state from which it can be stopped.	Check the state of the specified instance.
com.amazonaws.AmazonClientException Unable to execute HTTP request: Connect to ec2.amazonaws.com/ec2.amazonaws.com/xxx.xxx.xxx.xxx timed out	A request to Amazon EC2 couldn't be sent because the number of milliseconds specified in Timeout have elapsed.	Increase the number of milliseconds in Timeout, or check the connection status of the destination Amazon EC2.
com.amazonaws.AmazonClientException Unable to execute HTTP request: <endpoint>	Endpoint of the connection resource specified in Destination is incorrect.	Check the settings for the connection resource specified in Destination.
InvalidPropertyConfigurationException <Property name> is not specified.	<Property name> isn't specified.	Specify <property name>.
ResourceNotFoundException Resource definition could not be found. Name: []	Destination isn't specified.	Specify Destination.
ResourceNotFoundException Resource definition could not be found. Name: [<connection resource name>]	The resource definition selected in Destination isn't found.	Check the connection resource specified in Destination.