Module types 

Data structures used by operation inputs/outputs.

Modules

builders

Builders

error

Error types that AWS Free Tier can respond with.

Structs

ActivitySummary

The summary of activities.

DimensionValues

Contains the specifications for the filters to use for your request.

Expression

Use Expression to filter in the GetFreeTierUsage API operation.

You can use the following patterns:

• Simple dimension values (Dimensions root operator)

• Complex expressions with logical operators (AND, NOT, and OR root operators).

For simple dimension values, you can set the dimension name, values, and match type for the filters that you plan to use.

Example for simple dimension values

You can filter to match exactly for REGION==us-east-1 OR REGION==us-west-1.

The corresponding Expression appears like the following: { "Dimensions": { "Key": "REGION", "Values": \[ "us-east-1", "us-west-1" \], "MatchOptions": \["EQUALS"\] } }

As shown in the previous example, lists of dimension values are combined with OR when you apply the filter.

For complex expressions with logical operators, you can have nested expressions to use the logical operators and specify advanced filtering.

Example for complex expressions with logical operators

You can filter by ((REGION == us-east-1 OR REGION == us-west-1) OR (SERVICE CONTAINS AWSLambda)) AND (USAGE_TYPE !CONTAINS DataTransfer).

The corresponding Expression appears like the following: { "And": \[ {"Or": \[ {"Dimensions": { "Key": "REGION", "Values": \[ "us-east-1", "us-west-1" \], "MatchOptions": \["EQUALS"\] }}, {"Dimensions": { "Key": "SERVICE", "Values": \["AWSLambda"\], "MatchOptions": \["CONTAINS"\] } } \]}, {"Not": {"Dimensions": { "Key": "USAGE_TYPE", "Values": \["DataTransfer"\], "MatchOptions": \["CONTAINS"\] }}} \] }

In the following Contents, you must specify exactly one of the following root operators.

FreeTierUsage

Consists of a Amazon Web Services Free Tier offer’s metadata and your data usage for the offer.

MonetaryAmount

The monetary amount of the credit.

Enums

AccountPlanStatus

When writing a match expression against AccountPlanStatus, 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.

AccountPlanType

When writing a match expression against AccountPlanType, 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.

ActivityReward

The summary of the rewards granted as a result of activities completed.

ActivityStatus

When writing a match expression against ActivityStatus, 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.

CurrencyCode

When writing a match expression against CurrencyCode, 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.

Dimension

When writing a match expression against Dimension, 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.

LanguageCode

When writing a match expression against LanguageCode, 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.

MatchOption

When writing a match expression against MatchOption, 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.