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.ResourceCollectionFilter

Description

Documentation

data ResourceCollectionFilter Source #

Information about a filter used to specify which Amazon Web Services resources are analyzed for anomalous behavior by DevOps Guru.

See: newResourceCollectionFilter smart constructor.

Constructors

ResourceCollectionFilter'

Fields

cloudFormation :: Maybe CloudFormationCollectionFilter
Information about Amazon Web Services CloudFormation stacks. You can use up to 500 stacks to specify which Amazon Web Services resources in your account to analyze. For more information, see Stacks in the Amazon Web Services CloudFormation User Guide.
tags :: Maybe [TagCollectionFilter]
The Amazon Web Services tags used to filter the resources in the resource collection.
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 ResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollectionFilter Methods parseJSON :: Value -> Parser ResourceCollectionFilter # parseJSONList :: Value -> Parser [ResourceCollectionFilter] #
Generic ResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollectionFilter Associated Types type Rep ResourceCollectionFilter :: Type -> Type # Methods from :: ResourceCollectionFilter -> Rep ResourceCollectionFilter x # to :: Rep ResourceCollectionFilter x -> ResourceCollectionFilter #
Read ResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollectionFilter Methods readsPrec :: Int -> ReadS ResourceCollectionFilter # readList :: ReadS [ResourceCollectionFilter] # readPrec :: ReadPrec ResourceCollectionFilter # readListPrec :: ReadPrec [ResourceCollectionFilter] #
Show ResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollectionFilter Methods showsPrec :: Int -> ResourceCollectionFilter -> ShowS # show :: ResourceCollectionFilter -> String # showList :: [ResourceCollectionFilter] -> ShowS #
NFData ResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollectionFilter Methods rnf :: ResourceCollectionFilter -> () #
Eq ResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollectionFilter Methods (==) :: ResourceCollectionFilter -> ResourceCollectionFilter -> Bool # (/=) :: ResourceCollectionFilter -> ResourceCollectionFilter -> Bool #
Hashable ResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollectionFilter Methods hashWithSalt :: Int -> ResourceCollectionFilter -> Int # hash :: ResourceCollectionFilter -> Int #
type Rep ResourceCollectionFilter Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollectionFilter type Rep ResourceCollectionFilter = D1 ('MetaData "ResourceCollectionFilter" "Amazonka.DevOpsGuru.Types.ResourceCollectionFilter" "amazonka-devops-guru-2.0-C03FLSgo73f1Pu5ftIREHS" 'False) (C1 ('MetaCons "ResourceCollectionFilter'" 'PrefixI 'True) (S1 ('MetaSel ('Just "cloudFormation") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe CloudFormationCollectionFilter)) :*: S1 ('MetaSel ('Just "tags") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe [TagCollectionFilter]))))

newResourceCollectionFilter :: ResourceCollectionFilter Source #

Create a value of ResourceCollectionFilter 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:ResourceCollectionFilter', resourceCollectionFilter_cloudFormation - Information about Amazon Web Services CloudFormation stacks. You can use up to 500 stacks to specify which Amazon Web Services resources in your account to analyze. For more information, see Stacks in the Amazon Web Services CloudFormation User Guide.

$sel:tags:ResourceCollectionFilter', resourceCollectionFilter_tags - The Amazon Web Services tags used to filter the resources in the resource collection.

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.

resourceCollectionFilter_cloudFormation :: Lens' ResourceCollectionFilter (Maybe CloudFormationCollectionFilter) Source #

Information about Amazon Web Services CloudFormation stacks. You can use up to 500 stacks to specify which Amazon Web Services resources in your account to analyze. For more information, see Stacks in the Amazon Web Services CloudFormation User Guide.

resourceCollectionFilter_tags :: Lens' ResourceCollectionFilter (Maybe [TagCollectionFilter]) Source #

The Amazon Web Services tags used to filter the resources in the resource collection.

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.