DataSnapshots Object

When Truto actually read this object from the provider, in UTC ISO 8601 with the offset present. Not when the request was made and not a provider timestamp. Drives consumer staleness rules.

When the snapshot was taken.

Whether the snapshot is encrypted.

Truto's stable unified identifier for this object. Opaque; use provider_ref to address the object in the provider's own console or API.

Whether the snapshot is readable by any account on the provider.

Where the snapshot sits NOW. Never mapped from a provider source-region field, which means 'created in or copied from' and therefore names the origin rather than the current home for a cross-region copy. For block-volume snapshots AWS returns no location at all and the collector stamps on the region it queried.

The provider's own type string, unmodified -- for example 'AWS::S3::Bucket', 'aws_iam_role', 'Microsoft.Sql/servers'. Used for display and drill-down.

Which cloud this object was read from.

The provider's own unbroken identifier, passed through verbatim -- a full ARN, resource id or self-link. Never truncated, prefixed or normalised. This is the customer-facing key used to find the object in the console.

Which snapshot service this came from. A discriminator, because the underlying shapes use different field names for encryption and carry different sharing semantics -- one shared mapper reports every clustered snapshot as unencrypted.

The provider's own identifier for the snapshot.

The account that owns the source. Half of the production-data-in-test check. Neither AWS database snapshot type carries an owner field, so this is parsed out of the ARN.

The database or volume this snapshot was taken from.

Reference to the encryption key, where the snapshot is encrypted.

Where the object is. A compliance answer in its own right, not metadata. The literal string 'global' is emitted for genuinely global resources (for example IAM, or a GCP VPC network) rather than guessing a region. Never invented: where the provider does not return a location and none can be derived, the collector's queried region is used and that substitution is recorded in unreadable_fields.

The account-and-region-wide snapshot sharing posture. Changes how is_public must be read: under a block-all-sharing setting, an already-public snapshot is treated as private and is not publicly available, so reporting it as exposed is a false positive. Both the per-snapshot ACL and this regional posture are reported.

Raw data returned from the remote API call.

Accounts this snapshot has been explicitly shared with. An empty array means shared with nobody; null means the sharing attribute could not be read. On AWS this needs a separate per-snapshot call that has no batch form, making it the most expensive read in the collector.

Whether the per-snapshot sharing attribute was actually read. False means shared_with_accounts and is_public are inferred rather than confirmed, so an empty sharing list is never mistaken for a verified clean result.

Whether the snapshot was taken manually or by the provider's automated backup. Load-bearing: automated snapshots cannot be shared at all, so their sharing fields are true by construction rather than by a per-snapshot call.

The provider's own status string for the snapshot, verbatim.

Key-value pairs exactly as the customer set them: no case folding, no key or value normalisation, no merging of separate provider concepts. Present on every object because tags are the primary input for environment classification. An empty object means the object carries no tags; tags that could not be read are recorded in unreadable_fields instead.

Per-object list of the fields that could not be read, and why -- the brief section 8.4 answer, chosen over per-field sentinel values. Each entry is an object with 'field' (the property name on this resource), 'reason' (a reason code) and an optional human-readable 'detail'. Reason codes: not_supported_by_provider, not_configured, permission_denied, not_collected, collection_error, partially_collected. An empty array means every property on this object was read successfully. A property absent from this array and null in the payload means the provider genuinely returned no value, which is different from 'we could not look'.