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<Self, 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 — the manifest turns off its HTTP client, since reqwest is the one here, but keeps sso and credentials-process.

The provider is held rather than the resolved credentials: instance-profile creds are temporary, so each request re-resolves and picks up a rotation. That is why this is a provider field and not a Credentials field.

Trait Implementations

impl Debug for SignedTransport

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

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

Performs call, returning whatever the far side answered.