Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

CostEstimationResourceCollectionFilter

import type { CostEstimationResourceCollectionFilter } from "https://aws-api.deno.dev/v0.3/services/devopsguru.ts?docs=full";

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.

interface CostEstimationResourceCollectionFilter {
CloudFormation?: CloudFormationCostEstimationResourceCollectionFilter | null;
Tags?: TagCostEstimationResourceCollectionFilter[] | null;
}

§Properties

§
CloudFormation?: CloudFormationCostEstimationResourceCollectionFilter | null
[src]

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

§
Tags?: TagCostEstimationResourceCollectionFilter[] | null
[src]

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.

! IMPORTANT: ! 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.