75 releases (31 stable)

new 1.31.0 Jun 11, 2024
1.29.0 May 29, 2024
1.19.0 Mar 26, 2024
1.9.0 Dec 21, 2023
0.0.26-alpha Nov 24, 2021

#1822 in Network programming

Download history 1621/week @ 2024-02-15 1719/week @ 2024-02-22 1879/week @ 2024-02-29 1994/week @ 2024-03-07 1524/week @ 2024-03-14 1560/week @ 2024-03-21 1202/week @ 2024-03-28 1939/week @ 2024-04-04 1824/week @ 2024-04-11 2243/week @ 2024-04-18 2246/week @ 2024-04-25 1691/week @ 2024-05-02 1849/week @ 2024-05-09 1773/week @ 2024-05-16 1897/week @ 2024-05-23 2019/week @ 2024-05-30

7,886 downloads per month
Used in 3 crates


113K SLoC


Config provides a way to keep track of the configurations of all the Amazon Web Services resources associated with your Amazon Web Services account. You can use Config to get the current and historical configurations of each Amazon Web Services resource and also to get information about the relationship between the resources. An Amazon Web Services resource can be an Amazon Compute Cloud (Amazon EC2) instance, an Elastic Block Store (EBS) volume, an elastic network Interface (ENI), or a security group. For a complete list of resources currently supported by Config, see Supported Amazon Web Services resources.

You can access and manage Config through the Amazon Web Services Management Console, the Amazon Web Services Command Line Interface (Amazon Web Services CLI), the Config API, or the Amazon Web Services SDKs for Config. This reference guide contains documentation for the Config API and the Amazon Web Services CLI commands that you can use to manage Config. The Config API uses the Signature Version 4 protocol for signing requests. For more information about how to sign a request with this protocol, see Signature Version 4 Signing Process. For detailed information about Config features and their associated actions or commands, as well as how to work with Amazon Web Services Management Console, see What Is Config in the Config Developer 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-config to your project, add the following to your Cargo.toml file:

aws-config = { version = "1.1.7", features = ["behavior-version-latest"] }
aws-sdk-config = "1.31.0"
tokio = { version = "1", features = ["full"] }

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

use aws_sdk_config as config;

async fn main() -> Result<(), config::Error> {
    let config = aws_config::load_from_env().await;
    let client = aws_sdk_config::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.


~271K SLoC