Breaking Changes:

• 🐛⚠ (smithy-rs#1847) Support Sigv4 signature generation on PowerPC 32 and 64 bit. This architecture cannot compile ring, so the implementation has been updated to rely on hamc + sha2 to achive the same result with broader platform compatibility and higher performance. We also updated the CI which is now running as many tests as possible against i686 and PowerPC 32 and 64 bit.

• ⚠ (smithy-rs#1225, smithy-rs#1918) <service>::Client::from_conf_conn has been removed since it's now possible to configure the connection from the shared and service configs. To update your code, pass connections to the http_connector method during config creation.

  Example

  before:

      let conf = aws_sdk_sts::Config::builder()
          // The builder has no defaults but setting other fields is omitted for brevity...
          .build();
      let (server, request) = capture_request(None);
      let client = aws_sdk_sts::Client::from_conf_conn(conf, server);
  

  after:

      let (server, request) = capture_request(None);
      let conf = aws_sdk_sts::Config::builder()
          // The builder has no defaults but setting other fields is omitted for brevity...
          .http_connector(server)
          .build();
      let client = aws_sdk_sts::Client::from_conf(conf);
  

• ⚠ (smithy-rs#1935) Removed re-export of aws_smithy_client::retry::Config from the middleware module.

• ⚠ (smithy-rs#1926, smithy-rs#1819) Several breaking changes have been made to errors. See the upgrade guide for more information.

• ⚠ (smithy-rs#1945) Generate enums that guide the users to write match expressions in a forward-compatible way. Before this change, users could write a match expression against an enum in a non-forward-compatible way:

  match some_enum {
      SomeEnum::Variant1 => { /* ... */ },
      SomeEnum::Variant2 => { /* ... */ },
      Unknown(value) if value == "NewVariant" => { /* ... */ },
      _ => { /* ... */ },
  }
  

  This code can handle a case for "NewVariant" with a version of SDK where the enum does not yet include SomeEnum::NewVariant, but breaks with another version of SDK where the enum defines SomeEnum::NewVariant because the execution will hit a different match arm, i.e. the last one. After this change, users are guided to write the above match expression as follows:

  match some_enum {
      SomeEnum::Variant1 => { /* ... */ },
      SomeEnum::Variant2 => { /* ... */ },
      other @ _ if other.as_str() == "NewVariant" => { /* ... */ },
      _ => { /* ... */ },
  }
  

  This is forward-compatible because the execution will hit the second last match arm regardless of whether the enum defines SomeEnum::NewVariant or not.

• ⚠ (smithy-rs#1984, smithy-rs#1496) Functions on aws_smithy_http::endpoint::Endpoint now return a Result instead of panicking.

• ⚠ (smithy-rs#1984, smithy-rs#1496) Endpoint::mutable now takes impl AsRef<str> instead of Uri. For the old functionality, use Endpoint::mutable_uri.

• ⚠ (smithy-rs#1984, smithy-rs#1496) Endpoint::immutable now takes impl AsRef<str> instead of Uri. For the old functionality, use Endpoint::immutable_uri.

• ⚠ (smithy-rs#1983, smithy-rs#2029) Implementation of the Debug trait for container shapes now redacts what is printed per the sensitive trait.

• ⚠ (smithy-rs#2065) SdkBody callbacks have been removed. If you were using these, please file an issue so that we can better understand your use-case and provide the support you need.

• ⚠ (smithy-rs#2063) AwsEndpointStage, a middleware which set endpoints and auth has been split into AwsAuthStage and SmithyEndpointStage. Related types have also been renamed.

• ⚠ (smithy-rs#1989) The Unit type for a Union member is no longer rendered. The serializers and parsers generated now function accordingly in the absence of the inner data associated with the Unit type.

New this release:

• 🎉 (smithy-rs#1225, smithy-rs#1918)

  The HTTP connector used when making requests is now configurable through `SdkConfig`.

  use std::time::Duration;
  use aws_smithy_client::{Client, hyper_ext};
  use aws_smithy_client::erase::DynConnector;
  use aws_smithy_client::http_connector::ConnectorSettings;
  use aws_types::SdkConfig;
  
  let https_connector = hyper_rustls::HttpsConnectorBuilder::new()
      .with_webpki_roots()
      .https_only()
      .enable_http1()
      .enable_http2()
      .build();
  
  let smithy_connector = hyper_ext::Adapter::builder()
      // Optionally set things like timeouts as well
      .connector_settings(
          ConnectorSettings::builder()
              .connect_timeout(Duration::from_secs(5))
              .build()
      )
      .build(https_connector);
  
  let sdk_config = aws_config::from_env()
      .http_connector(smithy_connector)
      .load()
      .await;
  
  let client = Client::new(&sdk_config);
  
  // When sent, this operation will go through the custom smithy connector instead of
  // the default HTTP connector.
  let op = client
      .get_object()
      .bucket("some-test-bucket")
      .key("test.txt")
      .send()
      .await
      .unwrap();
  

• 🎉 (aws-sdk-rust#641, smithy-rs#1892, @albe-rosado) Ability to add an inline policy or a list of policy ARNs to the AssumeRoleProvider builder.

• 🎉 (smithy-rs#2044, smithy-rs#371) Fixed and improved the request tracing span hierarchy to improve log messages, profiling, and debuggability.

• (smithy-rs#1890) Add test to exercise excluded headers in aws-sigv4.

• (smithy-rs#1801) Add test ensuring that a response will error if the response body returns an EOF before the entire body has been read.

• (smithy-rs#1923) Fix cargo audit issue on criterion.

• (smithy-rs#1918) Add to_vec method to aws_smithy_http::byte_stream::AggregatedBytes.

• 🐛 (smithy-rs#1957) It was possible in some cases to send some S3 requests without a required upload ID, causing a risk of unintended data deletion and modification. Now, when an operation has query parameters that are marked as required, the omission of those query parameters will cause a BuildError, preventing the invalid operation from being sent.

• 🐛 (smithy-rs#2018) Normalize URI paths per RFC3986 when constructing canonical requests, except for S3.

• (smithy-rs#2064, aws-sdk-rust#632) The SDK clients now default max idle connections to 70 (previously unlimited) to reduce the likelihood of hitting max file handles in AWS Lambda.

• (smithy-rs#2057, smithy-rs#371) Add more tracing events to signing and event streams

• (smithy-rs#2062) Log an info on credentials cache miss and adjust level of some credential tracing spans/events.

Contributors Thank you for your contributions! ❤

• @albe-rosado (aws-sdk-rust#641, smithy-rs#1892)

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! ❤

• @kastolars (smithy-rs#1747)
• @kevinpark1217 (aws-sdk-rust#625, smithy-rs#1822)

There were issues with release automation for this release, and it has been yanked from crates.io.

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.

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.

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

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! ❤

• @calavera (smithy-rs#1457)
• @joshtriplett (smithy-rs#1541)

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! ❤

• @jmklix (aws-sdk-rust#540)

New this release:

• 🐛 (aws-sdk-rust#547, smithy-rs#1458) Fix bug in profile file credential provider where a missing default profile lead to an unintended error.
• (smithy-rs#1421) Add Debug implementation to several types in aws-config
• 🐛 (aws-sdk-rust#558, smithy-rs#1478) Fix bug in retry policy where user configured timeouts were not retried. With this fix, setting with_call_attempt_timeout will lead to a retry when retries are enabled.
• 🐛 (aws-sdk-rust#554) Requests to Route53 that return ResourceIds often come with a prefix. When passing those IDs directly into another request, the request would fail unless they manually stripped the prefix. Now, when making a request with a prefixed ID, the prefix will be stripped automatically.

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! ❤

• @jszwedko (smithy-rs#1356)
• @petrosagg (smithy-rs#1404)

New this release:

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

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! ❤

• @ryansb (smithy-rs#1344)

Breaking Changes:

• ⚠ (aws-sdk-rust#490) Update all SDK and runtime crates to edition 2021

New this release:

• (smithy-rs#1262, @liubin) Fix link to Developer Guide in crate's README.md
• 🐛 (smithy-rs#1271, @elrob) Treat blank environment variable credentials (AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY) as missing instead of attempting to use them to sign requests.
• (aws-sdk-rust#479, smithy-rs#1296) Add support for configuring the session length in AssumeRoleProvider
• (smithy-rs#1296) Add caching to AssumeRoleProvider
• (smithy-rs#1300, @benesch) Add endpoint resolver to SdkConfig. This enables overriding the endpoint resolver for all services build from a single SdkConfig.

Contributors Thank you for your contributions! ❤

• @benesch (smithy-rs#1300)
• @elrob (aws-sdk-rust#1271)
• @liubin (smithy-rs#1262)

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:

• 🎉 (aws-sdk-rust#475, aws-sdk-rust#473) Enable presigning for S3 operations UploadPart and DeleteObject

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

New this release:

• (aws-sdk-rust#423) Added impl Into<http::request::Builder> for PresignedRequest and a conversion method for turning PresignedRequests into http::Requests.
• (smithy-rs#1087) Convert several info spans to debug in aws-config
• (smithy-rs#1118) SDK examples now come from awsdocs/aws-doc-sdk-examples rather than from smithy-rs

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.

New this release:

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

New this release:

• 🎉 (aws-sdk-rust#348) The docs for fluent builders now have easy links to their corresponding Input, Output, and Error structs
• 🎉 (smithy-rs#1051, aws-sdk-rust#4) Add support for SSO credentials
• 🐛🎉 (smithy-rs#1065, aws-sdk-rust#398, @nmoutschen) Silence profile credential warnings in Lambda environment
• 🐛 (aws-sdk-rust#405, smithy-rs#1083) Fixed paginator bug impacting EC2 describe VPCs (and others)

Contributors Thank you for your contributions! ❤

• @nmoutschen (aws-sdk-rust#398, smithy-rs#1065)

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)

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)

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)

This release was a version bump to fix a version number conflict on crates.io while releasing 0.1.0. The changes in 0.1.0 were: 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)
• :bug: Don't capture empty session tokens from the AWS_SESSION_TOKEN environment variable (aws-sdk-rust#316, smithy-rs#906)

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)
• :bug: Don't capture empty session tokens from the AWS_SESSION_TOKEN environment variable (aws-sdk-rust#316, smithy-rs#906)

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

• :warning: 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)
• :bug: Relaxed profile name validation to allow @ and other characters (smithy-rs#861, aws-sdk-rust#270)
• :bug: Fixed signing problem with S3 Control (smithy-rs#858, aws-sdk-rust#291)
• :tada: 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! :heart:

• @floric (smithy-rs#862)

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.

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)
• :bug: Fix bug that caused signing to fail for requests where the body length was <=9. (smithy-rs#845)

To upgrade to the new version of the SDK, update your version to 0.0.23-alpha:

[dependencies]
aws-sdk-s3 = "0.0.23-alpha"

New this week

• 🎉 The SDK is available on crates.io! This also means that generated docs are now searchable and hosted on https://docs.rs.
• :tada: Add support for AWS Glacier (smithy-rs#801)
• :tada: Add support for AWS Panorama
• :bug: 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)
• :bug: hyper::Error(IncompleteMessage) will now be retried (smithy-rs#815)
• :bug: 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)
• :bug: S3 request metadata signing now correctly trims headers fixing problems like this (smithy-rs#761)

Breaking Changes

• CredentialsError variants became non-exhaustive & now have struct bodies. 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. If you match on specific variants, you will also need to update your code to include ... (#781)
• The default credentials chain now returns CredentialsError::CredentialsNotLoaded instead of ProviderError when no credentials providers are configured.
• :warning: 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)