Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Cost
AndUsage Query Defines the parameters for retrieving Amazon Web Services cost and usage data. Includes specifications for metrics, time periods, granularity, grouping dimensions, and filtering conditions.
- Cost
Category Values Specifies the values and match options for cost category-based filtering in cost and usage queries.
- Dashboard
Reference Contains basic information about a dashboard, including its ARN, name, type, and timestamps.
- Date
Time Range Defines a time period with explicit start and end times for data queries.
- Date
Time Value Represents a point in time that can be specified as either an absolute date (for example, "2025-07-01") or a relative time period using ISO 8601 duration format (for example, "-P3M" for three months ago).
- Dimension
Values Specifies the values and match options for dimension-based filtering in cost and usage queries.
- Expression
Defines complex filtering conditions using logical operators (
AND
,OR
,NOT
) and various filter types.- Graph
Display Config Defines the visual representation settings for widget data, including the visualization type, styling options, and display preferences for different metric types.
- Group
Definition Specifies how to group cost and usage data.
- Reservation
Coverage Query Defines the parameters for querying Reserved Instance coverage data, including grouping options, metrics, and sorting preferences.
- Reservation
Utilization Query Defines the parameters for querying Reserved Instance utilization data, including grouping options and time granularity.
- Resource
Tag A key-value pair that can be attached to a dashboard for organization and management purposes.
- Savings
Plans Coverage Query Defines the parameters for querying Savings Plans coverage data, including metrics, grouping options, and time granularity.
- Savings
Plans Utilization Query Defines the parameters for querying Savings Plans utilization data, including time granularity and sorting preferences.
- Table
Display Config Struct Configuration structure for customizing the tabular display of widget data.
- TagValues
Specifies tag-based filtering options for cost and usage queries.
- Widget
A configurable visualization component within a dashboard that displays specific cost and usage metrics. Each widget can show data as charts or tables and includes settings for data querying, filtering, and visual presentation.
- Widget
Config Defines the complete configuration for a widget, including data retrieval settings and visualization preferences.
Enums§
- Dashboard
Type - When writing a match expression against
DashboardType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Date
Time Type - When writing a match expression against
DateTimeType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Dimension
- When writing a match expression against
Dimension
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Display
Config Defines how the widget's data should be visualized, including chart type, color schemes, axis configurations, and other display preferences.
- Granularity
- When writing a match expression against
Granularity
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Group
Definition Type - When writing a match expression against
GroupDefinitionType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Match
Option - When writing a match expression against
MatchOption
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Metric
Name - When writing a match expression against
MetricName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Query
Parameters Defines the data retrieval parameters for a widget.
- Visual
Type - When writing a match expression against
VisualType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.