Struct SignedTransport 

pub struct SignedTransport { /* private fields */ }

The real transport: resolve credentials, sign SigV4, send with reqwest.

Implementations

impl SignedTransport

pub async fn new(region: Region) -> Result<SignedTransport, Error>

Resolves the default credential chain for region and builds the HTTP client.

Why the chain rather than explicit keys

Because the credentials a developer actually has are in SSO, a credential process, or an instance profile, and re-implementing that resolution is how a client ends up working only on the machine it was written on. aws-config’s default chain is the whole reason to depend on it at all. Its HTTP client serves credential endpoints; reqwest sends the signed service requests. SSO and credential processes stay enabled.

The shared provider keeps the SDK identity cache: temporary credentials refresh before expiry, and concurrent requests share the same refresh.

Trait Implementations

impl Debug for SignedTransport

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Hand-written because a derived one would print the credentials provider, and the provider’s own Debug is not something this crate controls.

impl Transport for SignedTransport

fn region(&self) -> Option<&Region>

The service region, when known, for diagnostics about ambiguous denials. Custom transports may leave this unknown without changing their behavior.

fn resolve_credentials( &self, ) -> Pin<Box<dyn Future<Output = Result<(), Error>> + Send + '_>>

Resolves the credentials the next Transport::send would sign with, sending nothing to the service (BIND-15’s credentials check).

fn send( &self, call: Call, ) -> Pin<Box<dyn Future<Output = Result<Reply, Error>> + Send + '_>>

Performs call, returning whatever the far side answered.