Skip to content

Latest commit

 

History

History
1444 lines (1179 loc) · 78.5 KB

CHANGELOG.md

File metadata and controls

1444 lines (1179 loc) · 78.5 KB

October 26th, 2022

Breaking Changes:

  • ⚠ (smithy-rs#1825) Bump MSRV to be 1.62.0.
  • ⚠ (smithy-rs#1740, smithy-rs#256) The SDK, by default, now times out if socket connect or time to first byte read takes longer than 3.1 seconds. There are a large number of breaking changes that come with this change that may affect you if you customize the client configuration at all. See the upgrade guide for information on how to configure timeouts, and how to resolve compilation issues after upgrading.

New this release:

  • 🎉 (aws-sdk-rust#237, smithy-rs#1770) It is now possible to programmatically customize the locations of the profile config/credentials files in aws-config: 
    use aws_config::profile::{ProfileFileCredentialsProvider, ProfileFileRegionProvider};
use aws_config::profile::profile_file::{ProfileFiles, ProfileFileKind};

let profile_files = ProfileFiles::builder()
    .with_file(ProfileFileKind::Credentials, "some/path/to/credentials-file")
    .build();
let credentials_provider = ProfileFileCredentialsProvider::builder()
    .profile_files(profile_files.clone())
    .build();
let region_provider = ProfileFileRegionProvider::builder()
    .profile_files(profile_files)
    .build();

let sdk_config = aws_config::from_env()
    .credentials_provider(credentials_provider)
    .region(region_provider)
    .load()
    .await;
  • 🐛 (smithy-rs#1740, smithy-rs#256) Setting connect/read timeouts with SdkConfig now works. Previously, these timeout config values were lost during connector creation, so the only reliable way to set them was to manually override the HTTP connector.
  • 🐛 (aws-sdk-rust#620, smithy-rs#1748) Paginators now stop on encountering a duplicate token by default rather than panic. This behavior can be customized by toggling the stop_on_duplicate_token property on the paginator before calling send.
  • 🐛 (smithy-rs#1747, @kastolars) The client Config now has getters for every value that it holds.
  • 🐛 (smithy-rs#1822, @kevinpark1217) Fix regression where connect_timeout and read_timeout fields are unused in the IMDS client
  • (aws-sdk-rust#625, @kevinpark1217) Ability to override the IMDS client in DefaultCredentialsChain
  • 🐛 (smithy-rs#1656) Fix aws-sigv4 canonical request formatting fallibility.
  • (smithy-rs#1890) Add test to exercise excluded headers in aws-sigv4.

Contributors Thank you for your contributions! ❤

October 13th, 2022

September 21st, 2022

Breaking Changes:

  • ⚠ (smithy-rs#1603, aws-sdk-rust#586) aws_config::RetryConfig no longer implements Default, and its new function has been replaced with standard.
  • ⚠ (smithy-rs#1603, aws-sdk-rust#586) Direct configuration of aws_config::SdkConfig now defaults to retries being disabled. If you're using aws_config::load_from_env() or aws_config::from_env() to configure the SDK, then you are NOT affected by this change. If you use SdkConfig::builder() to configure the SDK, then you ARE affected by this change and should set the retry config on that builder.
  • ⚠ (smithy-rs#1603, aws-sdk-rust#586) Client creation now panics if retries or timeouts are enabled without an async sleep implementation set on the SDK config. If you're using the Tokio runtime and have the rt-tokio feature enabled (which is enabled by default), then you shouldn't notice this change at all. Otherwise, if using something other than Tokio as the async runtime, the AsyncSleep trait must be implemented, and that implementation given to the config builder via the sleep_impl method. Alternatively, retry can be explicitly turned off by setting the retry config to RetryConfig::disabled(), which will result in successful client creation without an async sleep implementation.
  • ⚠ (smithy-rs#1715, smithy-rs#1717) ClassifyResponse was renamed to ClassifyRetry and is no longer implemented for the unit type.
  • ⚠ (smithy-rs#1715, smithy-rs#1717) The with_retry_policy and retry_policy functions on aws_smithy_http::operation::Operation have been renamed to with_retry_classifier and retry_classifier respectively. Public member retry_policy on aws_smithy_http::operation::Parts has been renamed to retry_classifier.

New this release:

  • 🎉 (smithy-rs#1647, smithy-rs#1112) Implemented customizable operations per RFC-0017.

    Before this change, modifying operations before sending them required using lower-level APIs:

    let input = SomeOperationInput::builder().some_value(5).build()?;

let operation = {
    let op = input.make_operation(&service_config).await?;
    let (request, response) = op.into_request_response();

    let request = request.augment(|req, _props| {
        req.headers_mut().insert(
            HeaderName::from_static("x-some-header"),
            HeaderValue::from_static("some-value")
        );
        Result::<_, Infallible>::Ok(req)
    })?;

    Operation::from_parts(request, response)
};

let response = smithy_client.call(operation).await?;

    Now, users may easily modify operations before sending with the customize method:

    let response = client.some_operation()
    .some_value(5)
    .customize()
    .await?
    .mutate_request(|mut req| {
        req.headers_mut().insert(
            HeaderName::from_static("x-some-header"),
            HeaderValue::from_static("some-value")
        );
    })
    .send()
    .await?;

  • 🐛 (smithy-rs#966, smithy-rs#1718) The AWS STS SDK now automatically retries IDPCommunicationError when calling AssumeRoleWithWebIdentity

  • 🐛 (aws-sdk-rust#303, smithy-rs#1717) The SdkError::ResponseError, typically caused by a connection terminating before the full response is received, is now treated as a transient failure and retried.

August 31st, 2022

Breaking Changes:

  • ⚠ (smithy-rs#1641) Refactor endpoint resolution internals to use aws_smithy_types::Endpoint internally. The public internal functions aws_endpoint::set_endpoint_resolver and aws_endpoint::get_endpoint_resolver were removed.
  • 🐛⚠ (smithy-rs#1274) Lossy converters into integer types for aws_smithy_types::Number have been removed. Lossy converters into floating point types for aws_smithy_types::Number have been suffixed with _lossy. If you were directly using the integer lossy converters, we recommend you use the safe converters. Before: 
    fn f1(n: aws_smithy_types::Number) {
    let foo: f32 = n.to_f32(); // Lossy conversion!
    let bar: u32 = n.to_u32(); // Lossy conversion!
}
    After: 
    fn f1(n: aws_smithy_types::Number) {
    use std::convert::TryInto; // Unnecessary import if you're using Rust 2021 edition.
    let foo: f32 = n.try_into().expect("lossy conversion detected"); // Or handle the error instead of panicking.
    // You can still do lossy conversions, but only into floating point types.
    let foo: f32 = n.to_f32_lossy();
    // To lossily convert into integer types, use an `as` cast directly.
    let bar: u32 = n as u32; // Lossy conversion!
}
  • ⚠ (smithy-rs#1669) Bump MSRV from 1.58.1 to 1.61.0 per our policy.

New this release:

  • 🎉 (smithy-rs#1598) Service configs are now generated with new accessors for:

    • Config::retry_config() - Returns a reference to the inner retry configuration.
    • Config::timeout_config() - Returns a reference to the inner timeout configuration.
    • Config::sleep_impl() - Returns a clone of the inner async sleep implementation.

    Previously, these were only accessible through SdkConfig.

  • 🐛🎉 (aws-sdk-rust#609) The AWS S3 GetObjectAttributes operation will no longer fail with an XML error.

August 8th, 2022

Breaking Changes:

  • ⚠ (smithy-rs#1157) Rename EventStreamInput to EventStreamSender
  • ⚠ (smithy-rs#1157) The type of streaming unions that contain errors is generated without those errors. Errors in a streaming union Union are generated as members of the type UnionError. Taking Transcribe as an example, the AudioStream streaming union generates, in the client, both the AudioStream type: 
    pub enum AudioStream {
    AudioEvent(crate::model::AudioEvent),
    Unknown,
}
    and its error type, 
    pub struct AudioStreamError {
    /// Kind of error that occurred.
    pub kind: AudioStreamErrorKind,
    /// Additional metadata about the error, including error code, message, and request ID.
    pub(crate) meta: aws_smithy_types::Error,
}
    AudioStreamErrorKind contains all error variants for the union. Before, the generated code looked as: 
    pub enum AudioStream {
    AudioEvent(crate::model::AudioEvent),
    ... all error variants,
    Unknown,
}
  • ⚠ (smithy-rs#1157) aws_smithy_http::event_stream::EventStreamSender and aws_smithy_http::event_stream::Receiver are now generic over <T, E>, where T is a streaming union and E the union's errors. This means that event stream errors are now sent as Err of the union's error type. With this example model: 
    @streaming union Event {
    throttlingError: ThrottlingError
}
@error("client") structure ThrottlingError {}
    Before: 
    stream! { yield Ok(Event::ThrottlingError ...) }
    After: 
    stream! { yield Err(EventError::ThrottlingError ...) }
    An example from the SDK is in transcribe streaming.

New this release:

  • 🎉 (smithy-rs#1482) The AWS SDK for Rust now supports additional checksum algorithms for Amazon S3. When getting and putting objects, you may now request that the request body be validated with a checksum. The supported algorithms are SHA-1, SHA-256, CRC-32, and CRC-32C.

    #[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let sdk_config = aws_config::load_from_env().await;
    let s3_client = aws_sdk_s3::Client::new(&sdk_config);
    let body = aws_sdk_s3::types::ByteStream::read_from()
        .path(std::path::Path::new("./path/to/your/file.txt"))
        .build()
        .await
        .unwrap();

    let _ = s3_client
        .put_object()
        .bucket("your-bucket")
        .key("file.txt")
        .body(body)
        // When using this field, the checksum will be calculated for you
        .checksum_algorithm(aws_sdk_s3::model::ChecksumAlgorithm::Crc32C)
        .send()
        .await?;

    let body = aws_sdk_s3::types::ByteStream::read_from()
        .path(std::path::Path::new("./path/to/your/other-file.txt"))
        .build()
        .await
        .unwrap();

    let _ = s3_client
        .put_object()
        .bucket("your-bucket")
        .key("other-file.txt")
        .body(body)
        // Alternatively, you can pass a checksum that you've calculated yourself. It must be base64
        // encoded. Also, make sure that you're base64 encoding the bytes of the checksum, not its
        // string representation.
        .checksum_crc32_c(aws_smithy_types::base64::encode(&A_PRECALCULATED_CRC_32_C_CHECKSUM[..]))
        .send()
        .await?;
}

  • 🎉 (smithy-rs#1571, smithy-rs#1385) SDK crate READMEs now include an example of creating a client

  • (smithy-rs#1573, smithy-rs#1569) Non-streaming struct members are now marked #[doc(hidden)] since they will be removed in the future

July 21st, 2022

New this release:

  • 🎉 (smithy-rs#1457, @calavera) Re-export aws_types::SdkConfig in aws_config

  • 🎉 (aws-sdk-rust#581) Add From<aws_smithy_client::erase::DynConnector> impl for aws_smithy_client::http_connector::HttpConnector

  • 🎉 (aws-sdk-rust#567) Updated SDK Client retry behavior to allow for a configurable initial backoff. Previously, the initial backoff (named r in the code) was set to 2 seconds. This is not an ideal default for services like DynamoDB that expect clients to quickly retry failed request attempts. Now, users can set quicker (or slower) backoffs according to their needs.

    #[tokio::main]
async fn main() -> Result<(), aws_sdk_dynamodb::Error> {
    let retry_config = aws_smithy_types::retry::RetryConfigBuilder::new()
        .max_attempts(4)
        .initial_backoff(Duration::from_millis(20));

    let shared_config = aws_config::from_env()
        .retry_config(retry_config)
        .load()
        .await;

    let client = aws_sdk_dynamodb::Client::new(&shared_config);

    // Given the 20ms backoff multiplier, and assuming this request fails 3 times before succeeding,
    // the first retry would take place between 0-20ms after the initial request,
    // the second retry would take place between 0-40ms after the first retry,
    // and the third retry would take place between 0-80ms after the second retry.
    let request = client
        .put_item()
        .table_name("users")
        .item("username", "Velfi")
        .item("account_type", "Developer")
        .send().await?;

    Ok(())
}

  • 🎉 (smithy-rs#1557, aws-sdk-rust#580) The imds::Client in aws-config now implements Clone

  • 🐛 (smithy-rs#1541, @joshtriplett) Fix compilation of aws-config with rustls and native-tls disabled. The ProviderConfig::with_tcp_connector method uses aws_smithy_client::hyper_ext, which only exists with the client-hyper feature enabled. Add a feature enabling that, and enable it by default.

  • (smithy-rs#1263) Add support for aws-chunked content encoding. Only single-chunk encoding is supported. Multiple chunks and chunk signing are not supported at this time.

  • (smithy-rs#1540) Until now, SDK crates have all shared the exact same version numbers. This changes with this release. From now on, SDK crates will only version bump if they have changes. Coincidentally, they may share the same version number for some releases since changes to the code generator will cause a version bump in all of them, but this should not be relied upon.

  • 🐛 (smithy-rs#1559, aws-sdk-rust#582) Remove warning for valid IMDS provider use-case

  • 🐛 (smithy-rs#1558, aws-sdk-rust#583) Only emit a warning about failing to expand a ~ to the home directory in a profile file's path if that path was explicitly set (don't emit it for the default paths)

  • (smithy-rs#1556) The sleep_impl methods on the SdkConfig builder are now exposed and documented.

Contributors Thank you for your contributions! ❤

v0.15.0 (June 29th, 2022)

Breaking Changes:

  • ⚠ (smithy-rs#932) Replaced use of pin-project with equivalent pin-project-lite. For pinned enum tuple variants and tuple structs, this change requires that we switch to using enum struct variants and regular structs. Most of the structs and enums that were updated had only private fields/variants and so have the same public API. However, this change does affect the public API of aws_smithy_http_tower::map_request::MapRequestFuture<F, E>. The Inner and Ready variants contained a single value. Each have been converted to struct variants and the inner value is now accessible by the inner field instead of the 0 field.

New this release:

  • 🐛 (aws-sdk-rust#560, smithy-rs#1487) Add a trailing slash to the URI `/latest/meta-data/iam/security-credentials/ when loading credentials from IMDS
  • (aws-sdk-rust#540, @jmklix) Add comments for docker settings needed when using this sdk

Contributors Thank you for your contributions! ❤

v0.14.0 (June 22nd, 2022)

New this release:

v0.13.0 (June 9th, 2022)

New this release:

  • 🎉 (smithy-rs#1390) Add method ByteStream::into_async_read. This makes it easy to convert ByteStreams into a struct implementing tokio:io::AsyncRead. Available on crate feature rt-tokio only.
  • 🎉 (smithy-rs#1356, @jszwedko) Add support for credential_process in AWS configs for fetching credentials from an external process.
  • (smithy-rs#1404, @petrosagg) Switch to RustCrypto's implementation of MD5.

Contributors Thank you for your contributions! ❤

v0.12.0 (May 13th, 2022)

New this release:

  • (smithy-rs#1352) Log a debug event when a retry is going to be peformed

0.11.0 (April 28th, 2022)

Breaking Changes:

  • ⚠ (smithy-rs#1318) Bump MSRV from 1.56.1 to 1.58.1 per our "two versions behind" policy.

New this release:

  • 🐛 (smithy-rs#1344, @ryansb) Suppress irrelevant $HOME expansion warning when running in a Lambda Extension

Contributors Thank you for your contributions! ❤

0.10.1 (April 14th, 2022)

Breaking Changes:

New this release:

Contributors Thank you for your contributions! ❤

0.9.0 (March 17, 2022)

Breaking Changes:

  • ⚠ (aws-sdk-rust#406) aws_types::config::Config has been renamed to aws_types::sdk_config::SdkConfig. This is to better differentiate it from service-specific configs like aws_sdk_s3::Config. If you were creating shared configs with aws_config::load_from_env(), then you don't have to do anything. If you were directly referring to a shared config, update your use statements and struct names.

    Before:

    use aws_types::config::Config;

fn main() {
    let config = Config::builder()
    // config builder methods...
    .build()
    .await;
}

    After:

    // We re-export this type from the root module so it's easier to reference
use aws_types::SdkConfig;

fn main() {
    let config = SdkConfig::builder()
    // config builder methods...
    .build()
    .await;
}

  • ⚠ (smithy-rs#724) Timeout configuration has been refactored a bit. If you were setting timeouts through environment variables or an AWS profile, then you shouldn't need to change anything. Take note, however, that we don't currently support HTTP connect, read, write, or TLS negotiation timeouts. If you try to set any of those timeouts in your profile or environment, we'll log a warning explaining that those timeouts don't currently do anything.

    If you were using timeouts programmatically, you'll need to update your code. In previous versions, timeout configuration was stored in a single TimeoutConfig struct. In this new version, timeouts have been broken up into several different config structs that are then collected in a timeout::Config struct. As an example, to get the API per-attempt timeout in previous versions you would access it with <your TimeoutConfig>.api_call_attempt_timeout() and in this new version you would access it with <your timeout::Config>.api.call_attempt_timeout(). We also made some unimplemented timeouts inaccessible in order to avoid giving users the impression that setting them had an effect. We plan to re-introduce them once they're made functional in a future update.

New this release:

0.8.0 (Februrary 24, 2022)

Breaking Changes:

  • ⚠ (smithy-rs#1216) aws-sigv4 no longer skips the content-length and content-type headers when signing with SignatureLocation::QueryParams

New this release:

  • 🎉 (smithy-rs#1220, aws-sdk-rust#462) Made it possible to change settings, such as load timeout, on the credential cache used by the DefaultCredentialsChain.
  • 🐛 (smithy-rs#1197) Fixed a bug that caused clients to eventually stop retrying. The cross-request retry allowance wasn't being reimbursed upon receiving a successful response, so once this allowance reached zero, no further retries would ever be attempted.
  • 🐛 (smithy-rs#1217, aws-sdk-rust#467) ClientBuilder helpers rustls() and native_tls() now return DynConnector so that they once again work when constructing clients with custom middleware in the SDK.
  • 🐛 (smithy-rs#1216, aws-sdk-rust#466) Fixed a bug in S3 that prevented the content-length and content-type inputs from being included in a presigned request signature. With this fix, customers can generate presigned URLs that enforce content-length and content-type for requests to S3.

0.7.0 (February 18th, 2022)

Breaking Changes:

  • ⚠ (smithy-rs#1144) The aws_config::http_provider module has been renamed to aws_config::http_credential_provider to better reflect its purpose.

  • ⚠ (smithy-rs#1144) Some APIs required that timeout configuration be specified with an aws_smithy_client::timeout::Settings struct while others required an aws_smithy_types::timeout::TimeoutConfig struct. Both were equivalent. Now aws_smithy_types::timeout::TimeoutConfig is used everywhere and aws_smithy_client::timeout::Settings has been removed. Here's how to migrate code your code that depended on timeout::Settings:

    The old way:

    let timeout = timeout::Settings::new()
    .with_connect_timeout(Duration::from_secs(1))
    .with_read_timeout(Duration::from_secs(2));

    The new way:

    // This example is passing values, so they're wrapped in `Option::Some`. You can disable a timeout by passing `None`.
let timeout = TimeoutConfig::new()
    .with_connect_timeout(Some(Duration::from_secs(1)))
    .with_read_timeout(Some(Duration::from_secs(2)));

  • ⚠ (smithy-rs#1144) MakeConnectorFn, HttpConnector, and HttpSettings have been moved from aws_config::provider_config to aws_smithy_client::http_connector. This is in preparation for a later update that will change how connectors are created and configured.

    If you were using these structs/enums, you can migrate your old code by importing them from their new location.

  • ⚠ (smithy-rs#1144) Along with moving HttpConnector to aws_smithy_client, the HttpConnector::make_connector method has been renamed to HttpConnector::connector.

    If you were using this method, you can migrate your old code by calling connector instead of make_connector.

  • ⚠ (smithy-rs#1085) Moved the following re-exports into a types module for all services:

    • aws_sdk_<service>::AggregatedBytes -> aws_sdk_<service>::types::AggregatedBytes
    • aws_sdk_<service>::Blob -> aws_sdk_<service>::types::Blob
    • aws_sdk_<service>::ByteStream -> aws_sdk_<service>::types::ByteStream
    • aws_sdk_<service>::DateTime -> aws_sdk_<service>::types::DateTime
    • aws_sdk_<service>::SdkError -> aws_sdk_<service>::types::SdkError

  • ⚠ (smithy-rs#1085) AggregatedBytes and ByteStream are now only re-exported if the service has streaming operations, and Blob/DateTime are only re-exported if the service uses them.

  • ⚠ (smithy-rs#1130) MSRV increased from 1.54 to 1.56.1 per our 2-behind MSRV policy.

  • ⚠ (smithy-rs#1132) Fluent clients for all services no longer have generics, and now use DynConnector and DynMiddleware to allow for connector/middleware customization. This should only break references to the client that specified generic types for it.

    If you customized the AWS client's connector or middleware with something like the following:

    let client = aws_sdk_s3::Client::with_config(
    aws_sdk_s3::client::Builder::new()
        .connector(my_custom_connector) // Connector customization
        .middleware(my_custom_middleware) // Middleware customization
        .default_async_sleep()
        .build(),
    config
);

    Then you will need to wrap the custom connector or middleware in DynConnector and DynMiddleware respectively:

    let client = aws_sdk_s3::Client::with_config(
    aws_sdk_s3::client::Builder::new()
        .connector(DynConnector::new(my_custom_connector)) // Now with `DynConnector`
        .middleware(DynMiddleware::new(my_custom_middleware)) // Now with `DynMiddleware`
        .default_async_sleep()
        .build(),
    config
);

    If you had functions that took a generic connector, such as the following:

    fn some_function<C, E>(conn: C) -> Result<()>
where
    C: aws_smithy_client::bounds::SmithyConnector<Error = E> + Send + 'static,
    E: Into<aws_smithy_http::result::ConnectorError>
{
    // ...
}

    Then the generics and trait bounds will no longer be necessary:

    fn some_function(conn: DynConnector) -> Result<()> {
    // ...
}

    Similarly, functions that took a generic middleware can replace the generic with DynMiddleware and remove their trait bounds.

New this release:

  • 🐛 (aws-sdk-rust#443) The ProfileFileRegionProvider will now respect regions set in chained profiles
  • (smithy-rs#1144) Several modules defined in the aws_config crate that used to be declared within another module's file have been moved to their own files. The moved modules are sts, connector, and default_providers. They still have the exact same import paths.
  • 🐛 (smithy-rs#1129) Fix some docs links not working because they were escaped when they shouldn't have been
  • (smithy-rs#1085) The Client and Config re-exports now have their documentation inlined in the service docs
  • 🐛 (smithy-rs#1180) Fixed example showing how to use hardcoded credentials in aws-types

0.6.0 (January 26, 2022)

New this release:

0.5.2 (January 20th, 2022)

New this release:

  • 🐛 (smithy-rs#1100) Internal: Update sync script to run gradle clean. This fixes an issue where codegen was not triggered when only properties changed.

v0.5.1 (January 19th, 2022)

New this release:

  • 🐛 (smithy-rs#1089) Fix dev-dependency cycle between aws-sdk-sso and aws-config

0.5.0 (January 19, 2022)

New this release:

Contributors Thank you for your contributions! ❤

v0.4.1 (January 10, 2022)

New this release:

  • 🐛 (smithy-rs#1050, @nmoutschen) Fix typos for X-Ray trace ID environment variable in aws_http::recursion_detection
  • 🐛 (smithy-rs#1054, aws-sdk-rust#391) Fix critical paginator bug where an empty outputToken lead to a never ending stream.

Contributors Thank you for your contributions! ❤

  • @nmoutschen (smithy-rs#1050)

0.4.0 (January 6th, 2022)

Breaking Changes:

  • ⚠ (smithy-rs#990) Codegen will no longer produce builders and clients with methods that take impl Into<T> except for strings and boxed types.
  • ⚠ (smithy-rs#961) The meta, environment, and dns Cargo feature flags were removed from aws-config. The code behind the dns flag is now enabled when rt-tokio is enabled. The code behind the meta and environment flags is always enabled now.
  • ⚠ (smithy-rs#1003) aws_http::AwsErrorRetryPolicy was moved to aws_http::retry::AwsErrorRetryPolicy.
  • ⚠ (smithy-rs#1017, smithy-rs#930) Simplify features in aws-config. All features have been removed from aws-config with the exception of: rt-tokio, rustls and native-tls. All other features are now included by default. If you depended on those features specifically, remove them from your features listing.

New this release:

  • 🎉 (aws-sdk-rust#47, smithy-rs#1006) Add support for paginators! Paginated APIs now include .into_paginator() and (when supported) .into_paginator().items() to enable paginating responses automatically. The paginator API should be considered in preview and is subject to change pending customer feedback.
  • (smithy-rs#712) We removed an example 'telephone-game' that was problematic for our CI. The APIs that that example demonstrated are also demonstrated by our Polly and TranscribeStreaming examples so please check those out if you miss it.
  • 🐛 (aws-sdk-rust#357) Generated docs should no longer contain links that don't go anywhere
  • (aws-sdk-rust#254, @jacco) Made fluent operation structs cloneable
  • (smithy-rs#973) Debug implementation of Credentials will print expiry in a human readable way.
  • 🐛 (smithy-rs#999, smithy-rs#143, aws-sdk-rust#344) Add Route53 customization to trim /hostedzone/ prefix prior to serialization. This fixes a bug where round-tripping a hosted zone id resulted in an error.
  • 🐛 (smithy-rs#998, aws-sdk-rust#359) Fix bug where ECS credential provider could not perform retries.
  • (smithy-rs#1003) Add recursion detection middleware to the default stack
  • (smithy-rs#1002, aws-sdk-rust#352) aws_types::Config is now Clone
  • (smithy-rs#670, @jacco) Example for Config builder region function added
  • (smithy-rs#1021, @kiiadi) Add function to aws_config::profile::ProfileSet that allows listing of loaded profiles by name.
  • 🐛 (smithy-rs#1046, aws-sdk-rust#384) Fix IMDS credentials provider bug where the instance profile name was incorrectly cached.

Contributors Thank you for your contributions! ❤

  • @jacco (aws-sdk-rust#254, smithy-rs#670)
  • @kiiadi (smithy-rs#1021)

v0.3.0 (December 15th, 2021)

Breaking Changes:

  • ⚠ (smithy-rs#930) If you directly depend on AWS or Smithy runtime crates (e.g., AWS crates not named aws-config or prefixed with aws-sdk-), the formerly default features from those crates must now be explicitly set in your Cargo.toml.

    Upgrade guide

    before after
    aws-smithy-async = "VERSION" aws-smithy-async = { version = "VERSION", features = ["rt-tokio"] }
    aws-smithy-client = "VERSION" aws-smithy-client = { version = "VERSION", features = ["client-hyper", "rustls", "rt-tokio"] }
    aws-smithy-http = "VERSION" aws-smithy-http = { version = "VERSION", features = ["rt-tokio"] }

  • ⚠ (smithy-rs#940) aws_hyper::Client which was just a re-export of aws_smithy_types::Client with generics set has been removed. If you used aws_hyper::Client or aws_hyper::Client::https() you can update your code to use aws_smithy_client::Builder::https().

  • ⚠ (smithy-rs#947) The features aws-hyper/rustls and aws-hyper/native-tls have been removed. If you were using these, use the identical features on aws-smithy-client.

  • ⚠ (smithy-rs#959, smithy-rs#934) aws-hyper::AwsMiddleware is now generated into generated service clients directly. If you used aws_hyper::Middleware, use ::middleware::DefaultMiddleware` instead.

New this release:

  • 🐛 (aws-sdk-rust#330) A bug that occurred when signing certain query strings has been fixed
  • 🐛 (smithy-rs#949, @a-xp) Fix incorrect argument order in the builder for LazyCachingCredentialsProvider
  • 🐛 (aws-sdk-rust#304) aws-config will now work as intended for users that want to use native-tls instead of rustls. Previously, it was difficult to ensure that rustls was not in use. Also, there is now an example of how to use native-tls and a test that ensures rustls is not in the dependency tree
  • 🐛 (aws-sdk-rust#317, smithy-rs#907) Removed inaccurate log message when a client was used without a sleep implementation, and improved context and call to action in logged messages around missing sleep implementations.
  • (smithy-rs#923) Use provided sleep_impl for retries instead of using Tokio directly.
  • (smithy-rs#920) Fix typos in module documentation for generated crates
  • 🐛 (aws-sdk-rust#301, smithy-rs#892) Avoid serializing repetitive xmlns attributes when serializing XML. This reduces the length of serialized requests and should improve compatibility with localstack.
  • 🐛 (smithy-rs#953, aws-sdk-rust#331) Fixed a bug where certain characters caused a panic during URI encoding.

Contributors Thank you for your contributions! ❤

  • @a-xp (smithy-rs#949)

v0.2.0 (December 2nd, 2021)

  • This release was a version bump to fix a version number conflict in crates.io

v0.1.0 (December 2nd, 2021)

New this release

  • Add docs.rs metadata section to all crates to document all features
  • Added a new example showing how to set all currently supported timeouts
  • Add a new check so that the SDK doesn't emit an irrelevant $HOME dir warning when running in a Lambda (aws-sdk-rust#307)
  • 🐛 Don't capture empty session tokens from the AWS_SESSION_TOKEN environment variable (aws-sdk-rust#316, smithy-rs#906)

v0.0.26-alpha (November 23rd, 2021)

Breaking Changes

  • RetryConfigBuilder::merge_with has been renamed to RetryConfigBuilder::take_unset_from
  • Credentials::from_keys is now behind a feature flag named hardcoded-credentials in aws-types. It is NOT secure to hardcode credentials into your application, and the credentials providers that come with the AWS SDK should be preferred. (smithy-rs#875, smithy-rs#317)
  • (aws-smithy-client): Extraneous pub use SdkSuccess removed from aws_smithy_client::hyper_ext. (smithy-rs#855)
  • The add_metadata function was removed from AwsUserAgent in aws-http. Use with_feature_metadata, with_config_metadata, or with_framework_metadata now instead. (smithy-rs#865)
  • Several breaking changes around aws_smithy_types::Instant were introduced by smithy-rs#849:
    • aws_smithy_types::Instant from was renamed to DateTime to avoid confusion with the standard library's monotonically nondecreasing Instant type.
    • DateParseError in aws_smithy_types has been renamed to DateTimeParseError to match the type that's being parsed.
    • The chrono-conversions feature and associated functions have been moved to the aws-smithy-types-convert crate.
      • Calls to Instant::from_chrono should be changed to: 
        use aws_smithy_types::DateTime;
use aws_smithy_types_convert::date_time::DateTimeExt;

// For chrono::DateTime<Utc>
let date_time = DateTime::from_chrono_utc(chrono_date_time);
// For chrono::DateTime<FixedOffset>
let date_time = DateTime::from_chrono_offset(chrono_date_time);
      • Calls to instant.to_chrono() should be changed to: 
        use aws_smithy_types_convert::date_time::DateTimeExt;

date_time.to_chrono_utc();
    • Instant::from_system_time and Instant::to_system_time have been changed to From trait implementations.
      • Calls to from_system_time should be changed to: 
        DateTime::from(system_time);
// or
let date_time: DateTime = system_time.into();
      • Calls to to_system_time should be changed to: 
        SystemTime::from(date_time);
// or
let system_time: SystemTime = date_time.into();
    • Several functions in Instant/DateTime were renamed:
      • Instant::from_f64 -> DateTime::from_secs_f64
      • Instant::from_fractional_seconds -> DateTime::from_fractional_secs
      • Instant::from_epoch_seconds -> DateTime::from_secs
      • Instant::from_epoch_millis -> DateTime::from_millis
      • Instant::epoch_fractional_seconds -> DateTime::as_secs_f64
      • Instant::has_nanos -> DateTime::has_subsec_nanos
      • Instant::epoch_seconds -> DateTime::secs
      • Instant::epoch_subsecond_nanos -> DateTime::subsec_nanos
      • Instant::to_epoch_millis -> DateTime::to_millis
    • The DateTime::fmt method is now fallible and fails when a DateTime's value is outside what can be represented by the desired date format.

New this week

  • ⚠️ MSRV increased from 1.53.0 to 1.54.0 per our 3-behind MSRV policy.
  • Conversions from aws_smithy_types::DateTime to OffsetDateTime from the time crate are now available from the aws-smithy-types-convert crate. (smithy-rs#849)
  • Fixed links to Usage Examples (smithy-rs#862, @floric)
  • Added missing features to user agent formatting, and made it possible to configure an app name for the user agent via service config. (smithy-rs#865)
  • 🐛 Relaxed profile name validation to allow @ and other characters (smithy-rs#861, aws-sdk-rust#270)
  • 🐛 Fixed signing problem with S3 Control (smithy-rs#858, aws-sd-rust#291)
  • 🎉 Timeouts for requests are now configurable. You can set a timeout for each individual request attempt or for all attempts made for a request. (smithy-rs#831)
    • SdkError now includes a variant TimeoutError for when a request times out (smithy-rs#885)
  • Improve docs on aws-smithy-client (smithy-rs#855)
  • Fix http-body dependency version (smithy-rs#883, aws-sdk-rust#305)

Contributions

Thank you for your contributions! ❤️

  • @floric (smithy-rs#862)

v0.0.25-alpha (November 11th, 2021)

No changes since last release except for version bumping since older versions of the AWS SDK were failing to compile with the 0.27.0-alpha.2 version chosen for some of the supporting crates.

v0.0.24-alpha (November 9th, 2021)

Breaking Changes

  • Members named builder on model structs were renamed to builder_value so that their accessors don't conflict with the existing builder() methods (smithy-rs#842)

New this week

  • Fix epoch seconds date-time parsing bug in aws-smithy-types (smithy-rs#834)
  • Omit trailing zeros from fraction when formatting HTTP dates in aws-smithy-types (smithy-rs#834)
  • Moved examples into repository root (aws-sdk-rust#181, smithy-rs#843)
  • Model structs now have accessor methods for their members. We recommend updating code to use accessors instead of public fields. A future release will deprecate the public fields before they are made private. (smithy-rs#842)
  • 🐛 Fix bug that caused signing to fail for requests where the body length was <=9. (smithy-rs#845)

v0.0.23-alpha (November 3rd, 2021)

New this week

  • 🎉 Add support for AWS Glacier (smithy-rs#801)
  • 🎉 Add support for AWS Panorama
  • 🐛 Fix native-tls feature in aws-config (aws-sdk-rust#265, smithy-rs#803)
  • Add example to aws-sig-auth for generating an IAM Token for RDS (smithy-rs#811, aws-sdk-rust#147)
  • 🐛 hyper::Error(IncompleteMessage) will now be retried (smithy-rs#815)
  • 🐛 S3 request metadata signing now correctly trims headers fixing problems like this (smithy-rs#761)
  • All unions (eg. dynamodb::model::AttributeValue) now include an additional Unknown variant. These support cases where a new union variant has been added on the server but the client has not been updated.
  • 🐛 Fix generated docs on unions like dynamodb::AttributeValue. (smithy-rs#826)

Breaking Changes

  • <operation>.make_operation(&config) is now an async function for all operations. Code should be updated to call .await. This will only impact users using the low-level API. (smithy-rs#797)

v0.0.22-alpha (October 20th, 2021)

Breaking Changes

  • CredentialsError variants became non-exhaustive. This makes them impossible to construct directly outside of the aws_types crate. In order to construct credentials errors, new methods have been added for each variant. Instead of CredentialsError::Unhandled(...), you should instead use CredentialsError::unhandled. Matching methods exist for all variants. (#781)
  • The default credentials chain now returns CredentialsError::CredentialsNotLoaded instead of ProviderError when no credentials providers are configured.
  • ⚠️ All Smithy runtime crates have been renamed to have an aws- prefix. This may require code changes:
    • Cargo.toml changes:
      • smithy-async -> aws-smithy-async
      • smithy-client -> aws-smithy-client
      • smithy-eventstream -> aws-smithy-eventstream
      • smithy-http -> aws-smithy-http
      • smithy-http-tower -> aws-smithy-http-tower
      • smithy-json -> aws-smithy-json
      • smithy-protocol-test -> aws-smithy-protocol-test
      • smithy-query -> aws-smithy-query
      • smithy-types -> aws-smithy-types
      • smithy-xml -> aws-smithy-xml
    • Rust use statement changes:
      • smithy_async -> aws_smithy_async
      • smithy_client -> aws_smithy_client
      • smithy_eventstream -> aws_smithy_eventstream
      • smithy_http -> aws_smithy_http
      • smithy_http_tower -> aws_smithy_http_tower
      • smithy_json -> aws_smithy_json
      • smithy_protocol_test -> aws_smithy_protocol_test
      • smithy_query -> aws_smithy_query
      • smithy_types -> aws_smithy_types
      • smithy_xml -> aws_smithy_xml

New this week

  • Moved the contents of aws-auth into the aws-http runtime crate (smithy-rs#783)
  • Fix instances where docs were missing in generated services and add #[warn_missing_docs] (smithy-rs#779)
  • Add tracing output for resolved AWS endpoint (smithy-rs#784)
  • Update AWS service models (smithy-rs#790)
  • Add support for the following Glacier customizations:
    • Set the ApiVersion header (smithy-rs#138, #787)

v0.0.21-alpha (October 15th, 2021)

New this week

  • Prepare crate manifests for publishing to crates.io (smithy-rs#755)
  • Add support for IAM Roles for tasks credential provider (smithy-rs#765, aws-sdk-rust#123)
  • All service crates now have generated README files (smithy-rs#766)
  • Update AWS service models (smithy-rs#772)
  • 🎉 Add support for Amazon Managed Grafana (smithy-rs#772)

v0.0.20-alpha (October 7, 2021)

Breaking changes

  • ⚠️ MSRV increased from 1.52.1 to 1.53.0 per our 3-behind MSRV policy.
  • SmithyConnector and DynConnector now return ConnectorError instead of Box<dyn Error>. If you have written a custom connector, it will need to be updated to return the new error type. (#744)
  • The DispatchError variant of SdkError now contains ConnectorError instead of Box<dyn Error> (#744).

New This Week

  • 🎉 Make retry behavior configurable
    • With env vars AWS_MAX_ATTEMPTS and AWS_RETRY_MODE
    • With ~/.aws/config settings max_attempts and retry_mode
    • By calling the with_retry_config method on a Config and passing in a RetryConfig
    • Only the Standard retry mode is currently implemented. Adaptive retry mode will be implemented at a later date.
    • For more info, see the AWS Reference pages on configuring these settings:
  • 🎉 Add presigned request support and examples for S3 GetObject and PutObject (smithy-rs#731, aws-sdk-rust#139)
  • 🎉 Add presigned request support and example for Polly SynthesizeSpeech (smithy-rs#735, aws-sdk-rust#139)
  • Add connect & HTTP read timeouts to IMDS, defaulting to 1 second
  • IO and timeout errors from Hyper can now be retried (#744)
  • 🐛 Fix error when receiving Cont event from S3 SelectObjectContent (smithy-rs#736)
  • 🐛 Fix bug in event stream receiver that could cause the last events in the response stream to be lost when using S3 SelectObjectContent (smithy-rs#736)
  • Updated EC2 code examples to include readme; refactored operations from main into separate functions.
  • Updated Transcribe code example to take an audio file as a command-line option and added readme.
  • Refactored API Gateway code example by moving operation out of main and into a separate function; added readme.
  • Updated Auto Scaling code example to move operation from main to separate function; added readme.
  • Updated AWS Config code examples to include a readme; added command-line options; added DeleteConfigurationRecorder, DeleteDeliveryChannel, ListConfigurationRecorders, ListDeliveryChannels, ListResources, ShowResourceHistory, and EnableConfig code examples.
  • 🎉 Add support for 6 new AWS services:
    • Wisdom
    • VoiceId
    • Account
    • KafkaConnect
    • OpenSearch
    • CloudControl

v0.0.19-alpha (September 24th, 2021)

New This Week

  • 🎉 IMDS support in the default credential provider chain (aws-sdk-rust#97)
  • 🎉 Add sts::AssumeRoleProvider to aws-config. This enables customers to invoke STS directly, instead of using it via ~/.aws/config. (smithy-rs#703, aws-sdk-rust#3)
  • Add IMDS client to aws-config (smithy-rs#701)
  • Add IMDS credential provider to aws-config (smithy-rs#709)
  • Add IMDS region provider to aws-config (smithy-rs#715, aws-sdk-rust#97)
  • Update event stream Receivers to be Send (aws-sdk-rust#224)
  • Add query param signing to the aws-sigv4 crate (smithy-rs#707)
  • 🐛 Update event stream Receivers to be Send (smithy-rs#702, #aws-sdk-rust#224)
  • 🐛 Fix panic when signing non-ASCII header values (smithy-rs#708, aws-sdk-rust#226)
  • Add an example that uses Polly, Transcribe, and S3 called telephone-game

Contributions

Thank you for your contributions! ❤️

  • @jonhoo (smithy-rs#703)

v0.0.18-alpha (September 14th, 2021)

  • 🎉 Add support for OpenSearch service & bring in other model updates (#todo)
  • Cleanup docs in aws-config

New This Week

  • 🐛 Fixes issue where Content-Length header could be duplicated leading to signing failure (aws-sdk-rust#220, smithy-rs#697)

  • Updated AutoScaling code examples to use asynchronous config; added readme file; tested on 0.0.17 bits

v0.0.17-alpha (September 2nd, 2021)

This release adds support for three commonly requested features:

  • More powerful credential chain
  • Support for constructing multiple clients from the same configuration
  • Support for Transcribe streaming and S3 Select

In addition, this overhauls client configuration which lead to a number of breaking changes. Detailed changes are inline.

Current Credential Provider Support:

  • Environment variables
  • Web Identity Token Credentials
  • Profile file support (partial)
    • Credentials
      • SSO
      • ECS Credential source
      • IMDS credential source
      • Assume role from source profile
      • Static credentials source profile
      • WebTokenIdentity provider
    • Region
  • IMDS
  • ECS

Upgrade Guide

If you use <sdk>::Client::from_env

from_env loaded region & credentials from environment variables only. Default sources have been removed from the generated SDK clients and moved to the aws-config package. Note that the aws-config package default chain adds support for profile file and web identity token profiles.

  1. Add a dependency on aws-config: 
    [dependencies]
aws-config = { git = "https://github.com/awslabs/aws-sdk-rust", tag = "v0.0.17-alpha" }
  2. Update your client creation code: 
    // `shared_config` can be used to construct multiple different service clients!
let shared_config = aws_config::load_from_env().await;
// before: <service>::Client::from_env();
let client = <service>::Client::new(&shared_config)

If you used <client>::Config::builder()

Config::build() has been modified to not fallback to a default provider. Instead, use aws-config to load and modify the default chain. Note that when you switch to aws-config, support for profile files and web identity tokens will be added.

  1. Add a dependency on aws-config:

    [dependencies]
aws-config = { git = "https://github.com/awslabs/aws-sdk-rust", tag = "v0.0.17-alpha" }

  2. Update your client creation code:

    fn before() {
  let region = aws_types::region::ChainProvider::first_try(<1 provider>).or_default_provider();
  let config = <service>::Config::builder().region(region).build();
  let client = <service>::Client::from_conf(&config);
}

async fn after() {
  use aws_config::meta::region::RegionProviderChain;
  let region_provider = RegionProviderChain::first_try(<1 provider>).or_default_provider();
  // `shared_config` can be used to construct multiple different service clients!
  let shared_config = aws_config::from_env().region(region_provider).load().await;
  let client = <service>::Client::new(&shared_config)
}

If you used aws-auth-providers

All credential providers that were in aws-auth-providers have been moved to aws-config. Unless you have a specific use case for a specific credential provider, you should use the default provider chain:

 let shared_config = aws_config::load_from_env().await;
 let client = <service>::Client::new(&shared_config);

If you maintain your own credential provider

AsyncProvideCredentials has been renamed to ProvideCredentials. The trait has been moved from aws-auth to aws-types. The original ProvideCredentials trait has been removed. The return type has been changed to by a custom future.

For synchronous use cases:

use aws_types::credentials::{ProvideCredentials, future};

#[derive(Debug)]
struct CustomCreds;
impl ProvideCredentials for CustomCreds {
  fn provide_credentials<'a>(&'a self) -> future::ProvideCredentials<'a>
    where
            Self: 'a,
  {
    // if your credentials are synchronous, use `::ready`
    // if your credentials are loaded asynchronously, use `::new`
    future::ProvideCredentials::ready(todo!()) // your credentials go here
  }
}

For asynchronous use cases:

use aws_types::credentials::{ProvideCredentials, future, Result};

#[derive(Debug)]
struct CustomAsyncCreds;
impl CustomAsyncCreds {
  async fn load_credentials(&self) -> Result {
    Ok(Credentials::from_keys("my creds...", "secret", None))
  }
}

impl ProvideCredentials for CustomCreds {
  fn provide_credentials<'a>(&'a self) -> future::ProvideCredentials<'a>
    where
            Self: 'a,
  {
    future::ProvideCredentials::new(self.load_credentials())
  }
}

Changes

Breaking Changes

  • Credential providers from aws-auth-providers have been moved to aws-config (smithy-rs#678)

  • AsyncProvideCredentials has been renamed to ProvideCredentials. The original non-async provide credentials has been removed. See the migration guide above.

  • <sevicename>::from_env() has been removed (#675). A drop-in replacement is available:

    1. Add a dependency on aws-config: 
      [dependencies]
aws-config = { git = "https://github.com/awslabs/aws-sdk-rust", tag = "v0.0.17-alpha" }
    2. Update your client creation code: 
      let client = <service>>::Client::new(&aws_config::load_from_env().await)

  • ProvideRegion has been moved to aws_config::meta::region::ProvideRegion. (smithy-rs#675)

  • aws_types::region::ChainProvider has been moved to aws_config::meta::region::RegionProviderChain (smithy-rs#675).

  • ProvideRegion is now asynchronous. Code that called provider.region() must be changed to provider.region().await.

  • <awsservice>::Config::builder() will not load a default region. To preserve previous behavior:

    1. Add a dependency on aws-config: 
      [dependencies]
aws-config = { git = "https://github.com/awslabs/aws-sdk-rust", tag = "v0.0.17-alpha" }
    2. let shared_config = aws_config::load_from_env().await;
let config = <service>::config::Builder::from(&shared_config).<other builder modifications>.build();

New this week

  • 🎉 Add profile file provider for region (smithy-rs#594, smithy-rs#682)
  • 🎉 Add support for shared configuration between multiple services (smithy-rs#673)
  • 🎉 Add support for Transcribe StartStreamTranscription and S3 SelectObjectContent operations (smithy-rs#667)
  • 🎉 Add support for new MemoryDB service (smithy-rs#677)
  • Improve documentation on collection-aware builders (smithy-rs#664)
  • Update AWS SDK models (smithy-rs#677)
  • 🐛 Fix sigv4 signing when request ALPN negotiates to HTTP/2. (smithy-rs#674)
  • 🐛 Fix integer size on S3 Size (smithy-rs#679, #209)
  • 🐛 Fix MediaLive response parsing issue (smithy-rs#683, #212)

v0.0.16-alpha (August 19th, 2021)

New This Week

  • 🎉 Add Chime Identity, Chime Messaging, and Snow Device Management support (smithy-rs#657)
  • 🎉 Add profile file credential provider implementation. This implementation currently does not support credential sources for assume role providers other than environment variables. (smithy-rs#640)
  • 🎉 Add support for WebIdentityToken providers via profile & environment variables. (smithy-rs#654)
  • 🐛 Fix name collision that occurred when a model had both a union and a structure named Result (smithy-rs#643)
  • 🐛 Fix STS Assume Role with WebIdentity & Assume role with SAML to support clients with no credentials provided (smithy-rs#652)
  • Update AWS SDK models (smithy-rs#657)
  • Add initial implementation of a default provider chain. (smithy-rs#650)

v0.0.15-alpha (August 11th, 2021)

This release primarily contains internal changes to runtime components & updates to AWS models.

Breaking changes

  • (smithy-rs#635) The config(), config_mut(), request(), and request_mut() methods on operation::Request have been renamed to properties(), properties_mut(), http(), and http_mut() respectively.

  • (smithy-rs#635) The Response type on Tower middleware has been changed from http::Response<SdkBody> to operation::Response. The HTTP response is still available from the operation::Response using its http() and http_mut() methods.

  • (smithy-rs#635) The ParseHttpResponse trait's parse_unloaded() method now takes an operation::Response rather than an http::Response<SdkBody>.

  • (smithy-rs#626) ParseHttpResponse no longer has a generic argument for the body type, but instead, always uses SdkBody. This may cause compilation failures for you if you are using Smithy generated types to parse JSON or XML without using a client to request data from a service. The fix should be as simple as removing <SdkBody> in the example below:

    Before:

    let output = <Query as ParseHttpResponse<SdkBody>>::parse_loaded(&parser, &response).unwrap();

    After:

    let output = <Query as ParseHttpResponse>::parse_loaded(&parser, &response).unwrap();

New This Week

  • The closure passed to async_provide_credentials_fn can now borrow values (smithy-rs#637)
  • Bring in the latest AWS models (smithy-rs#630)

v0.0.14-alpha (July 28th, 2021)

IoT Data Plane is now available! If you discover it isn't functioning as expected, please let us know!

This week also sees the addition of a robust async caching credentials provider. Take a look at the STS example to see how to use it.

To upgrade to the new release, update tag to v0.0.14-alpha:

[dependencies]
# e.g. S3:
aws-sdk-s3 = { git = "https://github.com/awslabs/aws-sdk-rust", tag = "v0.0.14-alpha" }

New This Week

  • 🎉 Add IoT Data Plane (smithy-rs#624)
  • 🎉 Add LazyCachingCredentialsProvider to aws-auth for use with expiring credentials, such as STS AssumeRole. Update STS example to use this new provider (smithy-rs#578, smithy-rs#595)
  • 🐛 Correctly encode HTTP Checksums using base64 instead of hex. Fixes #164. (smithy-rs#615)
  • Overhaul serialization/deserialization of numeric/boolean types. This resolves issues around serialization of NaN/Infinity and should also reduce the number of allocations required during serialization. (smithy-rs#618)
  • Update SQS example to clarify usage of FIFO vs. standard queues (#162, @trevorrobertsjr)

Contributions

Thank you for your contributions! ❤️

  • @trevorrobertsjr (#622)

v0.0.13-alpha (July 28th, 2021)

🎉 This week's release includes most of the remaining AWS services (269 in total!).

Breaking changes

  • test-util has been made an optional dependency and has moved from aws-hyper to smithy-http. If you were relying on aws_hyper::TestConnection, add smithy-client as a dependency and enable the optional test-util feature. This prunes some unnecessary dependencies on roxmltree and serde_json for most users. (smithy-rs#608)

New This Week

  • 🎉 Release all but four remaining AWS services! Glacier, IoT Data Plane, Timestream DB and Transcribe Streaming will be available in a future release. If you discover that a service isn't functioning as expected please let us know! (smithy-rs#607)
  • 🐛 Bugfix: Fix parsing bug where parsing XML incorrectly stripped whitespace (smithy-rs#590, #153)
  • We now run some tests on Windows (smithy-rs#594)
  • 🐛 Bugfix: Constrain RFC-3339 timestamp formatting to microsecond precision (smithy-rs#596, #152)

v0.0.12-alpha (July 19th, 2021)

This week we've added Autoscaling and fixed an S3 bug.

To update to the new release, change your tag to v0.0.12-alpha.

New this Week

  • 🎉 Add support for Autoscaling (#576, #582)
  • AsyncProvideCredentials now introduces an additional lifetime parameter, simplifying bridging it with #[async_trait] interfaces
  • Fix S3 bug when content type was set explicitly (aws-sdk-rust#131, #566, @eagletmt)

Contributions Thank you for your contributions! ❤️

  • @eagletmt (#566)

v0.0.11-alpha (July 6th, 2021)

This week, we've added AWS Config, EBS, Cognito, and Snowball. Projects that are implementing the ProvideCredentials trait will need to update their imports and should consider using the new async_provide_credentials_fn for async credential use-cases.

To update to the new release, change your tag to v0.0.11-alpha.

New this Week

  • ⚠️ Breaking Change: ProvideCredentials and CredentialError were both moved into aws_auth::provider when they were previously in aws_auth (#572)
  • 🎉 Add support for AWS Config (#570)
  • 🎉 Add support for EBS (#567)
  • 🎉 Add support for Cognito (#573)
  • 🎉 Add support for Snowball (#579, @landonxjames)
  • Make it possible to asynchronously provide credentials with async_provide_credentials_fn (#572, #577)
  • Improve RDS, QLDB, Polly, and KMS examples (#561, #560, #558, #556, #550)
  • Update AWS SDK models (#575)
  • 🐛 Bugfix: Fill in message from error response even when it doesn't match the modeled case format (#565)

Contributions

Thank you for your contributions! ❤️

  • landonxjames (#579)

v0.0.10-alpha (June 29th, 2021)

This week, we've added EKS, ECR and Cloudwatch. The JSON deserialization implementation has been replaced, please be on the lookout for potential issues and compile time improvements.

To update to the new release, change your tag to v0.0.10-alpha.

New this Week

  • 🎉 Add support for ECR (smithy-rs#557)
  • 🎉 Add support for Cloudwatch (smithy-rs#554)
  • 🎉 Add support for EKS (smithy-rs#553)
  • ⚠️ Breaking Change: httpLabel no longer causes fields to be non-optional. You may need to adapt code that uses models. (#537)
  • ⚠️ Breaking Change: Exception is not renamed to Error. Code may need to be updated to replace Error with Exception when naming error shapes.
  • ⚠️ Breaking Change: Models are now in strict pascal case including acronyms (e.g. dynamodb::model::{SSESpecification => SseSpecification})
  • Add more SES examples, and improve examples for Batch.
  • Improved error handling ergonomics: Errors now provide is_<variantname>() methods to simplify error handling
  • 🐛 Bugfix: Fix bug in create_multipart_upload: #127 (smithy-rs#531, @eagletmt)

Contributors

Thank you for your contributions! ❤️

  • @eagletmt (#531)

v0.0.9-alpha (June 22th, 2021)

This week, we've added CloudWatch Logs support and fixed several bugs in the generated S3 clients. There are breaking changes on builders and unions this week.

To upgrade to the new release, update tag to v0.0.9-alpha:

[dependencies]
# e.g. Cloudwatch Logs:
aws-sdk-cloudwatchlogs = { git = "https://github.com/awslabs/aws-sdk-rust", tag = "v0.0.9-alpha" }

New this Week

  • 🎉 Add support for CloudWatch Logs (smithy-rs#526)
  • ⚠️ Breaking Change: The set_* functions on generated Builders now always take an Option (smithy-rs#506)
  • ⚠️ Breaking Change: The as_* functions on unions now return Result rather than Option to clearly indicate what the actual value is (smithy-rs#527)
  • Add more S3 examples, and improve SNS, SQS, and SageMaker examples. Improve example doc comments (smithy-rs#490, smithy-rs#508, smithy-rs#509, smithy-rs#510, smithy-rs#511, smithy-rs#512, smithy-rs#513, smithy-rs#524)
  • Combine individual example packages into per-service example packages with multiple binaries (smithy-rs#481, smithy-rs#490)
  • 🐛 Bugfix: Show response body in trace logs for calls that don't return a stream (smithy-rs#514)
  • 🐛 Bugfix: Correctly parse S3's GetBucketLocation response (smithy-rs#516)
  • 🐛 Bugfix: Fix S3 ListObjectsV2 for prefixes containing tilde characters (smithy-rs#519)
  • 🐛 Bugfix: Fix S3 PutBucketLifecycle operation by adding support for the @httpChecksumRequired Smithy trait (smithy-rs#523)
  • 🐛 Bugfix: Correctly parse x-amz-expiration header on S3 GetObject responses (smithy-rs#525, @eagletmt)

Contributions

Thank you for your contributions! ❤️

  • @eagletmt (smithy-rs#525)
  • @zekisherif (smithy-rs#515)

v0.0.8-alpha (June 15th, 2021)

This week, we've added CloudFormation, SageMaker, EC2, and SES. More details below.

To upgrade to the new release, update tag to v0.0.8-alpha:

[dependencies]
# e.g. EC2:
aws-sdk-ec2 = { git = "https://github.com/awslabs/aws-sdk-rust", tag = "v0.0.8-alpha" }

New this Week

  • 🎉 Add support for CloudFormation (smithy-rs#500, @alistaim)
  • 🎉 Add support for SageMaker (smithy-rs#473, @alistaim)
  • 🎉 Add support for EC2 (smithy-rs#495)
  • 🎉 Add support for SES (smithy-rs#499)
  • Add support for the EC2 Query protocol (smithy-rs#475)
  • Refactor smithy/hyper connectors to enable client-specified middleware (smithy-rs#496, @jonhoo)
  • 🐛 Bugfix: RFC-3339 timestamp formatting is no longer truncating zeros off of the number of seconds (smithy-rs#479, smithy-rs#489)

Contributors:

  • @Doug-AWS
  • @jdisanti
  • @rcoh
  • @alistaim
  • @jonhoo

Thanks!!

v0.0.7-alpha (June 8th, 2021)

This week we’ve added MediaLive, MediaPackage, SNS, Batch, STS, RDS, RDSData, Route53, and IAM. More details below.

To upgrade to the new release, update tag to v0.0.7-alpha:

[dependencies]
# e.g. SNS:
aws-sdk-sns = { git = "https://github.com/awslabs/aws-sdk-rust", tag = "v0.0.7-alpha" }

New this Week

  • Breaking change: Some string enums have changed case:DynamoDB::{SSEStatus => SseStatus. SSEType => SseType}
  • 🎉 Add support for MediaLive and MediaPackage (#449, @alastaim)
  • 🎉 Add support for SNS (smithy-rs#450)
  • 🎉 Add support for Batch (smithy-rs#452)
  • 🎉 Add support for STS. Note: This does not include support for an STS-based credential provider although an example is provided. (smithy-rs#453)
  • 🎉 Add support for RDS (smithy-rs#455) and RDS-Data (smithy-rs#470). (@LMJW)
  • 🎉 Add support for Route53 (smithy-rs#457, @alistaim)
  • Support AWS Endpoints & Regions. With this update, regions like iam-fips and cn-north-1 will now resolve to the correct endpoint. Please report any issues with endpoint resolution. (smithy-rs#468)
  • 🐛 Primitive numerics and booleans are now filtered from serialization when they are 0 and not marked as required. This resolves issues where maxResults needed to be set even though it is optional & fixes errors during deserialization. (smithy-rs#451)
  • 🐛 S3 Head Object returned the wrong error when the object did not exist (smithy-rs#460, fixes smithy-rs#456)

Contributors:

  • @rcoh
  • @jdisanti
  • @alistaim
  • @LMJW

Thanks!

v0.0.6-alpha (June 1st, 2021)

New this week:

  • 🎉 Add support for SQS. SQS is our first service to use the awsQuery protocol. Please report any issues you may encounter.
  • 🎉 Add support for ECS.
  • Breaking Change: Refactored smithy_types::Error to be more flexible. Internal fields of Error are now private and can now be accessed accessor functions. (smithy-rs#426)
  • Breaking change: Smithy Enums do not implement serde::Serialize
  • ByteStream::from_path now accepts implications AsRef<Path> (@LMJW)
  • Add support for S3 extended request id (smithy-rs#429)
  • Add support for the awsQuery protocol. smithy-rs can now add support for all services except EC2.
  • Bugfix: Timestamps that fell precisely on minute boundaries were not properly formatted (smithy-rs#435)
  • Improve documentation for ByteStream & add pub use ByteStream to generated crates (smithy-rs#443)
  • Add support for EndpointPrefix needed for s3::WriteGetObjectResponse (smithy-rs#420)

Contributors:

  • @jdisanti
  • @rcoh
  • @LMJW

Thanks!

v0.0.5-alpha (May 25th, 2021)

You can install the new release by updating your dependencies to tag = "v0.0.5-alpha", e.g.

[dependencies]
aws-sdk-s3 = { git = "https://github.com/awslabs/aws-sdk-rust", tag = "v0.0.5-alpha" }

New This Week

  • 🎉 Add S3 support. S3 is the first protocol to use our new XML serializers which increases the likelihood of undiscovered issues. In addition, virtual addressing, dualstack and transfer acceleration are not currently supported. Please try it out and let us know if you run into any problems! (smithy-rs#398) 🎉
  • 🎉 Add support for SSM. SSM was prioritized based on your votes—Please keep voting for the services and feature most important to you! (smithy-rs#393) 🎉
  • Add request/response tracing. These can be enabled via tracing subscriber by setting: RUST_LOG='smithy_http_tower::dispatch=trace,smithy_http::middleware=trace' (smithy-rs#397)
  • Bugfix: Generated service docs were missing at the module level (smithy-rs#404)
  • ByteStream can now be created from Path and File via ByteStream::from_path (smithy-rs#412)
  • Example code now uses write_all_buf (#408, @lmjw)
  • The Authorization and x-amz-security-token headers are now marked as sensitive and will be omitted from logs even when full request/response tracing is enabled

And more: See the corresponding smithy-rs release.

Contributors:

  • @rcoh
  • @jdisanti
  • @LMJW

Thanks!

v0.0.4-alpha (May 18th, 2021)

You can install the new release by updating your dependencies to tag = "v0.0.4-alpha", e.g.

[dependencies]
aws-sdk-lambda = { git = "https://github.com/awslabs/aws-sdk-rust", tag = "v0.0.4-alpha" }

New this week:

  • 🎉 Add support for AWS Lambda (smithy-rs#361, @richardhboyd) 🎉
  • Generate docs automatically and host on GitHub Pages: https://awslabs.github.io/aws-sdk-rust/ (#81)
  • Add support for streaming request bodies. This is technically a breaking change but no currently generated AWS services expose this type. (smithy-rs#359)
  • Types represented by the Smithy Set type now generate Vec<T> in all cases. This is also technically breaking but not currently exposed. (smithy-rs#270)
  • Bugfix: The .message()field of errors will now look for both message and Message in the model (smithy-rs#374)
  • Add support for the AWS_REGION environment variable. (smithy-rs#362)
  • The request type generated by the fluent builders, e.g. dynamodb.list_tables() is now Debug (smithy-rs#377, @declanvk)

And more: See the corresponding smithy-rs release.

Contributors:

  • @richardhboyd
  • @declanvk
  • @jdisanti2019
  • @rcoh

Thanks!

v0.0.3-alpha (May 6th, 2021)

New this week:

  • Fix stack overflow in SdkBody Debug implementation
  • Upgrade to Smithy 1.7. This adds support for several new API Gateway endpoints
  • Add support for streaming response bodies. This is currently only used in Polly
  • Added code examples for Kinesis

More details in smithy-rs: https://github.com/awslabs/smithy-rs/releases/tag/v0.8