Cost Explorer paginators

[HectorBst]

Describe the feature

Add Paginators for CostExplorer operations:

• get_anomalies
• get_anomaly_monitors
• get_anomaly_subscriptions
• get_cost_and_usage
• get_cost_and_usage_with_resources
• get_cost_categories
• get_dimension_values
• get_reservation_coverage
• get_reservation_purchase_recommendation
• get_reservation_utilization
• get_rightsizing_recommendation
• get_savings_plans_coverage
• get_savings_plans_purchase_recommendation
• get_savings_plans_utilization_details
• get_tags
• list_commitment_purchase_analyses
• list_cost_allocation_tag_backfill_history
• list_cost_allocation_tags
• list_cost_category_definitions
• list_savings_plans_purchase_recommendation_generation

Use Case

While I was looking for a paginator for the get_cost_and_usage operation in CostExplorer (ce), I noticed that there was none. I think that's a lack, unless there's a reason why there's no need for paginators for the CostExplorer service?

My first need was for get_cost_and_usage, then maybe get_cost_and_usage_with_resources, get_cost_categories and get_tags, but if I'm right there are at least 20 operations that could get a paginator in CostExplorer (listed above).

Proposed Solution

Add paginators in the paginators-1.json of CostExplorer, to generate them.

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

SDK version used

1.35.90

Environment details (OS name and version, etc.)

Linux and Windows, Python 3.12

[RyanFitzSimmonsAK]

Hi @HectorBst, thanks for reaching out. I've reached out to the service team with a feature request to implement these paginators. However, a few of these actually do already exist.

get_savings_plans_coverage
get_savings_plans_utilization_details
list_cost_allocation_tag_backfill_history
list_cost_allocation_tags
list_cost_category_definitions

These paginators are modeled, but are missing a field that Boto3 requires. I've reported this bug to the service team as well, and will leave this issue open to track it. Thanks!

Ticket # for internal use : P186088655