Struct ManagedMicrovmImageSummaryWire 

pub struct ManagedMicrovmImageSummaryWire {
    pub image_arn: String,
    pub created_at: f64,
    pub updated_at: Option<f64>,
}

ManagedMicrovmImageSummary: an ARN and two timestamps, and that is all the model declares.

Why a discovered base cannot construct a crate::control::BaseImage

crate::control::BaseImage pairs three things that must agree: the baseImageArn, the Dockerfile FROM that goes with it, and whether the image declares a WORKDIR. This shape carries the first and says nothing about the other two — no registry reference, no architecture, no working directory. So require_matching_from would have no FROM to compare a caller’s Dockerfile against, and require_workdir would have no answer to the question it exists to ask; both guards would have to be skipped for a discovered base, which is worse than not discovering one. The registry ref in particular is not derivable: al2023-1 pairs with public.ecr.aws/amazonlinux/amazonlinux:2023-minimal, and nothing in the ARN says so.

So this is informational only — surfaced by microvm doctor so a caller can see whether AWS has published a base this client does not know about, and never fed into a create request. Measured 2026-08-16: the listing returns exactly one item, so a client hardcoding al2023-1 is currently missing nothing.

Fields

image_arn: String

created_at: f64

updated_at: Option<f64>

Trait Implementations

impl Clone for ManagedMicrovmImageSummaryWire

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ManagedMicrovmImageSummaryWire

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ManagedMicrovmImageSummaryWire

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.