Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface DescribeOrganizationResourceCollectionHealthResponse

Hierarchy

Index

Properties

Optional Account

Account: AccountHealth[]

The name of the organization's account.

Optional CloudFormation

CloudFormation: CloudFormationHealth[]

The returned CloudFormationHealthOverview object that contains an InsightHealthOverview object with the requested system health information.

Optional NextToken

NextToken: undefined | string

The pagination token to use to retrieve the next page of results for this operation. If there are no more pages, this value is null.

Optional Service

Service: ServiceHealth[]

An array of ServiceHealth objects that describes the health of the Amazon Web Services services associated with the resources in the collection.

Optional Tags

Tags: TagHealth[]

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.