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.DevOpsGuru.Types.CostEstimationResourceCollectionFilter

Description

Documentation

data CostEstimationResourceCollectionFilter Source #

Information about a filter used to specify which Amazon Web Services resources are analyzed to create a monthly DevOps Guru cost estimate. For more information, see Estimate your Amazon DevOps Guru costs and Amazon DevOps Guru pricing.

See: newCostEstimationResourceCollectionFilter smart constructor.

Constructors

CostEstimationResourceCollectionFilter'

Fields

cloudFormation :: Maybe CloudFormationCostEstimationResourceCollectionFilter
An object that specifies the CloudFormation stack that defines the Amazon Web Services resources used to create a monthly estimate for DevOps Guru.
tags :: Maybe [TagCostEstimationResourceCollectionFilter]
The Amazon Web Services tags used to filter the resource collection that is used for a cost estimate.
Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.
Each Amazon Web Services tag has two parts.
- A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.
- An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.
Together these are known as key-value pairs.
The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers.

Instances

Instances details

FromJSON CostEstimationResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.CostEstimationResourceCollectionFilter Methods parseJSON :: Value -> Parser CostEstimationResourceCollectionFilter # parseJSONList :: Value -> Parser [CostEstimationResourceCollectionFilter] #
ToJSON CostEstimationResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.CostEstimationResourceCollectionFilter Methods toJSON :: CostEstimationResourceCollectionFilter -> Value # toEncoding :: CostEstimationResourceCollectionFilter -> Encoding # toJSONList :: [CostEstimationResourceCollectionFilter] -> Value # toEncodingList :: [CostEstimationResourceCollectionFilter] -> Encoding #
Generic CostEstimationResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.CostEstimationResourceCollectionFilter Associated Types type Rep CostEstimationResourceCollectionFilter :: Type -> Type # Methods from :: CostEstimationResourceCollectionFilter -> Rep CostEstimationResourceCollectionFilter x # to :: Rep CostEstimationResourceCollectionFilter x -> CostEstimationResourceCollectionFilter #
Read CostEstimationResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.CostEstimationResourceCollectionFilter Methods readsPrec :: Int -> ReadS CostEstimationResourceCollectionFilter # readList :: ReadS [CostEstimationResourceCollectionFilter] # readPrec :: ReadPrec CostEstimationResourceCollectionFilter # readListPrec :: ReadPrec [CostEstimationResourceCollectionFilter] #
Show CostEstimationResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.CostEstimationResourceCollectionFilter Methods showsPrec :: Int -> CostEstimationResourceCollectionFilter -> ShowS # show :: CostEstimationResourceCollectionFilter -> String # showList :: [CostEstimationResourceCollectionFilter] -> ShowS #
NFData CostEstimationResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.CostEstimationResourceCollectionFilter Methods rnf :: CostEstimationResourceCollectionFilter -> () #
Eq CostEstimationResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.CostEstimationResourceCollectionFilter Methods (==) :: CostEstimationResourceCollectionFilter -> CostEstimationResourceCollectionFilter -> Bool # (/=) :: CostEstimationResourceCollectionFilter -> CostEstimationResourceCollectionFilter -> Bool #
Hashable CostEstimationResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.CostEstimationResourceCollectionFilter Methods hashWithSalt :: Int -> CostEstimationResourceCollectionFilter -> Int # hash :: CostEstimationResourceCollectionFilter -> Int #
type Rep CostEstimationResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.CostEstimationResourceCollectionFilter type Rep CostEstimationResourceCollectionFilter = D1 ('MetaData "CostEstimationResourceCollectionFilter" "Amazonka.DevOpsGuru.Types.CostEstimationResourceCollectionFilter" "amazonka-devops-guru-2.0-C03FLSgo73f1Pu5ftIREHS" 'False) (C1 ('MetaCons "CostEstimationResourceCollectionFilter'" 'PrefixI 'True) (S1 ('MetaSel ('Just "cloudFormation") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe CloudFormationCostEstimationResourceCollectionFilter)) :*: S1 ('MetaSel ('Just "tags") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe [TagCostEstimationResourceCollectionFilter]))))

newCostEstimationResourceCollectionFilter :: CostEstimationResourceCollectionFilter Source #

Create a value of CostEstimationResourceCollectionFilter 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:cloudFormation:CostEstimationResourceCollectionFilter', costEstimationResourceCollectionFilter_cloudFormation - An object that specifies the CloudFormation stack that defines the Amazon Web Services resources used to create a monthly estimate for DevOps Guru.

$sel:tags:CostEstimationResourceCollectionFilter', costEstimationResourceCollectionFilter_tags - The Amazon Web Services tags used to filter the resource collection that is used for a cost estimate.

Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.

Each Amazon Web Services tag has two parts.

A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.
An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.

Together these are known as key-value pairs.

The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers.

costEstimationResourceCollectionFilter_cloudFormation :: Lens' CostEstimationResourceCollectionFilter (Maybe CloudFormationCostEstimationResourceCollectionFilter) Source #

An object that specifies the CloudFormation stack that defines the Amazon Web Services resources used to create a monthly estimate for DevOps Guru.

costEstimationResourceCollectionFilter_tags :: Lens' CostEstimationResourceCollectionFilter (Maybe [TagCostEstimationResourceCollectionFilter]) Source #

The Amazon Web Services tags used to filter the resource collection that is used for a cost estimate.

Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.

Each Amazon Web Services tag has two parts.

A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.
An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.

Together these are known as key-value pairs.

The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers.