@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class ResourceCollectionFilter extends Object implements Serializable, Cloneable, StructuredPojo
Information about a filter used to specify which Amazon Web Services resources are analyzed for anomalous behavior by DevOps Guru.
| Constructor and Description |
|---|
ResourceCollectionFilter() |
| Modifier and Type | Method and Description |
|---|---|
ResourceCollectionFilter |
clone() |
boolean |
equals(Object obj) |
CloudFormationCollectionFilter |
getCloudFormation()
Information about Amazon Web Services CloudFormation stacks.
|
List<TagCollectionFilter> |
getTags()
The Amazon Web Services tags used to filter the resources in the resource collection.
|
int |
hashCode() |
void |
marshall(ProtocolMarshaller protocolMarshaller) |
void |
setCloudFormation(CloudFormationCollectionFilter cloudFormation)
Information about Amazon Web Services CloudFormation stacks.
|
void |
setTags(Collection<TagCollectionFilter> tags)
The Amazon Web Services tags used to filter the resources in the resource collection.
|
String |
toString()
Returns a string representation of this object.
|
ResourceCollectionFilter |
withCloudFormation(CloudFormationCollectionFilter cloudFormation)
Information about Amazon Web Services CloudFormation stacks.
|
ResourceCollectionFilter |
withTags(Collection<TagCollectionFilter> tags)
The Amazon Web Services tags used to filter the resources in the resource collection.
|
ResourceCollectionFilter |
withTags(TagCollectionFilter... tags)
The Amazon Web Services tags used to filter the resources in the resource collection.
|
public void setCloudFormation(CloudFormationCollectionFilter 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.
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.public CloudFormationCollectionFilter getCloudFormation()
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.
public ResourceCollectionFilter withCloudFormation(CloudFormationCollectionFilter 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.
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.public List<TagCollectionFilter> getTags()
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. While keys are case-sensitive, the case of key characters
don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds
and a key named DevOps-Guru-RDS. Possible key/value pairs in your application
might be Devops-Guru-production-application/RDS or
Devops-Guru-production-application/containers.
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. While
keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For
example, DevOps Guru works with a key named devops-guru-rds and a key named
DevOps-Guru-RDS. Possible key/value pairs in your application might be
Devops-Guru-production-application/RDS or
Devops-Guru-production-application/containers.
public void setTags(Collection<TagCollectionFilter> 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. While keys are case-sensitive, the case of key characters
don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds
and a key named DevOps-Guru-RDS. Possible key/value pairs in your application
might be Devops-Guru-production-application/RDS or
Devops-Guru-production-application/containers.
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. While
keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For
example, DevOps Guru works with a key named devops-guru-rds and a key named
DevOps-Guru-RDS. Possible key/value pairs in your application might be
Devops-Guru-production-application/RDS or
Devops-Guru-production-application/containers.
public ResourceCollectionFilter withTags(TagCollectionFilter... 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. While keys are case-sensitive, the case of key characters
don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds
and a key named DevOps-Guru-RDS. Possible key/value pairs in your application
might be Devops-Guru-production-application/RDS or
Devops-Guru-production-application/containers.
NOTE: This method appends the values to the existing list (if any). Use
setTags(java.util.Collection) or withTags(java.util.Collection) if you want to override the
existing values.
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. While
keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For
example, DevOps Guru works with a key named devops-guru-rds and a key named
DevOps-Guru-RDS. Possible key/value pairs in your application might be
Devops-Guru-production-application/RDS or
Devops-Guru-production-application/containers.
public ResourceCollectionFilter withTags(Collection<TagCollectionFilter> 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. While keys are case-sensitive, the case of key characters
don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds
and a key named DevOps-Guru-RDS. Possible key/value pairs in your application
might be Devops-Guru-production-application/RDS or
Devops-Guru-production-application/containers.
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. While
keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For
example, DevOps Guru works with a key named devops-guru-rds and a key named
DevOps-Guru-RDS. Possible key/value pairs in your application might be
Devops-Guru-production-application/RDS or
Devops-Guru-production-application/containers.
public String toString()
toString in class ObjectObject.toString()public ResourceCollectionFilter clone()
public void marshall(ProtocolMarshaller protocolMarshaller)
marshall in interface StructuredPojoCopyright © 2022. All rights reserved.