interface CfnCoreDefinitionProps
Language | Type name |
---|---|
![]() | Amazon.CDK.AWS.Greengrass.CfnCoreDefinitionProps |
![]() | github.com/aws/aws-cdk-go/awscdk/v2/awsgreengrass#CfnCoreDefinitionProps |
![]() | software.amazon.awscdk.services.greengrass.CfnCoreDefinitionProps |
![]() | aws_cdk.aws_greengrass.CfnCoreDefinitionProps |
![]() | aws-cdk-lib » aws_greengrass » CfnCoreDefinitionProps |
Properties for defining a CfnCoreDefinition
.
Example
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import { aws_greengrass as greengrass } from 'aws-cdk-lib';
declare const tags: any;
const cfnCoreDefinitionProps: greengrass.CfnCoreDefinitionProps = {
name: 'name',
// the properties below are optional
initialVersion: {
cores: [{
certificateArn: 'certificateArn',
id: 'id',
thingArn: 'thingArn',
// the properties below are optional
syncShadow: false,
}],
},
tags: tags,
};
Properties
Name | Type | Description |
---|---|---|
name | string | The name of the core definition. |
initial | IResolvable | Core | The core definition version to include when the core definition is created. |
tags? | any | Application-specific metadata to attach to the core definition. |
name
Type:
string
The name of the core definition.
initialVersion?
Type:
IResolvable
|
Core
(optional)
The core definition version to include when the core definition is created.
Currently, a core definition version can contain only one core
.
To associate a core definition version after the core definition is created, create an
AWS::Greengrass::CoreDefinitionVersion
resource and specify the ID of this core definition.
tags?
Type:
any
(optional)
Application-specific metadata to attach to the core definition.
You can use tags in IAM policies to control access to AWS IoT Greengrass resources. You can also use tags to categorize your resources. For more information, see Tagging Your AWS IoT Greengrass Resources in the Developer Guide .
This Json
property type is processed as a map of key-value pairs. It uses the following format, which is different from most Tags
implementations in AWS CloudFormation templates.
"Tags": { "KeyName0": "value", "KeyName1": "value", "KeyName2": "value"
}