56 releases (12 stable)

1.13.0 Feb 9, 2024
1.9.0 Dec 21, 2023
1.3.0 Nov 27, 2023
0.39.0 Nov 20, 2023
0.0.26-alpha Nov 24, 2021

#2319 in Network programming

Download history 90/week @ 2023-10-28 10/week @ 2023-11-04 57/week @ 2023-11-11 104/week @ 2023-11-18 261/week @ 2023-11-25 150/week @ 2023-12-02 73/week @ 2023-12-09 113/week @ 2023-12-16 168/week @ 2023-12-23 10/week @ 2023-12-30 29/week @ 2024-01-06 10/week @ 2024-01-13 78/week @ 2024-01-20 219/week @ 2024-01-27 34/week @ 2024-02-03 255/week @ 2024-02-10

586 downloads per month

Apache-2.0

495KB
7.5K SLoC

aws-sdk-route53recoverycluster

Welcome to the Routing Control (Recovery Cluster) API Reference Guide for Amazon Route 53 Application Recovery Controller.

With Route 53 ARC, you can use routing control with extreme reliability to recover applications by rerouting traffic across Availability Zones or Amazon Web Services Regions. Routing controls are simple on/off switches hosted on a highly available cluster in Route 53 ARC. A cluster provides a set of five redundant Regional endpoints against which you can run API calls to get or update the state of routing controls. To implement failover, you set one routing control to ON and another one to OFF, to reroute traffic from one Availability Zone or Amazon Web Services Region to another.

Be aware that you must specify a Regional endpoint for a cluster when you work with API cluster operations to get or update routing control states in Route 53 ARC. In addition, you must specify the US West (Oregon) Region for Route 53 ARC API calls. For example, use the parameter --region us-west-2 with AWS CLI commands. For more information, see Get and update routing control states using the API in the Amazon Route 53 Application Recovery Controller Developer Guide.

This API guide includes information about the API operations for how to get and update routing control states in Route 53 ARC. To work with routing control in Route 53 ARC, you must first create the required components (clusters, control panels, and routing controls) using the recovery cluster configuration API.

For more information about working with routing control in Route 53 ARC, see the following:

Getting Started

Examples are available for many services and operations, check out the examples folder in GitHub.

The SDK provides one crate per AWS service. You must add Tokio as a dependency within your Rust project to execute asynchronous code. To add aws-sdk-route53recoverycluster to your project, add the following to your Cargo.toml file:

[dependencies]
aws-config = { version = "1.1.5", features = ["behavior-version-latest"] }
aws-sdk-route53recoverycluster = "1.13.0"
tokio = { version = "1", features = ["full"] }

Then in code, a client can be created with the following:

use aws_sdk_route53recoverycluster as route53recoverycluster;

#[::tokio::main]
async fn main() -> Result<(), route53recoverycluster::Error> {
    let config = aws_config::load_from_env().await;
    let client = aws_sdk_route53recoverycluster::Client::new(&config);

    // ... make some calls with the client

    Ok(())
}

See the client documentation for information on what calls can be made, and the inputs and outputs for each of those calls.

Using the SDK

Until the SDK is released, we will be adding information about using the SDK to the Developer Guide. Feel free to suggest additional sections for the guide by opening an issue and describing what you are trying to do.

Getting Help

License

This project is licensed under the Apache-2.0 License.

Dependencies

~7–20MB
~258K SLoC