Module types

Module types 

Source
Expand description

Data structures used by operation inputs/outputs.

Modules§

builders
Builders
error
Error types that Compute Optimizer Automation can respond with.

Structs§

AccountInfo

Contains information about an Amazon Web Services account's enrollment and association status with Compute Optimizer Automation.

AutomationEvent

Contains information about an automation event.

AutomationEventFilter

A filter to apply when listing automation events.

AutomationEventStep

Contains information about a step in an automation event.

AutomationEventSummary

A summary of automation events grouped by specified dimensions.

AutomationRule

Represents a complete automation rule configuration including criteria, schedule, and execution settings.

Criteria

A set of conditions that specify which recommended action qualify for implementation. When a rule is active and a recommended action matches these criteria, Compute Optimizer implements the action at the scheduled run time. You can specify up to 20 conditions per filter criteria and 20 values per condition.

DoubleCriteriaCondition

Defines a condition for filtering based on double/floating-point numeric values with comparison operators.

EbsVolume

Represents an Amazon EBS volume with its configuration and snapshot usage information.

EbsVolumeConfiguration

Configuration details for an Amazon EBS volume.

EstimatedMonthlySavings

Contains information about estimated monthly cost savings.

Filter

A filter used to narrow down results based on specific criteria.

IntegerCriteriaCondition

Defines a condition for filtering based on integer values with comparison operators.

OrganizationConfiguration

Configuration settings for organization-wide automation rules.

OrganizationScope

Defines the scope for organization-level rules when previewing matching actions.

PreviewResult

Contains the results of previewing an automation rule against available recommendations.

PreviewResultSummary

Contains a summary of preview results for an automation rule.

RecommendedAction

Contains information about a recommended action that can be applied to optimize an Amazon Web Services resource.

RecommendedActionFilter

A filter used to narrow down recommended action results based on specific criteria.

RecommendedActionSummary

Summary information about recommended actions, grouped by specific criteria with totals and counts.

RecommendedActionTotal

Aggregate totals for a group of recommended actions, including count and estimated monthly savings.

ResourceTagsCriteriaCondition

Criteria condition for filtering resources based on their tags, including comparison operators and values.

RulePreviewTotal

Aggregate totals for automation rule preview results, including count and estimated savings.

Schedule

Configuration for scheduling when automation rules should execute, including timing and execution windows.

StringCriteriaCondition

Criteria condition for filtering based on string values, including comparison operators and target values.

SummaryDimension

A key-value pair used to categorize and group summary data for analysis and reporting.

SummaryTotals

Aggregate totals for automation events, including counts and estimated savings.

Tag

A key-value pair used to categorize and organize Amazon Web Services resources and automation rules.

TimePeriod

Defines a time range with inclusive start time and exclusive end time for filtering and analysis.

Enums§

AutomationEventFilterName
When writing a match expression against AutomationEventFilterName, 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.
AutomationRuleFilterName
When writing a match expression against AutomationRuleFilterName, 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.
EnrollmentStatus
When writing a match expression against EnrollmentStatus, 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.
EventStatus
When writing a match expression against EventStatus, 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.
OrganizationRuleMode
When writing a match expression against OrganizationRuleMode, 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.
RecommendedActionFilterName
When writing a match expression against RecommendedActionFilterName, 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.
RecommendedActionType
When writing a match expression against RecommendedActionType, 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.
ResourceDetails

Detailed configuration information for a specific Amazon Web Services resource, with type-specific details.

ResourceType
When writing a match expression against ResourceType, 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.
RuleApplyOrder
When writing a match expression against RuleApplyOrder, 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.
RuleStatus
When writing a match expression against RuleStatus, 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.
RuleType
When writing a match expression against RuleType, 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.
SavingsEstimationMode
When writing a match expression against SavingsEstimationMode, 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.
StepStatus
When writing a match expression against StepStatus, 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.
StepType
When writing a match expression against StepType, 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.
SummaryDimensionKey
When writing a match expression against SummaryDimensionKey, 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.