New API Documentation - Developer Preview Available
We are excited to announce the developer preview of our new API documentation for AWS SDK for JavaScript v3. Please follow instructions on the landing page to leave us your feedback.
Class DeleteCustomRoutingAcceleratorCommandProtected
Delete a custom routing accelerator. Before you can delete an accelerator, you must disable it and remove all dependent resources
(listeners and endpoint groups). To disable the accelerator, update the accelerator to set Enabled to false.
When you create a custom routing accelerator, by default, Global Accelerator provides you with a set of two static IP addresses.
The IP
addresses are assigned to your accelerator for as long as it exists, even if you disable the accelerator and
it no longer accepts or routes traffic. However, when you delete an accelerator, you lose the
static IP addresses that are assigned to the accelerator, so you can no longer route traffic by using them.
As a best practice, ensure that you have permissions in place to avoid inadvertently deleting accelerators. You
can use IAM policies with Global Accelerator to limit the users who have permissions to delete an accelerator. For more information,
see Identity and access management in
the Global Accelerator Developer Guide.
Example
Use a bare-bones client and the command you need to make an API call.
The accelerator that you specified has a listener associated with it. You must remove all dependent resources from an
accelerator before you can delete it.
Delete a custom routing accelerator. Before you can delete an accelerator, you must disable it and remove all dependent resources (listeners and endpoint groups). To disable the accelerator, update the accelerator to set
Enabled
to false.When you create a custom routing accelerator, by default, Global Accelerator provides you with a set of two static IP addresses.
The IP addresses are assigned to your accelerator for as long as it exists, even if you disable the accelerator and it no longer accepts or routes traffic. However, when you delete an accelerator, you lose the static IP addresses that are assigned to the accelerator, so you can no longer route traffic by using them. As a best practice, ensure that you have permissions in place to avoid inadvertently deleting accelerators. You can use IAM policies with Global Accelerator to limit the users who have permissions to delete an accelerator. For more information, see Identity and access management in the Global Accelerator Developer Guide.
Example
Use a bare-bones client and the command you need to make an API call.
Param
DeleteCustomRoutingAcceleratorCommandInput
Returns
DeleteCustomRoutingAcceleratorCommandOutput
See
input
shape.response
shape.config
shape.Throws
AcceleratorNotDisabledException (client fault)
The accelerator that you specified could not be disabled.
Throws
AcceleratorNotFoundException (client fault)
The accelerator that you specified doesn't exist.
Throws
AssociatedListenerFoundException (client fault)
The accelerator that you specified has a listener associated with it. You must remove all dependent resources from an accelerator before you can delete it.
Throws
InternalServiceErrorException (server fault)
There was an internal error for Global Accelerator.
Throws
InvalidArgumentException (client fault)
An argument that you specified is invalid.
Throws
GlobalAcceleratorServiceException
Base exception class for all service exceptions from GlobalAccelerator service.