29 breaking releases

new 0.31.1 Sep 20, 2023
0.30.0 Aug 24, 2023
0.28.0 May 24, 2023
0.25.0 Mar 30, 2023
0.0.0 May 7, 2021

#2239 in Network programming

Download history 2/week @ 2023-06-11 73/week @ 2023-06-18 6/week @ 2023-07-02 3/week @ 2023-07-09 2/week @ 2023-07-16 4/week @ 2023-07-23 21/week @ 2023-07-30 15/week @ 2023-08-06 33/week @ 2023-08-13 21/week @ 2023-08-20 72/week @ 2023-08-27 42/week @ 2023-09-03 3/week @ 2023-09-10 44/week @ 2023-09-17

162 downloads per month


17K SLoC


Please Note: The SDK is currently in Developer Preview and is intended strictly for feedback purposes only. Do not use this SDK for production workloads.

The Health API provides access to the Health information that appears in the Health Dashboard. You can use the API operations to get information about events that might affect your Amazon Web Services and resources.

You must have a Business, Enterprise On-Ramp, or Enterprise Support plan from Amazon Web Services Support to use the Health API. If you call the Health API from an Amazon Web Services account that doesn't have a Business, Enterprise On-Ramp, or Enterprise Support plan, you receive a SubscriptionRequiredException error.

For API access, you need an access key ID and a secret access key. Use temporary credentials instead of long-term access keys when possible. Temporary credentials include an access key ID, a secret access key, and a security token that indicates when the credentials expire. For more information, see Best practices for managing Amazon Web Services access keys in the Amazon Web Services General Reference.

You can use the Health endpoint health.us-east-1.amazonaws.com (HTTPS) to call the Health API operations. Health supports a multi-Region application architecture and has two regional endpoints in an active-passive configuration. You can use the high availability endpoint example to determine which Amazon Web Services Region is active, so that you can get the latest information from the API. For more information, see Accessing the Health API in the Health User Guide.

For authentication of requests, Health uses the Signature Version 4 Signing Process.

If your Amazon Web Services account is part of Organizations, you can use the Health organizational view feature. This feature provides a centralized view of Health events across all accounts in your organization. You can aggregate Health events in real time to identify accounts in your organization that are affected by an operational event or get notified of security vulnerabilities. Use the organizational view API operations to enable this feature and return event information. For more information, see Aggregating Health events in the Health User Guide.

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-health to your project, add the following to your Cargo.toml file:

aws-config = "0.56.1"
aws-sdk-health = "0.31.1"
tokio = { version = "1", features = ["full"] }

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

use aws_sdk_health as health;

async fn main() -> Result<(), health::Error> {
    let config = aws_config::load_from_env().await;
    let client = aws_sdk_health::Client::new(&config);

    // ... make some calls with the client


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


This project is licensed under the Apache-2.0 License.


~374K SLoC