| Copyright | (c) 2013-2023 Brendan Hay |
|---|---|
| License | Mozilla Public License, v. 2.0. |
| Maintainer | Brendan Hay |
| Stability | auto-generated |
| Portability | non-portable (GHC extensions) |
| Safe Haskell | Safe-Inferred |
| Language | Haskell2010 |
Amazonka.CostExplorer.Types.Expression
Description
Synopsis
- data Expression = Expression' {}
- newExpression :: Expression
- expression_and :: Lens' Expression (Maybe [Expression])
- expression_costCategories :: Lens' Expression (Maybe CostCategoryValues)
- expression_dimensions :: Lens' Expression (Maybe DimensionValues)
- expression_not :: Lens' Expression (Maybe Expression)
- expression_or :: Lens' Expression (Maybe [Expression])
- expression_tags :: Lens' Expression (Maybe TagValues)
Documentation
data Expression Source #
Use Expression to filter in various Cost Explorer APIs.
Not all Expression types are supported in each API. Refer to the
documentation for each specific API to see what is supported.
There are two patterns:
Simple dimension values.
There are three types of simple dimension values:
CostCategories,Tags, andDimensions.- Specify the
CostCategoriesfield to define a filter that acts on Cost Categories. - Specify the
Tagsfield to define a filter that acts on Cost Allocation Tags. - Specify the
Dimensionsfield to define a filter that acts on the DimensionValues .
- Specify the
For each filter type, you can set the dimension name and values for the filters that you plan to use.
- For example, you can filter for
REGION==us-east-1 OR REGION==us-west-1. ForGetRightsizingRecommendation, the Region is a full name (for example,REGION==US East (N. Virginia). - The corresponding
Expressionfor this example is as follows:{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1", “us-west-1” ] } } - As shown in the previous example, lists of dimension values
are combined with
ORwhen applying the filter.
- For example, you can filter for
You can also set different match options to further control how the filter behaves. Not all APIs support match options. Refer to the documentation for each specific API to see what is supported.
- For example, you can filter for linked account names that start with “a”.
- The corresponding
Expressionfor this example is as follows:{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }
Compound
Expressiontypes with logical operations.- You can use multiple
Expressiontypes and the logical operatorsAND/OR/NOTto create a list of one or moreExpressionobjects. By doing this, you can filter by more advanced options. - For example, you can filter by
((REGION == us-east-1 OR REGION == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE != DataTransfer). - The corresponding
Expressionfor this example is as follows:{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName", "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key": "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] }
Because each
Expressioncan have only one operator, the service returns an error if more than one is specified. The following example shows anExpressionobject that creates an error:{ "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [ "DataTransfer" ] } }The following is an example of the corresponding error message:
"Expression has more than one roots. Only one root operator is allowed for each expression: And, Or, Not, Dimensions, Tags, CostCategories"- You can use multiple
For the GetRightsizingRecommendation action, a combination of OR and
NOT isn't supported. OR isn't supported between different dimensions,
or dimensions and tags. NOT operators aren't supported. Dimensions are
also limited to LINKED_ACCOUNT, REGION, or RIGHTSIZING_TYPE.
For the GetReservationPurchaseRecommendation action, only NOT is
supported. AND and OR aren't supported. Dimensions are limited to
LINKED_ACCOUNT.
See: newExpression smart constructor.
Constructors
| Expression' | |
Fields
| |
Instances
newExpression :: Expression Source #
Create a value of Expression with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.
The following record fields are available, with the corresponding lenses provided for backwards compatibility:
$sel:and:Expression', expression_and - Return results that match both Dimension objects.
$sel:costCategories:Expression', expression_costCategories - The filter that's based on CostCategory values.
$sel:dimensions:Expression', expression_dimensions - The specific Dimension to use for Expression.
$sel:not:Expression', expression_not - Return results that don't match a Dimension object.
$sel:or:Expression', expression_or - Return results that match either Dimension object.
$sel:tags:Expression', expression_tags - The specific Tag to use for Expression.
expression_and :: Lens' Expression (Maybe [Expression]) Source #
Return results that match both Dimension objects.
expression_costCategories :: Lens' Expression (Maybe CostCategoryValues) Source #
The filter that's based on CostCategory values.
expression_dimensions :: Lens' Expression (Maybe DimensionValues) Source #
The specific Dimension to use for Expression.
expression_not :: Lens' Expression (Maybe Expression) Source #
Return results that don't match a Dimension object.
expression_or :: Lens' Expression (Maybe [Expression]) Source #
Return results that match either Dimension object.
expression_tags :: Lens' Expression (Maybe TagValues) Source #
The specific Tag to use for Expression.