DateInterval
¶
Used by
-
AsyncCostExplorerClient-
Operations
-
get_cost_and_usage -
get_cost_and_usage_comparisons -
get_cost_and_usage_with_resources -
get_cost_categories -
get_cost_comparison_drivers -
get_cost_forecast -
get_dimension_values -
get_reservation_coverage -
get_reservation_utilization -
get_savings_plans_coverage -
get_savings_plans_utilization -
get_savings_plans_utilization_details -
get_tags -
get_usage_forecast
-
- Paginators
-
Operations
-
CostExplorerClient-
Operations
-
get_cost_and_usage -
get_cost_and_usage_comparisons -
get_cost_and_usage_with_resources -
get_cost_categories -
get_cost_comparison_drivers -
get_cost_forecast -
get_dimension_values -
get_reservation_coverage -
get_reservation_utilization -
get_savings_plans_coverage -
get_savings_plans_utilization -
get_savings_plans_utilization_details -
get_tags -
get_usage_forecast
-
- Paginators
-
Operations
Source code in docs_src/capo_cost_explorer/types/date_interval.py
end
instance-attribute
¶
end: YearMonthDay
The end of the time period. The end date is exclusive. For example, if end is 2017-05-01, Amazon Web Services retrieves cost and usage data from the start date up to, but not including, 2017-05-01.
start
instance-attribute
¶
start: YearMonthDay
The beginning of the time period. The start date is inclusive. For example, if start is 2017-01-01, Amazon Web Services retrieves cost and usage data starting at 2017-01-01 up to the end date. The start date must be equal to or no later than the current date to avoid a validation error.