Module aws_sdk_budgets::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS Budgets can respond with.

Structs

• Action

  A budget action resource.

• ActionHistory

  The historical records for a budget action.

• ActionHistoryDetails

  The description of the details for the event.

• ActionThreshold

  The trigger threshold of the action.

• AutoAdjustData

  The parameters that determine the budget amount for an auto-adjusting budget.

• Budget

  Represents the output of the CreateBudget operation. The content consists of the detailed metadata and data file information, and the current status of the budget object.

• BudgetNotificationsForAccount

  The budget name and associated notifications for an account.

• BudgetPerformanceHistory

  A history of the state of a budget at the end of the budget's specified time period.

• BudgetedAndActualAmounts

  The amount of cost or usage that you created the budget for, compared to your actual costs or usage.

• CalculatedSpend

  The spend objects that are associated with this budget. The actualSpend tracks how much you've used, cost, usage, RI units, or Savings Plans units and the forecastedSpend tracks how much that you're predicted to spend based on your historical usage profile.

• CostTypes

  The types of cost that are included in a COST budget, such as tax and subscriptions.

• Definition

  Specifies all of the type-specific parameters.

• HistoricalOptions

  The parameters that define or describe the historical data that your auto-adjusting budget is based on.

• IamActionDefinition

  The Identity and Access Management (IAM) action definition details.

• Notification

  A notification that's associated with a budget. A budget can have up to ten notifications.

• NotificationWithSubscribers

  A notification with subscribers. A notification can have one SNS subscriber and up to 10 email subscribers, for a total of 11 subscribers.

• ResourceTag

  The tag structure that contains a tag key and value.

• ScpActionDefinition

  The service control policies (SCP) action definition details.

• Spend

  The amount of cost or usage that's measured for a budget.

• SsmActionDefinition

  The Amazon Web Services Systems Manager (SSM) action definition details.

• Subscriber

  The subscriber to a budget notification. The subscriber consists of a subscription type and either an Amazon SNS topic or an email address.

• TimePeriod

  The period of time that's covered by a budget. The period has a start date and an end date. The start date must come before the end date. There are no restrictions on the end date.

Enums

• ActionStatus
  When writing a match expression against ActionStatus, 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.
• ActionSubType
  When writing a match expression against ActionSubType, 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.
• ActionType
  When writing a match expression against ActionType, 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.
• ApprovalModel
  When writing a match expression against ApprovalModel, 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.
• AutoAdjustType
  When writing a match expression against AutoAdjustType, 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.
• BudgetType
  When writing a match expression against BudgetType, 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.
• ComparisonOperator
  When writing a match expression against ComparisonOperator, 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.
• EventType
  When writing a match expression against EventType, 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.
• ExecutionType
  When writing a match expression against ExecutionType, 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.
• NotificationState
  When writing a match expression against NotificationState, 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.
• NotificationType
  When writing a match expression against NotificationType, 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.
• SubscriptionType
  When writing a match expression against SubscriptionType, 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.
• ThresholdType
  When writing a match expression against ThresholdType, 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.
• TimeUnit
  When writing a match expression against TimeUnit, 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.