Module aws_sdk_snowball::types::error

source ·
Expand description

Error types that Amazon Import/Export Snowball can respond with.

Modules§

Structs§

  • ClusterLimitExceededException

    Job creation failed. Currently, clusters support five nodes. If you have fewer than five nodes for your cluster and you have more nodes to create for this cluster, try again and create jobs until your cluster has exactly five nodes.

  • ConflictException

    You get this exception when you call CreateReturnShippingLabel more than once when other requests are not completed.

  • Ec2RequestFailedException

    Your user lacks the necessary Amazon EC2 permissions to perform the attempted action.

  • InvalidAddressException

    The address provided was invalid. Check the address with your region's carrier, and try again.

  • InvalidInputCombinationException

    Job or cluster creation failed. One or more inputs were invalid. Confirm that the CreateClusterRequest$SnowballType value supports your CreateJobRequest$JobType, and try again.

  • InvalidJobStateException

    The action can't be performed because the job's current state doesn't allow that action to be performed.

  • InvalidNextTokenException

    The NextToken string was altered unexpectedly, and the operation has stopped. Run the operation without changing the NextToken string, and try again.

  • InvalidResourceException

    The specified resource can't be found. Check the information you provided in your last request, and try again.

  • KmsRequestFailedException

    The provided Key Management Service key lacks the permissions to perform the specified CreateJob or UpdateJob action.

  • ReturnShippingLabelAlreadyExistsException

    You get this exception if you call CreateReturnShippingLabel and a valid return shipping label already exists. In this case, use DescribeReturnShippingLabel to get the URL.

  • UnsupportedAddressException

    The address is either outside the serviceable area for your region, or an error occurred. Check the address with your region's carrier and try again. If the issue persists, contact Amazon Web Services Support.