We recommend new projects start with resources from the AWS provider.
aws-native.devopsguru.ResourceCollection
Explore with Pulumi AI
We recommend new projects start with resources from the AWS provider.
This resource schema represents the ResourceCollection resource in the Amazon DevOps Guru.
Example Usage
Example
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using AwsNative = Pulumi.AwsNative;
return await Deployment.RunAsync(() =>
{
var myResourceCollection = new AwsNative.DevOpsGuru.ResourceCollection("myResourceCollection", new()
{
ResourceCollectionFilter = new AwsNative.DevOpsGuru.Inputs.ResourceCollectionFilterArgs
{
CloudFormation = new AwsNative.DevOpsGuru.Inputs.ResourceCollectionCloudFormationCollectionFilterArgs
{
StackNames = new[]
{
"StackA",
"StackB",
},
},
},
});
});
package main
import (
"github.com/pulumi/pulumi-aws-native/sdk/go/aws/devopsguru"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := devopsguru.NewResourceCollection(ctx, "myResourceCollection", &devopsguru.ResourceCollectionArgs{
ResourceCollectionFilter: &devopsguru.ResourceCollectionFilterArgs{
CloudFormation: &devopsguru.ResourceCollectionCloudFormationCollectionFilterArgs{
StackNames: pulumi.StringArray{
pulumi.String("StackA"),
pulumi.String("StackB"),
},
},
},
})
if err != nil {
return err
}
return nil
})
}
Coming soon!
import pulumi
import pulumi_aws_native as aws_native
my_resource_collection = aws_native.devopsguru.ResourceCollection("myResourceCollection", resource_collection_filter={
"cloud_formation": {
"stack_names": [
"StackA",
"StackB",
],
},
})
import * as pulumi from "@pulumi/pulumi";
import * as aws_native from "@pulumi/aws-native";
const myResourceCollection = new aws_native.devopsguru.ResourceCollection("myResourceCollection", {resourceCollectionFilter: {
cloudFormation: {
stackNames: [
"StackA",
"StackB",
],
},
}});
Coming soon!
Example
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using AwsNative = Pulumi.AwsNative;
return await Deployment.RunAsync(() =>
{
var myResourceCollection = new AwsNative.DevOpsGuru.ResourceCollection("myResourceCollection", new()
{
ResourceCollectionFilter = new AwsNative.DevOpsGuru.Inputs.ResourceCollectionFilterArgs
{
CloudFormation = new AwsNative.DevOpsGuru.Inputs.ResourceCollectionCloudFormationCollectionFilterArgs
{
StackNames = new[]
{
"StackA",
"StackB",
},
},
},
});
});
package main
import (
"github.com/pulumi/pulumi-aws-native/sdk/go/aws/devopsguru"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := devopsguru.NewResourceCollection(ctx, "myResourceCollection", &devopsguru.ResourceCollectionArgs{
ResourceCollectionFilter: &devopsguru.ResourceCollectionFilterArgs{
CloudFormation: &devopsguru.ResourceCollectionCloudFormationCollectionFilterArgs{
StackNames: pulumi.StringArray{
pulumi.String("StackA"),
pulumi.String("StackB"),
},
},
},
})
if err != nil {
return err
}
return nil
})
}
Coming soon!
import pulumi
import pulumi_aws_native as aws_native
my_resource_collection = aws_native.devopsguru.ResourceCollection("myResourceCollection", resource_collection_filter={
"cloud_formation": {
"stack_names": [
"StackA",
"StackB",
],
},
})
import * as pulumi from "@pulumi/pulumi";
import * as aws_native from "@pulumi/aws-native";
const myResourceCollection = new aws_native.devopsguru.ResourceCollection("myResourceCollection", {resourceCollectionFilter: {
cloudFormation: {
stackNames: [
"StackA",
"StackB",
],
},
}});
Coming soon!
Example
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using AwsNative = Pulumi.AwsNative;
return await Deployment.RunAsync(() =>
{
var myResourceCollection = new AwsNative.DevOpsGuru.ResourceCollection("myResourceCollection", new()
{
ResourceCollectionFilter = new AwsNative.DevOpsGuru.Inputs.ResourceCollectionFilterArgs
{
CloudFormation = new AwsNative.DevOpsGuru.Inputs.ResourceCollectionCloudFormationCollectionFilterArgs
{
StackNames = new[]
{
"*",
},
},
},
});
});
package main
import (
"github.com/pulumi/pulumi-aws-native/sdk/go/aws/devopsguru"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := devopsguru.NewResourceCollection(ctx, "myResourceCollection", &devopsguru.ResourceCollectionArgs{
ResourceCollectionFilter: &devopsguru.ResourceCollectionFilterArgs{
CloudFormation: &devopsguru.ResourceCollectionCloudFormationCollectionFilterArgs{
StackNames: pulumi.StringArray{
pulumi.String("*"),
},
},
},
})
if err != nil {
return err
}
return nil
})
}
Coming soon!
import pulumi
import pulumi_aws_native as aws_native
my_resource_collection = aws_native.devopsguru.ResourceCollection("myResourceCollection", resource_collection_filter={
"cloud_formation": {
"stack_names": ["*"],
},
})
import * as pulumi from "@pulumi/pulumi";
import * as aws_native from "@pulumi/aws-native";
const myResourceCollection = new aws_native.devopsguru.ResourceCollection("myResourceCollection", {resourceCollectionFilter: {
cloudFormation: {
stackNames: ["*"],
},
}});
Coming soon!
Example
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using AwsNative = Pulumi.AwsNative;
return await Deployment.RunAsync(() =>
{
var myResourceCollection = new AwsNative.DevOpsGuru.ResourceCollection("myResourceCollection", new()
{
ResourceCollectionFilter = new AwsNative.DevOpsGuru.Inputs.ResourceCollectionFilterArgs
{
CloudFormation = new AwsNative.DevOpsGuru.Inputs.ResourceCollectionCloudFormationCollectionFilterArgs
{
StackNames = new[]
{
"*",
},
},
},
});
});
package main
import (
"github.com/pulumi/pulumi-aws-native/sdk/go/aws/devopsguru"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := devopsguru.NewResourceCollection(ctx, "myResourceCollection", &devopsguru.ResourceCollectionArgs{
ResourceCollectionFilter: &devopsguru.ResourceCollectionFilterArgs{
CloudFormation: &devopsguru.ResourceCollectionCloudFormationCollectionFilterArgs{
StackNames: pulumi.StringArray{
pulumi.String("*"),
},
},
},
})
if err != nil {
return err
}
return nil
})
}
Coming soon!
import pulumi
import pulumi_aws_native as aws_native
my_resource_collection = aws_native.devopsguru.ResourceCollection("myResourceCollection", resource_collection_filter={
"cloud_formation": {
"stack_names": ["*"],
},
})
import * as pulumi from "@pulumi/pulumi";
import * as aws_native from "@pulumi/aws-native";
const myResourceCollection = new aws_native.devopsguru.ResourceCollection("myResourceCollection", {resourceCollectionFilter: {
cloudFormation: {
stackNames: ["*"],
},
}});
Coming soon!
Create ResourceCollection Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new ResourceCollection(name: string, args: ResourceCollectionArgs, opts?: CustomResourceOptions);
@overload
def ResourceCollection(resource_name: str,
args: ResourceCollectionArgs,
opts: Optional[ResourceOptions] = None)
@overload
def ResourceCollection(resource_name: str,
opts: Optional[ResourceOptions] = None,
resource_collection_filter: Optional[ResourceCollectionFilterArgs] = None)
func NewResourceCollection(ctx *Context, name string, args ResourceCollectionArgs, opts ...ResourceOption) (*ResourceCollection, error)
public ResourceCollection(string name, ResourceCollectionArgs args, CustomResourceOptions? opts = null)
public ResourceCollection(String name, ResourceCollectionArgs args)
public ResourceCollection(String name, ResourceCollectionArgs args, CustomResourceOptions options)
type: aws-native:devopsguru:ResourceCollection
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args ResourceCollectionArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args ResourceCollectionArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args ResourceCollectionArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args ResourceCollectionArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args ResourceCollectionArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
ResourceCollection Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The ResourceCollection resource accepts the following input properties:
- Resource
Collection Pulumi.Filter Aws Native. Dev Ops Guru. Inputs. Resource Collection Filter - Information about a filter used to specify which AWS resources are analyzed for anomalous behavior by DevOps Guru.
- Resource
Collection ResourceFilter Collection Filter Args - Information about a filter used to specify which AWS resources are analyzed for anomalous behavior by DevOps Guru.
- resource
Collection ResourceFilter Collection Filter - Information about a filter used to specify which AWS resources are analyzed for anomalous behavior by DevOps Guru.
- resource
Collection ResourceFilter Collection Filter - Information about a filter used to specify which AWS resources are analyzed for anomalous behavior by DevOps Guru.
- resource_
collection_ Resourcefilter Collection Filter Args - Information about a filter used to specify which AWS resources are analyzed for anomalous behavior by DevOps Guru.
- resource
Collection Property MapFilter - Information about a filter used to specify which AWS resources are analyzed for anomalous behavior by DevOps Guru.
Outputs
All input properties are implicitly available as output properties. Additionally, the ResourceCollection resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Resource
Collection Pulumi.Type Aws Native. Dev Ops Guru. Resource Collection Type - The type of ResourceCollection
- Id string
- The provider-assigned unique ID for this managed resource.
- Resource
Collection ResourceType Collection Type - The type of ResourceCollection
- id String
- The provider-assigned unique ID for this managed resource.
- resource
Collection ResourceType Collection Type - The type of ResourceCollection
- id string
- The provider-assigned unique ID for this managed resource.
- resource
Collection ResourceType Collection Type - The type of ResourceCollection
- id str
- The provider-assigned unique ID for this managed resource.
- resource_
collection_ Resourcetype Collection Type - The type of ResourceCollection
- id String
- The provider-assigned unique ID for this managed resource.
- resource
Collection "AWS_CLOUD_FORMATION" | "AWS_TAGS"Type - The type of ResourceCollection
Supporting Types
ResourceCollectionCloudFormationCollectionFilter, ResourceCollectionCloudFormationCollectionFilterArgs
- Stack
Names List<string> - An array of CloudFormation stack names.
- Stack
Names []string - An array of CloudFormation stack names.
- stack
Names List<String> - An array of CloudFormation stack names.
- stack
Names string[] - An array of CloudFormation stack names.
- stack_
names Sequence[str] - An array of CloudFormation stack names.
- stack
Names List<String> - An array of CloudFormation stack names.
ResourceCollectionFilter, ResourceCollectionFilterArgs
- Cloud
Formation Pulumi.Aws Native. Dev Ops Guru. Inputs. Resource Collection Cloud Formation Collection Filter - Information about AWS CloudFormation stacks. You can use up to 1000 stacks to specify which AWS resources in your account to analyze. For more information, see Stacks in the AWS CloudFormation User Guide .
- List<Pulumi.
Aws Native. Dev Ops Guru. Inputs. Resource Collection Tag Collection> The AWS tags used to filter the resources in the resource collection.
Tags help you identify and organize your AWS resources. Many AWS 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 AWS Lambda function. For more information about using tags, see the Tagging best practices whitepaper.
Each AWS tag has two parts.
- A tag key (for example,
CostCenter
,Environment
,Project
, orSecret
). Tag keys are case-sensitive. - A 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. The tag value is a required property when AppBoundaryKey is specified.
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 beDevOps-Guru-deployment-application
ordevops-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 nameddevops-guru-rds
and a key namedDevOps-Guru-RDS
, and these act as two different keys . Possible key / value pairs in your application might beDevops-Guru-production-application/RDS
orDevops-Guru-production-application/containers
.- A tag key (for example,
- Cloud
Formation ResourceCollection Cloud Formation Collection Filter - Information about AWS CloudFormation stacks. You can use up to 1000 stacks to specify which AWS resources in your account to analyze. For more information, see Stacks in the AWS CloudFormation User Guide .
- []Resource
Collection Tag Collection The AWS tags used to filter the resources in the resource collection.
Tags help you identify and organize your AWS resources. Many AWS 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 AWS Lambda function. For more information about using tags, see the Tagging best practices whitepaper.
Each AWS tag has two parts.
- A tag key (for example,
CostCenter
,Environment
,Project
, orSecret
). Tag keys are case-sensitive. - A 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. The tag value is a required property when AppBoundaryKey is specified.
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 beDevOps-Guru-deployment-application
ordevops-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 nameddevops-guru-rds
and a key namedDevOps-Guru-RDS
, and these act as two different keys . Possible key / value pairs in your application might beDevops-Guru-production-application/RDS
orDevops-Guru-production-application/containers
.- A tag key (for example,
- cloud
Formation ResourceCollection Cloud Formation Collection Filter - Information about AWS CloudFormation stacks. You can use up to 1000 stacks to specify which AWS resources in your account to analyze. For more information, see Stacks in the AWS CloudFormation User Guide .
- List<Resource
Collection Tag Collection> The AWS tags used to filter the resources in the resource collection.
Tags help you identify and organize your AWS resources. Many AWS 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 AWS Lambda function. For more information about using tags, see the Tagging best practices whitepaper.
Each AWS tag has two parts.
- A tag key (for example,
CostCenter
,Environment
,Project
, orSecret
). Tag keys are case-sensitive. - A 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. The tag value is a required property when AppBoundaryKey is specified.
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 beDevOps-Guru-deployment-application
ordevops-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 nameddevops-guru-rds
and a key namedDevOps-Guru-RDS
, and these act as two different keys . Possible key / value pairs in your application might beDevops-Guru-production-application/RDS
orDevops-Guru-production-application/containers
.- A tag key (for example,
- cloud
Formation ResourceCollection Cloud Formation Collection Filter - Information about AWS CloudFormation stacks. You can use up to 1000 stacks to specify which AWS resources in your account to analyze. For more information, see Stacks in the AWS CloudFormation User Guide .
- Resource
Collection Tag Collection[] The AWS tags used to filter the resources in the resource collection.
Tags help you identify and organize your AWS resources. Many AWS 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 AWS Lambda function. For more information about using tags, see the Tagging best practices whitepaper.
Each AWS tag has two parts.
- A tag key (for example,
CostCenter
,Environment
,Project
, orSecret
). Tag keys are case-sensitive. - A 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. The tag value is a required property when AppBoundaryKey is specified.
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 beDevOps-Guru-deployment-application
ordevops-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 nameddevops-guru-rds
and a key namedDevOps-Guru-RDS
, and these act as two different keys . Possible key / value pairs in your application might beDevops-Guru-production-application/RDS
orDevops-Guru-production-application/containers
.- A tag key (for example,
- cloud_
formation ResourceCollection Cloud Formation Collection Filter - Information about AWS CloudFormation stacks. You can use up to 1000 stacks to specify which AWS resources in your account to analyze. For more information, see Stacks in the AWS CloudFormation User Guide .
- Sequence[Resource
Collection Tag Collection] The AWS tags used to filter the resources in the resource collection.
Tags help you identify and organize your AWS resources. Many AWS 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 AWS Lambda function. For more information about using tags, see the Tagging best practices whitepaper.
Each AWS tag has two parts.
- A tag key (for example,
CostCenter
,Environment
,Project
, orSecret
). Tag keys are case-sensitive. - A 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. The tag value is a required property when AppBoundaryKey is specified.
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 beDevOps-Guru-deployment-application
ordevops-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 nameddevops-guru-rds
and a key namedDevOps-Guru-RDS
, and these act as two different keys . Possible key / value pairs in your application might beDevops-Guru-production-application/RDS
orDevops-Guru-production-application/containers
.- A tag key (for example,
- cloud
Formation Property Map - Information about AWS CloudFormation stacks. You can use up to 1000 stacks to specify which AWS resources in your account to analyze. For more information, see Stacks in the AWS CloudFormation User Guide .
- List<Property Map>
The AWS tags used to filter the resources in the resource collection.
Tags help you identify and organize your AWS resources. Many AWS 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 AWS Lambda function. For more information about using tags, see the Tagging best practices whitepaper.
Each AWS tag has two parts.
- A tag key (for example,
CostCenter
,Environment
,Project
, orSecret
). Tag keys are case-sensitive. - A 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. The tag value is a required property when AppBoundaryKey is specified.
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 beDevOps-Guru-deployment-application
ordevops-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 nameddevops-guru-rds
and a key namedDevOps-Guru-RDS
, and these act as two different keys . Possible key / value pairs in your application might beDevops-Guru-production-application/RDS
orDevops-Guru-production-application/containers
.- A tag key (for example,
ResourceCollectionTagCollection, ResourceCollectionTagCollectionArgs
- App
Boundary stringKey - A Tag key for DevOps Guru app boundary.
- Tag
Values List<string> - Tag values of DevOps Guru app boundary.
- App
Boundary stringKey - A Tag key for DevOps Guru app boundary.
- Tag
Values []string - Tag values of DevOps Guru app boundary.
- app
Boundary StringKey - A Tag key for DevOps Guru app boundary.
- tag
Values List<String> - Tag values of DevOps Guru app boundary.
- app
Boundary stringKey - A Tag key for DevOps Guru app boundary.
- tag
Values string[] - Tag values of DevOps Guru app boundary.
- app_
boundary_ strkey - A Tag key for DevOps Guru app boundary.
- tag_
values Sequence[str] - Tag values of DevOps Guru app boundary.
- app
Boundary StringKey - A Tag key for DevOps Guru app boundary.
- tag
Values List<String> - Tag values of DevOps Guru app boundary.
ResourceCollectionType, ResourceCollectionTypeArgs
- Aws
Cloud Formation - AWS_CLOUD_FORMATION
- Aws
Tags - AWS_TAGS
- Resource
Collection Type Aws Cloud Formation - AWS_CLOUD_FORMATION
- Resource
Collection Type Aws Tags - AWS_TAGS
- Aws
Cloud Formation - AWS_CLOUD_FORMATION
- Aws
Tags - AWS_TAGS
- Aws
Cloud Formation - AWS_CLOUD_FORMATION
- Aws
Tags - AWS_TAGS
- AWS_CLOUD_FORMATION
- AWS_CLOUD_FORMATION
- AWS_TAGS
- AWS_TAGS
- "AWS_CLOUD_FORMATION"
- AWS_CLOUD_FORMATION
- "AWS_TAGS"
- AWS_TAGS
Package Details
- Repository
- AWS Native pulumi/pulumi-aws-native
- License
- Apache-2.0
We recommend new projects start with resources from the AWS provider.