ReadonlytagsTags to be applied to the stack.
+ReadonlytemplateOptions for CloudFormation template (like version, transform, description).
+ReadonlyregionThe AWS region into which this stack will be deployed (e.g. us-west-2).
This value is resolved according to the following rules:
+env.region when the stack is defined. This can
+either be a concrete region (e.g. us-west-2) or the Aws.REGION
+token.Aws.REGION, which is represents the CloudFormation intrinsic reference
+{ "Ref": "AWS::Region" } encoded as a string token.Preferably, you should use the return value as an opaque string and not
+attempt to parse it to implement your logic. If you do, you must first
+check that it is a concrete value an not an unresolved token. If this
+value is an unresolved token (Token.isUnresolved(stack.region) returns
+true), this implies that the user wishes that this stack will synthesize
+into a region-agnostic template. In this case, your code should either
+fail (throw an error, emit a synth error using Annotations.of(construct).addError()) or
+implement some other region-agnostic behavior.
ReadonlyaccountThe AWS account into which this stack will be deployed.
+This value is resolved according to the following rules:
+env.account when the stack is defined. This can
+either be a concrete account (e.g. 585695031111) or the
+Aws.ACCOUNT_ID token.Aws.ACCOUNT_ID, which represents the CloudFormation intrinsic reference
+{ "Ref": "AWS::AccountId" } encoded as a string token.Preferably, you should use the return value as an opaque string and not
+attempt to parse it to implement your logic. If you do, you must first
+check that it is a concrete value an not an unresolved token. If this
+value is an unresolved token (Token.isUnresolved(stack.account) returns
+true), this implies that the user wishes that this stack will synthesize
+into an account-agnostic template. In this case, your code should either
+fail (throw an error, emit a synth error using Annotations.of(construct).addError()) or
+implement some other account-agnostic behavior.
ReadonlyenvironmentThe environment coordinates in which this stack is deployed. In the form
+aws://account/region. Use stack.account and stack.region to obtain
+the specific values, no need to parse.
You can use this value to determine if two stacks are targeting the same +environment.
+If either stack.account or stack.region are not concrete values (e.g.
+Aws.ACCOUNT_ID or Aws.REGION) the special strings unknown-account and/or
+unknown-region will be used respectively to indicate this stack is
+region/account-agnostic.
Optional ReadonlynestedIf this is a nested stack, this represents its AWS::CloudFormation::Stack
+resource. undefined for top-level (non-nested) stacks.
ReadonlytemplateThe name of the CloudFormation template file emitted to the output +directory during synthesis.
+Example value: MyStack.template.json
ReadonlyartifactThe ID of the cloud assembly artifact for this stack.
+ReadonlysynthesizerSynthesis method for this stack
+Readonly Internal_Whether version reporting is enabled for this stack
+Controls whether the CDK Metadata resource is injected
+Readonly Internal_Whether cross region references are enabled for this stack
+Optional Readonly Internal_SNS Notification ARNs to receive stack events.
+ReadonlynodeThe tree node.
+Whether termination protection is enabled for this stack.
+Return the stacks this stack depends on
+The concrete CloudFormation physical stack name.
+This is either the name defined explicitly in the stackName prop or
+allocated based on the stack's location in the construct tree. Stacks that
+are directly defined under the app use their construct id as their stack
+name. Stacks that are defined deeper within the tree will use a hashed naming
+scheme based on the construct path to ensure uniqueness.
If you wish to obtain the deploy-time AWS::StackName intrinsic,
+you can use Aws.STACK_NAME directly.
The partition in which this stack is defined
+The Amazon domain suffix for the region in which this stack is defined
+Returns the list of notification Amazon Resource Names (ARNs) for the current stack.
+Indicates if this is a nested stack, in which case parentStack will include a reference to it's parent.
Returns the list of AZs that are available in the AWS environment +(account/region) associated with this stack.
+If the stack is environment-agnostic (either account and/or region are
+tokens), this property will return an array with 2 tokens that will resolve
+at deploy-time to the first two availability zones returned from CloudFormation's
+Fn::GetAZs intrinsic function.
If they are not available in the context, returns a set of dummy values and
+reports them as missing, and let the CLI resolve them by calling EC2
+DescribeAvailabilityZones on the target environment.
To specify a different strategy for selecting availability zones override this method.
+If this is a nested stack, returns it's parent stack.
+Indicates whether the stack requires bundling or not
+StaticisReturn whether the given object is a Stack.
+We do attribute detection since we can't reliably use 'instanceof'.
+StaticofLooks up the first stack scope in which construct is defined. Fails if there is no stack up the tree.
The construct to start the search from.
+Resolve a tokenized value in the context of the current stack.
+Convert an object, potentially containing tokens, to a JSON string
+Optionalspace: numberConvert an object, potentially containing tokens, to a YAML string
+Indicate that a context key was expected
+Contains instructions which will be emitted into the cloud assembly on how +the key should be supplied.
+The set of parameters needed to obtain the context
+Rename a generated logical identities
+To modify the naming scheme strategy, extend the Stack class and
+override the allocateLogicalId method.
Allocates a stack-unique CloudFormation-compatible logical identity for a +specific resource.
+This method is called when a CfnElement is created and used to render the
+initial logical identity of resources. Logical ID renames are applied at
+this stage.
This method uses the protected method allocateLogicalId to render the
+logical ID for an element. To modify the naming scheme, extend the Stack
+class and override this method.
The CloudFormation element for which a logical identity is +needed.
+Add a dependency between this stack and another stack.
+This can be used to define dependencies between any two stacks within an +app, and also supports nested stacks.
+Optionalreason: stringCreates an ARN from components.
+If partition, region or account are not specified, the stack's
+partition, region and account will be used.
If any component is the empty string, an empty string will be inserted +into the generated ARN at the location that component corresponds to.
+The ARN will be formatted as follows:
+arn:{partition}:{service}:{region}:{account}:{resource}{sep}{resource-name}
+The required ARN pieces that are omitted will be taken from the stack that +the 'scope' is attached to. If all ARN pieces are supplied, the supplied scope +can be 'undefined'.
+Splits the provided ARN into its components. +Works both if 'arn' is a string like 'arn:aws:s3:::bucket', +and a Token representing a dynamic CloudFormation expression +(in which case the returned components will also be dynamic CloudFormation expressions, +encoded as Tokens).
+the ARN to split into its components
+the expected format of 'arn' - depends on what format the service 'arn' represents uses
+Add a Transform to this stack. A Transform is a macro that AWS +CloudFormation uses to process your template.
+Duplicate values are removed when stack is synthesized.
+The transform to add
+Adds an arbitrary key-value pair, with information you want to record about the stack. +These get translated to the Metadata section of the generated template.
+InternalCalled implicitly by the addDependency helper function in order to
+realize a dependency between two top-level stacks at the assembly level.
Use stack.addDependency to define the dependency between any two stacks,
+and take into account nested stack relationships.
Optionalreason: StackDependencyReasonInternalCalled implicitly by the obtainDependencies helper function in order to
+collect resource dependencies across two top-level stacks at the assembly level.
Use stack.obtainDependencies to see the dependencies between any two stacks.
InternalCalled implicitly by the removeDependency helper function in order to
+remove a dependency between two top-level stacks at the assembly level.
Use stack.addDependency to define the dependency between any two stacks,
+and take into account nested stack relationships.
OptionalreasonFilter: StackDependencyReasonInternalSynthesizes the cloudformation template into a cloud assembly.
+OptionallookupRoleArn: stringOptionallookupRoleExternalId: stringOptionallookupRoleAdditionalOptions: { [key: string]: any }Look up a fact value for the given fact for the region of this stack
+Will return a definite value only if the region of the current stack is resolved. +If not, a lookup map will be added to the stack and the lookup will be done at +CDK deployment time.
+What regions will be included in the lookup map is controlled by the
+@aws-cdk/core:target-partitions context value: it must be set to a list
+of partitions, and only regions from the given partitions will be included.
+If no such context key is set, all regions will be included.
This function is intended to be used by construct library authors. Application +builders can rely on the abstractions offered by construct libraries and do +not have to worry about regional facts.
+If defaultValue is not given, it is an error if the fact is unknown for
+the given region.
OptionaldefaultValue: stringCreate a CloudFormation Export for a string value
+Returns a string representing the corresponding Fn.importValue()
+expression for this Export. You can control the name for the export by
+passing the name option.
If you don't supply a value for name, the value you're exporting must be
+a Resource attribute (for example: bucket.bucketName) and it will be
+given the same name as the automatic cross-stack reference that would be created
+if you used the attribute in another Stack.
One of the uses for this method is to remove the relationship between +two Stacks established by automatic cross-stack references. It will +temporarily ensure that the CloudFormation Export still exists while you +remove the reference from the consuming stack. After that, you can remove +the resource and the manual export.
+Here is how the process works. Let's say there are two stacks,
+producerStack and consumerStack, and producerStack has a bucket
+called bucket, which is referenced by consumerStack (perhaps because
+an AWS Lambda Function writes into it, or something like that).
It is not safe to remove producerStack.bucket because as the bucket is being
+deleted, consumerStack might still be using it.
Instead, the process takes two deployments:
+Deployment 1: break the relationship:
+consumerStack no longer references bucket.bucketName (maybe the consumer
+stack now uses its own bucket, or it writes to an AWS DynamoDB table, or maybe you just
+remove the Lambda Function altogether).ProducerStack class, call this.exportValue(this.bucket.bucketName). This
+will make sure the CloudFormation Export continues to exist while the relationship
+between the two stacks is being broken.consumerStack, but it's safe to deploy both).Deployment 2: remove the bucket resource:
+bucket resource from producerStack.exportValue() call as well.producerStack will be changed -- the bucket will be deleted).Optionaloptions: ExportValueOptionsCreate a CloudFormation Export for a string list value
+Returns a string list representing the corresponding Fn.importValue()
+expression for this Export. The export expression is automatically wrapped with an
+Fn::Join and the import value with an Fn::Split, since CloudFormation can only
+export strings. You can control the name for the export by passing the name option.
If you don't supply a value for name, the value you're exporting must be
+a Resource attribute (for example: bucket.bucketName) and it will be
+given the same name as the automatic cross-stack reference that would be created
+if you used the attribute in another Stack.
One of the uses for this method is to remove the relationship between +two Stacks established by automatic cross-stack references. It will +temporarily ensure that the CloudFormation Export still exists while you +remove the reference from the consuming stack. After that, you can remove +the resource and the manual export.
+See exportValue for an example of this process.
Optionaloptions: ExportValueOptionsProtectedallocateReturns the naming scheme used to allocate logical IDs. By default, uses
+the HashedAddressingScheme but this method can be overridden to customize
+this behavior.
In order to make sure logical IDs are unique and stable, we hash the resource +construct tree path (i.e. toplevel/secondlevel/.../myresource) and add it as +a suffix to the path components joined without a separator (CloudFormation +IDs only allow alphanumeric characters).
+The result will be:
+<path.join('')><md5(path.join('/')> +"human" "hash"
+If the "human" part of the ID exceeds 240 characters, we simply trim it so +the total ID doesn't exceed CloudFormation's 255 character limit.
+We only take 8 characters from the md5 hash (0.000005 chance of collision).
+Special cases:
+L1/L2/Pipeline/Pipeline), they will be de-duplicated to make the
+resulting human portion of the ID more pleasing: L1L2Pipeline<HASH>
+instead of L1L2PipelinePipeline<HASH>The element for which the logical ID is allocated.
+Protected_InternalValidate stack name
+CloudFormation stack names can include dashes in addition to the regular identifier +character classes, and we don't allow one of the magic markers.
+Protected_InternalReturns the CloudFormation template for this stack by traversing +the tree and invoking _toCloudFormation() on all Entity objects.
+Configure a stack tag
+At deploy time, CloudFormation will automatically apply all stack tags to all resources in the stack.
+Remove a stack tag
+At deploy time, CloudFormation will automatically apply all stack tags to all resources in the stack.
+StaticisChecks if x is a construct.
Use this method instead of instanceof to properly detect Construct
+instances, even when the construct library is symlinked.
Explanation: in JavaScript, multiple copies of the constructs library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class Construct in each copy of the constructs library
+is seen as a different class, and an instance of one class will not test as
+instanceof the other class. npm install will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the constructs
+library can be accidentally installed, and instanceof will behave
+unpredictably. It is safest to avoid using instanceof, and using
+this type-testing method instead.
Any object
+true if x is an object created from a class which extends Construct.
Returns a string representation of this construct.
+The pipeline for building the CodeBuild Image used in other pipelines. This +will produce an image for an OS based on verified Yocto hosts.
+For configuration options see BuildBaseImageCodePipelineProps.
+ReadonlytagsTags to be applied to the stack.
+ReadonlytemplateOptions for CloudFormation template (like version, transform, description).
+ReadonlyregionThe AWS region into which this stack will be deployed (e.g. us-west-2).
This value is resolved according to the following rules:
+env.region when the stack is defined. This can
+either be a concrete region (e.g. us-west-2) or the Aws.REGION
+token.Aws.REGION, which is represents the CloudFormation intrinsic reference
+{ "Ref": "AWS::Region" } encoded as a string token.Preferably, you should use the return value as an opaque string and not
+attempt to parse it to implement your logic. If you do, you must first
+check that it is a concrete value an not an unresolved token. If this
+value is an unresolved token (Token.isUnresolved(stack.region) returns
+true), this implies that the user wishes that this stack will synthesize
+into a region-agnostic template. In this case, your code should either
+fail (throw an error, emit a synth error using Annotations.of(construct).addError()) or
+implement some other region-agnostic behavior.
ReadonlyaccountThe AWS account into which this stack will be deployed.
+This value is resolved according to the following rules:
+env.account when the stack is defined. This can
+either be a concrete account (e.g. 585695031111) or the
+Aws.ACCOUNT_ID token.Aws.ACCOUNT_ID, which represents the CloudFormation intrinsic reference
+{ "Ref": "AWS::AccountId" } encoded as a string token.Preferably, you should use the return value as an opaque string and not
+attempt to parse it to implement your logic. If you do, you must first
+check that it is a concrete value an not an unresolved token. If this
+value is an unresolved token (Token.isUnresolved(stack.account) returns
+true), this implies that the user wishes that this stack will synthesize
+into an account-agnostic template. In this case, your code should either
+fail (throw an error, emit a synth error using Annotations.of(construct).addError()) or
+implement some other account-agnostic behavior.
ReadonlyenvironmentThe environment coordinates in which this stack is deployed. In the form
+aws://account/region. Use stack.account and stack.region to obtain
+the specific values, no need to parse.
You can use this value to determine if two stacks are targeting the same +environment.
+If either stack.account or stack.region are not concrete values (e.g.
+Aws.ACCOUNT_ID or Aws.REGION) the special strings unknown-account and/or
+unknown-region will be used respectively to indicate this stack is
+region/account-agnostic.
Optional ReadonlynestedIf this is a nested stack, this represents its AWS::CloudFormation::Stack
+resource. undefined for top-level (non-nested) stacks.
ReadonlytemplateThe name of the CloudFormation template file emitted to the output +directory during synthesis.
+Example value: MyStack.template.json
ReadonlyartifactThe ID of the cloud assembly artifact for this stack.
+ReadonlysynthesizerSynthesis method for this stack
+Readonly Internal_Whether version reporting is enabled for this stack
+Controls whether the CDK Metadata resource is injected
+Readonly Internal_Whether cross region references are enabled for this stack
+Optional Readonly Internal_SNS Notification ARNs to receive stack events.
+ReadonlyecrThe ECR Repository where the image is located.
+ReadonlyecrThe ECR Image Tag to find the base imaged.
+ReadonlynodeThe tree node.
+Whether termination protection is enabled for this stack.
+Return the stacks this stack depends on
+The concrete CloudFormation physical stack name.
+This is either the name defined explicitly in the stackName prop or
+allocated based on the stack's location in the construct tree. Stacks that
+are directly defined under the app use their construct id as their stack
+name. Stacks that are defined deeper within the tree will use a hashed naming
+scheme based on the construct path to ensure uniqueness.
If you wish to obtain the deploy-time AWS::StackName intrinsic,
+you can use Aws.STACK_NAME directly.
The partition in which this stack is defined
+The Amazon domain suffix for the region in which this stack is defined
+Returns the list of notification Amazon Resource Names (ARNs) for the current stack.
+Indicates if this is a nested stack, in which case parentStack will include a reference to it's parent.
Returns the list of AZs that are available in the AWS environment +(account/region) associated with this stack.
+If the stack is environment-agnostic (either account and/or region are
+tokens), this property will return an array with 2 tokens that will resolve
+at deploy-time to the first two availability zones returned from CloudFormation's
+Fn::GetAZs intrinsic function.
If they are not available in the context, returns a set of dummy values and
+reports them as missing, and let the CLI resolve them by calling EC2
+DescribeAvailabilityZones on the target environment.
To specify a different strategy for selecting availability zones override this method.
+If this is a nested stack, returns it's parent stack.
+Indicates whether the stack requires bundling or not
+StaticisReturn whether the given object is a Stack.
+We do attribute detection since we can't reliably use 'instanceof'.
+StaticofLooks up the first stack scope in which construct is defined. Fails if there is no stack up the tree.
The construct to start the search from.
+Resolve a tokenized value in the context of the current stack.
+Convert an object, potentially containing tokens, to a JSON string
+Optionalspace: numberConvert an object, potentially containing tokens, to a YAML string
+Indicate that a context key was expected
+Contains instructions which will be emitted into the cloud assembly on how +the key should be supplied.
+The set of parameters needed to obtain the context
+Rename a generated logical identities
+To modify the naming scheme strategy, extend the Stack class and
+override the allocateLogicalId method.
Allocates a stack-unique CloudFormation-compatible logical identity for a +specific resource.
+This method is called when a CfnElement is created and used to render the
+initial logical identity of resources. Logical ID renames are applied at
+this stage.
This method uses the protected method allocateLogicalId to render the
+logical ID for an element. To modify the naming scheme, extend the Stack
+class and override this method.
The CloudFormation element for which a logical identity is +needed.
+Add a dependency between this stack and another stack.
+This can be used to define dependencies between any two stacks within an +app, and also supports nested stacks.
+Optionalreason: stringCreates an ARN from components.
+If partition, region or account are not specified, the stack's
+partition, region and account will be used.
If any component is the empty string, an empty string will be inserted +into the generated ARN at the location that component corresponds to.
+The ARN will be formatted as follows:
+arn:{partition}:{service}:{region}:{account}:{resource}{sep}{resource-name}
+The required ARN pieces that are omitted will be taken from the stack that +the 'scope' is attached to. If all ARN pieces are supplied, the supplied scope +can be 'undefined'.
+Splits the provided ARN into its components. +Works both if 'arn' is a string like 'arn:aws:s3:::bucket', +and a Token representing a dynamic CloudFormation expression +(in which case the returned components will also be dynamic CloudFormation expressions, +encoded as Tokens).
+the ARN to split into its components
+the expected format of 'arn' - depends on what format the service 'arn' represents uses
+Add a Transform to this stack. A Transform is a macro that AWS +CloudFormation uses to process your template.
+Duplicate values are removed when stack is synthesized.
+The transform to add
+Adds an arbitrary key-value pair, with information you want to record about the stack. +These get translated to the Metadata section of the generated template.
+InternalCalled implicitly by the addDependency helper function in order to
+realize a dependency between two top-level stacks at the assembly level.
Use stack.addDependency to define the dependency between any two stacks,
+and take into account nested stack relationships.
Optionalreason: StackDependencyReasonInternalCalled implicitly by the obtainDependencies helper function in order to
+collect resource dependencies across two top-level stacks at the assembly level.
Use stack.obtainDependencies to see the dependencies between any two stacks.
InternalCalled implicitly by the removeDependency helper function in order to
+remove a dependency between two top-level stacks at the assembly level.
Use stack.addDependency to define the dependency between any two stacks,
+and take into account nested stack relationships.
OptionalreasonFilter: StackDependencyReasonInternalSynthesizes the cloudformation template into a cloud assembly.
+OptionallookupRoleArn: stringOptionallookupRoleExternalId: stringOptionallookupRoleAdditionalOptions: { [key: string]: any }Look up a fact value for the given fact for the region of this stack
+Will return a definite value only if the region of the current stack is resolved. +If not, a lookup map will be added to the stack and the lookup will be done at +CDK deployment time.
+What regions will be included in the lookup map is controlled by the
+@aws-cdk/core:target-partitions context value: it must be set to a list
+of partitions, and only regions from the given partitions will be included.
+If no such context key is set, all regions will be included.
This function is intended to be used by construct library authors. Application +builders can rely on the abstractions offered by construct libraries and do +not have to worry about regional facts.
+If defaultValue is not given, it is an error if the fact is unknown for
+the given region.
OptionaldefaultValue: stringCreate a CloudFormation Export for a string value
+Returns a string representing the corresponding Fn.importValue()
+expression for this Export. You can control the name for the export by
+passing the name option.
If you don't supply a value for name, the value you're exporting must be
+a Resource attribute (for example: bucket.bucketName) and it will be
+given the same name as the automatic cross-stack reference that would be created
+if you used the attribute in another Stack.
One of the uses for this method is to remove the relationship between +two Stacks established by automatic cross-stack references. It will +temporarily ensure that the CloudFormation Export still exists while you +remove the reference from the consuming stack. After that, you can remove +the resource and the manual export.
+Here is how the process works. Let's say there are two stacks,
+producerStack and consumerStack, and producerStack has a bucket
+called bucket, which is referenced by consumerStack (perhaps because
+an AWS Lambda Function writes into it, or something like that).
It is not safe to remove producerStack.bucket because as the bucket is being
+deleted, consumerStack might still be using it.
Instead, the process takes two deployments:
+Deployment 1: break the relationship:
+consumerStack no longer references bucket.bucketName (maybe the consumer
+stack now uses its own bucket, or it writes to an AWS DynamoDB table, or maybe you just
+remove the Lambda Function altogether).ProducerStack class, call this.exportValue(this.bucket.bucketName). This
+will make sure the CloudFormation Export continues to exist while the relationship
+between the two stacks is being broken.consumerStack, but it's safe to deploy both).Deployment 2: remove the bucket resource:
+bucket resource from producerStack.exportValue() call as well.producerStack will be changed -- the bucket will be deleted).Optionaloptions: ExportValueOptionsCreate a CloudFormation Export for a string list value
+Returns a string list representing the corresponding Fn.importValue()
+expression for this Export. The export expression is automatically wrapped with an
+Fn::Join and the import value with an Fn::Split, since CloudFormation can only
+export strings. You can control the name for the export by passing the name option.
If you don't supply a value for name, the value you're exporting must be
+a Resource attribute (for example: bucket.bucketName) and it will be
+given the same name as the automatic cross-stack reference that would be created
+if you used the attribute in another Stack.
One of the uses for this method is to remove the relationship between +two Stacks established by automatic cross-stack references. It will +temporarily ensure that the CloudFormation Export still exists while you +remove the reference from the consuming stack. After that, you can remove +the resource and the manual export.
+See exportValue for an example of this process.
Optionaloptions: ExportValueOptionsProtectedallocateReturns the naming scheme used to allocate logical IDs. By default, uses
+the HashedAddressingScheme but this method can be overridden to customize
+this behavior.
In order to make sure logical IDs are unique and stable, we hash the resource +construct tree path (i.e. toplevel/secondlevel/.../myresource) and add it as +a suffix to the path components joined without a separator (CloudFormation +IDs only allow alphanumeric characters).
+The result will be:
+<path.join('')><md5(path.join('/')> +"human" "hash"
+If the "human" part of the ID exceeds 240 characters, we simply trim it so +the total ID doesn't exceed CloudFormation's 255 character limit.
+We only take 8 characters from the md5 hash (0.000005 chance of collision).
+Special cases:
+L1/L2/Pipeline/Pipeline), they will be de-duplicated to make the
+resulting human portion of the ID more pleasing: L1L2Pipeline<HASH>
+instead of L1L2PipelinePipeline<HASH>The element for which the logical ID is allocated.
+Protected_InternalValidate stack name
+CloudFormation stack names can include dashes in addition to the regular identifier +character classes, and we don't allow one of the magic markers.
+Protected_InternalReturns the CloudFormation template for this stack by traversing +the tree and invoking _toCloudFormation() on all Entity objects.
+Configure a stack tag
+At deploy time, CloudFormation will automatically apply all stack tags to all resources in the stack.
+Remove a stack tag
+At deploy time, CloudFormation will automatically apply all stack tags to all resources in the stack.
+StaticisChecks if x is a construct.
Use this method instead of instanceof to properly detect Construct
+instances, even when the construct library is symlinked.
Explanation: in JavaScript, multiple copies of the constructs library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class Construct in each copy of the constructs library
+is seen as a different class, and an instance of one class will not test as
+instanceof the other class. npm install will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the constructs
+library can be accidentally installed, and instanceof will behave
+unpredictably. It is safest to avoid using instanceof, and using
+this type-testing method instead.
Any object
+true if x is an object created from a class which extends Construct.
Returns a string representation of this construct.
+The stack for creating a build pipeline.
+See EmbeddedLinuxCodePipelineProps for configration options.
+ReadonlytagsTags to be applied to the stack.
+ReadonlytemplateOptions for CloudFormation template (like version, transform, description).
+ReadonlyregionThe AWS region into which this stack will be deployed (e.g. us-west-2).
This value is resolved according to the following rules:
+env.region when the stack is defined. This can
+either be a concrete region (e.g. us-west-2) or the Aws.REGION
+token.Aws.REGION, which is represents the CloudFormation intrinsic reference
+{ "Ref": "AWS::Region" } encoded as a string token.Preferably, you should use the return value as an opaque string and not
+attempt to parse it to implement your logic. If you do, you must first
+check that it is a concrete value an not an unresolved token. If this
+value is an unresolved token (Token.isUnresolved(stack.region) returns
+true), this implies that the user wishes that this stack will synthesize
+into a region-agnostic template. In this case, your code should either
+fail (throw an error, emit a synth error using Annotations.of(construct).addError()) or
+implement some other region-agnostic behavior.
ReadonlyaccountThe AWS account into which this stack will be deployed.
+This value is resolved according to the following rules:
+env.account when the stack is defined. This can
+either be a concrete account (e.g. 585695031111) or the
+Aws.ACCOUNT_ID token.Aws.ACCOUNT_ID, which represents the CloudFormation intrinsic reference
+{ "Ref": "AWS::AccountId" } encoded as a string token.Preferably, you should use the return value as an opaque string and not
+attempt to parse it to implement your logic. If you do, you must first
+check that it is a concrete value an not an unresolved token. If this
+value is an unresolved token (Token.isUnresolved(stack.account) returns
+true), this implies that the user wishes that this stack will synthesize
+into an account-agnostic template. In this case, your code should either
+fail (throw an error, emit a synth error using Annotations.of(construct).addError()) or
+implement some other account-agnostic behavior.
ReadonlyenvironmentThe environment coordinates in which this stack is deployed. In the form
+aws://account/region. Use stack.account and stack.region to obtain
+the specific values, no need to parse.
You can use this value to determine if two stacks are targeting the same +environment.
+If either stack.account or stack.region are not concrete values (e.g.
+Aws.ACCOUNT_ID or Aws.REGION) the special strings unknown-account and/or
+unknown-region will be used respectively to indicate this stack is
+region/account-agnostic.
Optional ReadonlynestedIf this is a nested stack, this represents its AWS::CloudFormation::Stack
+resource. undefined for top-level (non-nested) stacks.
ReadonlytemplateThe name of the CloudFormation template file emitted to the output +directory during synthesis.
+Example value: MyStack.template.json
ReadonlyartifactThe ID of the cloud assembly artifact for this stack.
+ReadonlysynthesizerSynthesis method for this stack
+Readonly Internal_Whether version reporting is enabled for this stack
+Controls whether the CDK Metadata resource is injected
+Readonly Internal_Whether cross region references are enabled for this stack
+Optional Readonly Internal_SNS Notification ARNs to receive stack events.
+ReadonlynodeThe tree node.
+Whether termination protection is enabled for this stack.
+Return the stacks this stack depends on
+The concrete CloudFormation physical stack name.
+This is either the name defined explicitly in the stackName prop or
+allocated based on the stack's location in the construct tree. Stacks that
+are directly defined under the app use their construct id as their stack
+name. Stacks that are defined deeper within the tree will use a hashed naming
+scheme based on the construct path to ensure uniqueness.
If you wish to obtain the deploy-time AWS::StackName intrinsic,
+you can use Aws.STACK_NAME directly.
The partition in which this stack is defined
+The Amazon domain suffix for the region in which this stack is defined
+Returns the list of notification Amazon Resource Names (ARNs) for the current stack.
+Indicates if this is a nested stack, in which case parentStack will include a reference to it's parent.
Returns the list of AZs that are available in the AWS environment +(account/region) associated with this stack.
+If the stack is environment-agnostic (either account and/or region are
+tokens), this property will return an array with 2 tokens that will resolve
+at deploy-time to the first two availability zones returned from CloudFormation's
+Fn::GetAZs intrinsic function.
If they are not available in the context, returns a set of dummy values and
+reports them as missing, and let the CLI resolve them by calling EC2
+DescribeAvailabilityZones on the target environment.
To specify a different strategy for selecting availability zones override this method.
+If this is a nested stack, returns it's parent stack.
+Indicates whether the stack requires bundling or not
+StaticisReturn whether the given object is a Stack.
+We do attribute detection since we can't reliably use 'instanceof'.
+StaticofLooks up the first stack scope in which construct is defined. Fails if there is no stack up the tree.
The construct to start the search from.
+Resolve a tokenized value in the context of the current stack.
+Convert an object, potentially containing tokens, to a JSON string
+Optionalspace: numberConvert an object, potentially containing tokens, to a YAML string
+Indicate that a context key was expected
+Contains instructions which will be emitted into the cloud assembly on how +the key should be supplied.
+The set of parameters needed to obtain the context
+Rename a generated logical identities
+To modify the naming scheme strategy, extend the Stack class and
+override the allocateLogicalId method.
Allocates a stack-unique CloudFormation-compatible logical identity for a +specific resource.
+This method is called when a CfnElement is created and used to render the
+initial logical identity of resources. Logical ID renames are applied at
+this stage.
This method uses the protected method allocateLogicalId to render the
+logical ID for an element. To modify the naming scheme, extend the Stack
+class and override this method.
The CloudFormation element for which a logical identity is +needed.
+Add a dependency between this stack and another stack.
+This can be used to define dependencies between any two stacks within an +app, and also supports nested stacks.
+Optionalreason: stringCreates an ARN from components.
+If partition, region or account are not specified, the stack's
+partition, region and account will be used.
If any component is the empty string, an empty string will be inserted +into the generated ARN at the location that component corresponds to.
+The ARN will be formatted as follows:
+arn:{partition}:{service}:{region}:{account}:{resource}{sep}{resource-name}
+The required ARN pieces that are omitted will be taken from the stack that +the 'scope' is attached to. If all ARN pieces are supplied, the supplied scope +can be 'undefined'.
+Splits the provided ARN into its components. +Works both if 'arn' is a string like 'arn:aws:s3:::bucket', +and a Token representing a dynamic CloudFormation expression +(in which case the returned components will also be dynamic CloudFormation expressions, +encoded as Tokens).
+the ARN to split into its components
+the expected format of 'arn' - depends on what format the service 'arn' represents uses
+Add a Transform to this stack. A Transform is a macro that AWS +CloudFormation uses to process your template.
+Duplicate values are removed when stack is synthesized.
+The transform to add
+Adds an arbitrary key-value pair, with information you want to record about the stack. +These get translated to the Metadata section of the generated template.
+InternalCalled implicitly by the addDependency helper function in order to
+realize a dependency between two top-level stacks at the assembly level.
Use stack.addDependency to define the dependency between any two stacks,
+and take into account nested stack relationships.
Optionalreason: StackDependencyReasonInternalCalled implicitly by the obtainDependencies helper function in order to
+collect resource dependencies across two top-level stacks at the assembly level.
Use stack.obtainDependencies to see the dependencies between any two stacks.
InternalCalled implicitly by the removeDependency helper function in order to
+remove a dependency between two top-level stacks at the assembly level.
Use stack.addDependency to define the dependency between any two stacks,
+and take into account nested stack relationships.
OptionalreasonFilter: StackDependencyReasonInternalSynthesizes the cloudformation template into a cloud assembly.
+OptionallookupRoleArn: stringOptionallookupRoleExternalId: stringOptionallookupRoleAdditionalOptions: { [key: string]: any }Look up a fact value for the given fact for the region of this stack
+Will return a definite value only if the region of the current stack is resolved. +If not, a lookup map will be added to the stack and the lookup will be done at +CDK deployment time.
+What regions will be included in the lookup map is controlled by the
+@aws-cdk/core:target-partitions context value: it must be set to a list
+of partitions, and only regions from the given partitions will be included.
+If no such context key is set, all regions will be included.
This function is intended to be used by construct library authors. Application +builders can rely on the abstractions offered by construct libraries and do +not have to worry about regional facts.
+If defaultValue is not given, it is an error if the fact is unknown for
+the given region.
OptionaldefaultValue: stringCreate a CloudFormation Export for a string value
+Returns a string representing the corresponding Fn.importValue()
+expression for this Export. You can control the name for the export by
+passing the name option.
If you don't supply a value for name, the value you're exporting must be
+a Resource attribute (for example: bucket.bucketName) and it will be
+given the same name as the automatic cross-stack reference that would be created
+if you used the attribute in another Stack.
One of the uses for this method is to remove the relationship between +two Stacks established by automatic cross-stack references. It will +temporarily ensure that the CloudFormation Export still exists while you +remove the reference from the consuming stack. After that, you can remove +the resource and the manual export.
+Here is how the process works. Let's say there are two stacks,
+producerStack and consumerStack, and producerStack has a bucket
+called bucket, which is referenced by consumerStack (perhaps because
+an AWS Lambda Function writes into it, or something like that).
It is not safe to remove producerStack.bucket because as the bucket is being
+deleted, consumerStack might still be using it.
Instead, the process takes two deployments:
+Deployment 1: break the relationship:
+consumerStack no longer references bucket.bucketName (maybe the consumer
+stack now uses its own bucket, or it writes to an AWS DynamoDB table, or maybe you just
+remove the Lambda Function altogether).ProducerStack class, call this.exportValue(this.bucket.bucketName). This
+will make sure the CloudFormation Export continues to exist while the relationship
+between the two stacks is being broken.consumerStack, but it's safe to deploy both).Deployment 2: remove the bucket resource:
+bucket resource from producerStack.exportValue() call as well.producerStack will be changed -- the bucket will be deleted).Optionaloptions: ExportValueOptionsCreate a CloudFormation Export for a string list value
+Returns a string list representing the corresponding Fn.importValue()
+expression for this Export. The export expression is automatically wrapped with an
+Fn::Join and the import value with an Fn::Split, since CloudFormation can only
+export strings. You can control the name for the export by passing the name option.
If you don't supply a value for name, the value you're exporting must be
+a Resource attribute (for example: bucket.bucketName) and it will be
+given the same name as the automatic cross-stack reference that would be created
+if you used the attribute in another Stack.
One of the uses for this method is to remove the relationship between +two Stacks established by automatic cross-stack references. It will +temporarily ensure that the CloudFormation Export still exists while you +remove the reference from the consuming stack. After that, you can remove +the resource and the manual export.
+See exportValue for an example of this process.
Optionaloptions: ExportValueOptionsProtectedallocateReturns the naming scheme used to allocate logical IDs. By default, uses
+the HashedAddressingScheme but this method can be overridden to customize
+this behavior.
In order to make sure logical IDs are unique and stable, we hash the resource +construct tree path (i.e. toplevel/secondlevel/.../myresource) and add it as +a suffix to the path components joined without a separator (CloudFormation +IDs only allow alphanumeric characters).
+The result will be:
+<path.join('')><md5(path.join('/')> +"human" "hash"
+If the "human" part of the ID exceeds 240 characters, we simply trim it so +the total ID doesn't exceed CloudFormation's 255 character limit.
+We only take 8 characters from the md5 hash (0.000005 chance of collision).
+Special cases:
+L1/L2/Pipeline/Pipeline), they will be de-duplicated to make the
+resulting human portion of the ID more pleasing: L1L2Pipeline<HASH>
+instead of L1L2PipelinePipeline<HASH>The element for which the logical ID is allocated.
+Protected_InternalValidate stack name
+CloudFormation stack names can include dashes in addition to the regular identifier +character classes, and we don't allow one of the magic markers.
+Protected_InternalReturns the CloudFormation template for this stack by traversing +the tree and invoking _toCloudFormation() on all Entity objects.
+Configure a stack tag
+At deploy time, CloudFormation will automatically apply all stack tags to all resources in the stack.
+Remove a stack tag
+At deploy time, CloudFormation will automatically apply all stack tags to all resources in the stack.
+StaticisChecks if x is a construct.
Use this method instead of instanceof to properly detect Construct
+instances, even when the construct library is symlinked.
Explanation: in JavaScript, multiple copies of the constructs library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class Construct in each copy of the constructs library
+is seen as a different class, and an instance of one class will not test as
+instanceof the other class. npm install will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the constructs
+library can be accidentally installed, and instanceof will behave
+unpredictably. It is safest to avoid using instanceof, and using
+this type-testing method instead.
Any object
+true if x is an object created from a class which extends Construct.
Returns a string representation of this construct.
+Input (Source) data for our PipelineResourcesStack.
+ReadonlytagsTags to be applied to the stack.
+ReadonlytemplateOptions for CloudFormation template (like version, transform, description).
+ReadonlyregionThe AWS region into which this stack will be deployed (e.g. us-west-2).
This value is resolved according to the following rules:
+env.region when the stack is defined. This can
+either be a concrete region (e.g. us-west-2) or the Aws.REGION
+token.Aws.REGION, which is represents the CloudFormation intrinsic reference
+{ "Ref": "AWS::Region" } encoded as a string token.Preferably, you should use the return value as an opaque string and not
+attempt to parse it to implement your logic. If you do, you must first
+check that it is a concrete value an not an unresolved token. If this
+value is an unresolved token (Token.isUnresolved(stack.region) returns
+true), this implies that the user wishes that this stack will synthesize
+into a region-agnostic template. In this case, your code should either
+fail (throw an error, emit a synth error using Annotations.of(construct).addError()) or
+implement some other region-agnostic behavior.
ReadonlyaccountThe AWS account into which this stack will be deployed.
+This value is resolved according to the following rules:
+env.account when the stack is defined. This can
+either be a concrete account (e.g. 585695031111) or the
+Aws.ACCOUNT_ID token.Aws.ACCOUNT_ID, which represents the CloudFormation intrinsic reference
+{ "Ref": "AWS::AccountId" } encoded as a string token.Preferably, you should use the return value as an opaque string and not
+attempt to parse it to implement your logic. If you do, you must first
+check that it is a concrete value an not an unresolved token. If this
+value is an unresolved token (Token.isUnresolved(stack.account) returns
+true), this implies that the user wishes that this stack will synthesize
+into an account-agnostic template. In this case, your code should either
+fail (throw an error, emit a synth error using Annotations.of(construct).addError()) or
+implement some other account-agnostic behavior.
ReadonlyenvironmentThe environment coordinates in which this stack is deployed. In the form
+aws://account/region. Use stack.account and stack.region to obtain
+the specific values, no need to parse.
You can use this value to determine if two stacks are targeting the same +environment.
+If either stack.account or stack.region are not concrete values (e.g.
+Aws.ACCOUNT_ID or Aws.REGION) the special strings unknown-account and/or
+unknown-region will be used respectively to indicate this stack is
+region/account-agnostic.
Optional ReadonlynestedIf this is a nested stack, this represents its AWS::CloudFormation::Stack
+resource. undefined for top-level (non-nested) stacks.
ReadonlytemplateThe name of the CloudFormation template file emitted to the output +directory during synthesis.
+Example value: MyStack.template.json
ReadonlyartifactThe ID of the cloud assembly artifact for this stack.
+ReadonlysynthesizerSynthesis method for this stack
+Readonly Internal_Whether version reporting is enabled for this stack
+Controls whether the CDK Metadata resource is injected
+Readonly Internal_Whether cross region references are enabled for this stack
+Optional Readonly Internal_SNS Notification ARNs to receive stack events.
+ReadonlyvpcThe VPC for the pipeline to reside in.
+ReadonlyecrThe respository to put the build host container in.
+ReadonlypipelineThe artifact bucket
+ReadonlypipelineThe source bucket
+ReadonlypipelineThe output bucket
+Optional ReadonlyloggingThe Cloudwatch logging bucket
+ReadonlyencryptionThe encryption key use across
+ReadonlynodeThe tree node.
+Whether termination protection is enabled for this stack.
+Return the stacks this stack depends on
+The concrete CloudFormation physical stack name.
+This is either the name defined explicitly in the stackName prop or
+allocated based on the stack's location in the construct tree. Stacks that
+are directly defined under the app use their construct id as their stack
+name. Stacks that are defined deeper within the tree will use a hashed naming
+scheme based on the construct path to ensure uniqueness.
If you wish to obtain the deploy-time AWS::StackName intrinsic,
+you can use Aws.STACK_NAME directly.
The partition in which this stack is defined
+The Amazon domain suffix for the region in which this stack is defined
+Returns the list of notification Amazon Resource Names (ARNs) for the current stack.
+Indicates if this is a nested stack, in which case parentStack will include a reference to it's parent.
Returns the list of AZs that are available in the AWS environment +(account/region) associated with this stack.
+If the stack is environment-agnostic (either account and/or region are
+tokens), this property will return an array with 2 tokens that will resolve
+at deploy-time to the first two availability zones returned from CloudFormation's
+Fn::GetAZs intrinsic function.
If they are not available in the context, returns a set of dummy values and
+reports them as missing, and let the CLI resolve them by calling EC2
+DescribeAvailabilityZones on the target environment.
To specify a different strategy for selecting availability zones override this method.
+If this is a nested stack, returns it's parent stack.
+Indicates whether the stack requires bundling or not
+StaticisReturn whether the given object is a Stack.
+We do attribute detection since we can't reliably use 'instanceof'.
+StaticofLooks up the first stack scope in which construct is defined. Fails if there is no stack up the tree.
The construct to start the search from.
+Resolve a tokenized value in the context of the current stack.
+Convert an object, potentially containing tokens, to a JSON string
+Optionalspace: numberConvert an object, potentially containing tokens, to a YAML string
+Indicate that a context key was expected
+Contains instructions which will be emitted into the cloud assembly on how +the key should be supplied.
+The set of parameters needed to obtain the context
+Rename a generated logical identities
+To modify the naming scheme strategy, extend the Stack class and
+override the allocateLogicalId method.
Allocates a stack-unique CloudFormation-compatible logical identity for a +specific resource.
+This method is called when a CfnElement is created and used to render the
+initial logical identity of resources. Logical ID renames are applied at
+this stage.
This method uses the protected method allocateLogicalId to render the
+logical ID for an element. To modify the naming scheme, extend the Stack
+class and override this method.
The CloudFormation element for which a logical identity is +needed.
+Add a dependency between this stack and another stack.
+This can be used to define dependencies between any two stacks within an +app, and also supports nested stacks.
+Optionalreason: stringCreates an ARN from components.
+If partition, region or account are not specified, the stack's
+partition, region and account will be used.
If any component is the empty string, an empty string will be inserted +into the generated ARN at the location that component corresponds to.
+The ARN will be formatted as follows:
+arn:{partition}:{service}:{region}:{account}:{resource}{sep}{resource-name}
+The required ARN pieces that are omitted will be taken from the stack that +the 'scope' is attached to. If all ARN pieces are supplied, the supplied scope +can be 'undefined'.
+Splits the provided ARN into its components. +Works both if 'arn' is a string like 'arn:aws:s3:::bucket', +and a Token representing a dynamic CloudFormation expression +(in which case the returned components will also be dynamic CloudFormation expressions, +encoded as Tokens).
+the ARN to split into its components
+the expected format of 'arn' - depends on what format the service 'arn' represents uses
+Add a Transform to this stack. A Transform is a macro that AWS +CloudFormation uses to process your template.
+Duplicate values are removed when stack is synthesized.
+The transform to add
+Adds an arbitrary key-value pair, with information you want to record about the stack. +These get translated to the Metadata section of the generated template.
+InternalCalled implicitly by the addDependency helper function in order to
+realize a dependency between two top-level stacks at the assembly level.
Use stack.addDependency to define the dependency between any two stacks,
+and take into account nested stack relationships.
Optionalreason: StackDependencyReasonInternalCalled implicitly by the obtainDependencies helper function in order to
+collect resource dependencies across two top-level stacks at the assembly level.
Use stack.obtainDependencies to see the dependencies between any two stacks.
InternalCalled implicitly by the removeDependency helper function in order to
+remove a dependency between two top-level stacks at the assembly level.
Use stack.addDependency to define the dependency between any two stacks,
+and take into account nested stack relationships.
OptionalreasonFilter: StackDependencyReasonInternalSynthesizes the cloudformation template into a cloud assembly.
+OptionallookupRoleArn: stringOptionallookupRoleExternalId: stringOptionallookupRoleAdditionalOptions: { [key: string]: any }Look up a fact value for the given fact for the region of this stack
+Will return a definite value only if the region of the current stack is resolved. +If not, a lookup map will be added to the stack and the lookup will be done at +CDK deployment time.
+What regions will be included in the lookup map is controlled by the
+@aws-cdk/core:target-partitions context value: it must be set to a list
+of partitions, and only regions from the given partitions will be included.
+If no such context key is set, all regions will be included.
This function is intended to be used by construct library authors. Application +builders can rely on the abstractions offered by construct libraries and do +not have to worry about regional facts.
+If defaultValue is not given, it is an error if the fact is unknown for
+the given region.
OptionaldefaultValue: stringCreate a CloudFormation Export for a string value
+Returns a string representing the corresponding Fn.importValue()
+expression for this Export. You can control the name for the export by
+passing the name option.
If you don't supply a value for name, the value you're exporting must be
+a Resource attribute (for example: bucket.bucketName) and it will be
+given the same name as the automatic cross-stack reference that would be created
+if you used the attribute in another Stack.
One of the uses for this method is to remove the relationship between +two Stacks established by automatic cross-stack references. It will +temporarily ensure that the CloudFormation Export still exists while you +remove the reference from the consuming stack. After that, you can remove +the resource and the manual export.
+Here is how the process works. Let's say there are two stacks,
+producerStack and consumerStack, and producerStack has a bucket
+called bucket, which is referenced by consumerStack (perhaps because
+an AWS Lambda Function writes into it, or something like that).
It is not safe to remove producerStack.bucket because as the bucket is being
+deleted, consumerStack might still be using it.
Instead, the process takes two deployments:
+Deployment 1: break the relationship:
+consumerStack no longer references bucket.bucketName (maybe the consumer
+stack now uses its own bucket, or it writes to an AWS DynamoDB table, or maybe you just
+remove the Lambda Function altogether).ProducerStack class, call this.exportValue(this.bucket.bucketName). This
+will make sure the CloudFormation Export continues to exist while the relationship
+between the two stacks is being broken.consumerStack, but it's safe to deploy both).Deployment 2: remove the bucket resource:
+bucket resource from producerStack.exportValue() call as well.producerStack will be changed -- the bucket will be deleted).Optionaloptions: ExportValueOptionsCreate a CloudFormation Export for a string list value
+Returns a string list representing the corresponding Fn.importValue()
+expression for this Export. The export expression is automatically wrapped with an
+Fn::Join and the import value with an Fn::Split, since CloudFormation can only
+export strings. You can control the name for the export by passing the name option.
If you don't supply a value for name, the value you're exporting must be
+a Resource attribute (for example: bucket.bucketName) and it will be
+given the same name as the automatic cross-stack reference that would be created
+if you used the attribute in another Stack.
One of the uses for this method is to remove the relationship between +two Stacks established by automatic cross-stack references. It will +temporarily ensure that the CloudFormation Export still exists while you +remove the reference from the consuming stack. After that, you can remove +the resource and the manual export.
+See exportValue for an example of this process.
Optionaloptions: ExportValueOptionsProtectedallocateReturns the naming scheme used to allocate logical IDs. By default, uses
+the HashedAddressingScheme but this method can be overridden to customize
+this behavior.
In order to make sure logical IDs are unique and stable, we hash the resource +construct tree path (i.e. toplevel/secondlevel/.../myresource) and add it as +a suffix to the path components joined without a separator (CloudFormation +IDs only allow alphanumeric characters).
+The result will be:
+<path.join('')><md5(path.join('/')> +"human" "hash"
+If the "human" part of the ID exceeds 240 characters, we simply trim it so +the total ID doesn't exceed CloudFormation's 255 character limit.
+We only take 8 characters from the md5 hash (0.000005 chance of collision).
+Special cases:
+L1/L2/Pipeline/Pipeline), they will be de-duplicated to make the
+resulting human portion of the ID more pleasing: L1L2Pipeline<HASH>
+instead of L1L2PipelinePipeline<HASH>The element for which the logical ID is allocated.
+Protected_InternalValidate stack name
+CloudFormation stack names can include dashes in addition to the regular identifier +character classes, and we don't allow one of the magic markers.
+Protected_InternalReturns the CloudFormation template for this stack by traversing +the tree and invoking _toCloudFormation() on all Entity objects.
+Configure a stack tag
+At deploy time, CloudFormation will automatically apply all stack tags to all resources in the stack.
+Remove a stack tag
+At deploy time, CloudFormation will automatically apply all stack tags to all resources in the stack.
+StaticisChecks if x is a construct.
Use this method instead of instanceof to properly detect Construct
+instances, even when the construct library is symlinked.
Explanation: in JavaScript, multiple copies of the constructs library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class Construct in each copy of the constructs library
+is seen as a different class, and an instance of one class will not test as
+instanceof the other class. npm install will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the constructs
+library can be accidentally installed, and instanceof will behave
+unpredictably. It is safest to avoid using instanceof, and using
+this type-testing method instead.
Any object
+true if x is an object created from a class which extends Construct.
Returns a string representation of this construct.
+The type of project built.
+Build core-image-minimal from poky.
+Build the Qemu meta-aws Demonstration Distribution.
+Build an EC2 AMI
+Build an kas based image
+Build an Renesas image
+Build an IMX image using NXP layers.
+Build no pipeline, just CodeBuild project to connect with GitHub actions.
+Build an image using a custom buildspec and asstes.
+The aws4embeddedlinux-ci library helps you deploy an AWS cloud infrastructure supporting the Embedded Linux builds for your project using AWS CDK.
This is the overall architecture pattern used to deploy the build pipeline:
+The API documentation is generated automatically using Typedoc.
+ +Several pipelines are provided in this library, each one demonstrating a different aspect of how to build a Yocto image with AWS.
+Once deployed, ou can review the pipeline execution from the Developer Tools > Pipeline - CodePipeline > Pipelines page in the AWS Console.
From the pipeline page, you can find the source repository (S3), the CodeBuild Project (with the build logs), and the S3 bucket that the image is uploaded to, at the end.
+Each pipelines will refresh/re-run automatically every week using AWS EventBridge in order to grab the latest updates.
+The pipeline name will end with poky.
This example will build the core-image-minimal image from Poky using the repo tool to manage layers. CVE checking is also enabled in the buildspec file.
Expected build times:
+The pipeline name will end with poky-ami.
Yocto can be used to create an EC2 AMI. This example builds an AMI based on Poky and meta-aws and exports it to your AMI registry using the VM Import/Export Service.
+Expected build times:
+The pipeline name will end with kas.
The Kas example shows how to use a Kas Config to manage layers.
+This tool can help programatically manage layers and config with tighter Yocto integration than Git Submodules or the Repo tool.
+Expected build times:
+The pipeline name will end with qemu.
This example builds a Qemu based image using meta-aws-demos.
+The Qemu image can be run in the CodeBuild environment. Using SLIRP networking, OEQA testing such as ptest can be run in the pipeline.
+Expected build times:
+The pipeline name will end with nxp.
This example will build an image for the i.MX 6ULL EVK board.
+NXP requires users to accept and comply with a EULA in order to build and, for this reason, the buildspec will require modification before the build succeeds.
+See the IMX Yocto Users Guide for more detail.
+Expected build times:
+This example is based on the Yocto / Renesas R-Car work to build an image for Renesas R-Car-H3 Starter Kit Premier board (unofficial name - H3ULCB) including the proprietary graphics and multimedia drivers from Renesas.
+You will need to download the Multimedia and Graphics library and related Linux drivers from the following link (registration necessary):
+ +Download the following files:
+Graphic drivers are required for Wayland. Multimedia drivers are optional.
+Steps to build the image:
+proprietary in the root of the source repoproprietary folder#TODO line in the build.sh file in the source repoA build should automatically start. Once it succeeds you will get an image containing the proprietary graphics and multimedia drivers.
+Expected build times:
+This will create an AWS CodeBuild project ready to build Embedded Linux which can be used to connect to an external source, e.g. GitHub Actions. This is not using any AWS CodePipeline as in the the Pipeline examples section.
+You can use the following example for your GitHub Action.
+We recommend you to clone the created AWS CodeBuild project and then proceed with the GitHub Action configuration. +However, this will result in the use of the same EFS file system across projects.
+Using the AWS CodeBuild project requires a source to be configured manually in the AWS Console at Developer Tools > Build - CodeBuild > Projects.
To configure the AWS CodeBuild source connection to a GitHub repository, you will need to:
+aws4el-ci-codebuild-project)Project Details tabSource section and click on Edit.GitHub as a Source provider. Configure the access to your repositoryModify your repository GitHub action by replacing the following line:
+runs-on: ${{ vars.CODEBUILD_RUNNER_NAME }}-${{ github.run_id }}-${{ github.run_attempt }}
+
+
+with:
+runs-on: codebuild-<project-name>-${{ github.run_id }}-${{ github.run_attempt }}
+
+
+<project-name> should be replaced by your AWS CodeBuild project name (aws4el-ci-codebuild-project).
+There might be more than one occuerence to replace in the file.
Refer to the following example for more details.
+ +In order to use this library, you must first set up an AWS CDK project, including +installing the CDK tool and bootstrapping the account you wish to deploy to.
+Additionally, you must have NodeJS installed.
+This library is tested against Node Versions 22. If these version is not available for your system, we recommend using NVM to install a compatible version.
+You can also use the sample project code provided to get started and deploy the stacks.
+ +In order to create a new project, you will need to initialize a new CDK project.
+More details can be found in the CDK Getting Started Documentation.
+The following commands will create a new CDK project named my-project:
mkdir my-project
cd my-project
cdk init app --language typescript
+
+
+Then you will need to install the CDK library including the aws4embeddedlinux-ci library either using npm:
npm install aws4embeddedlinux/aws4embeddedlinux-ci
+
+
+of `yarn':
+yarn add aws4embeddedlinux-cdk-lib@aws4embeddedlinux/aws4embeddedlinux-ci
yarn install
+
+
+++If you are not familliar with Yarn, please refer to the documentation.
+
Once added, you can start creatin your application using the library.
+For example, you can start by importing classes using:
+import {
EmbeddedLinuxCodePipelineBaseImageStack,
EmbeddedLinuxCodePipelineStack,
EmbeddedLinuxCodeBuildProjectStack,
PipelineResourcesStack,
ProjectType,
} from "aws4embeddedlinux-cdk-lib";
+
+
+Then deploy the base resources and base image pipeline stacks:
+const pipelineResourcesStack = new PipelineResourcesStack(app, `demo-resources`, {...});
const baseImageStack = new EmbeddedLinuxCodePipelineBaseImageStack(app, `demo-pipeline-base-image`, {...});
+
+
+And ultimately deploy the target pipeline:
+const projectPipeline = new EmbeddedLinuxCodePipelineStack(app, "demo-project", {
projectType: ProjectType.Poky,
ecrRepository: <ecrRepository>,
ecrRepositoryImageTag: <ecrRepositoryImageTag>,
pipelineSourceBucket: <SourceBucket>,
pipelineArtifactBucket: <ArtifactBucket>,
pipelineOutputBucket: <OutputBucket>,
vpc: <vpc>,
encryptionKey: <encryptionKey>,
});
+
+
+Refer to the API Documentation and the sample for more details.
+Once you have completed the code of your application, you can deploy the CDK stack using:
+cdk deploy
+
+
+After the CDK application is successfully deployed, the 'Base Image' pipeline needs to complete successfully.
+This will create an Ubuntu based container for building the Yocto images.
+This container is used by the other pipelines. If the other pipelines are run before this container is created and pushed to ECR, they will fail.
+The 'Base Image' pipeline will run weekly by default to keep the container patched and up to date.
+We recommend you to deploy first the 'Base Image' pipeline and once the pipeline completes successfully, then you can deploy the other pipelines in you application as described in the sample.
+Once your pipelines completes successfully, the Yocto deploy directory generated content will be pushed into a S3 bucket.
+ +The repository is leveraging Yarn 2 and if you are not familliar with Yarn, please refer to the documentation.
+If you are looking to develop new feature, you can use yarn link to develop with a local copy of this repo.
In this library repo, execute the following:
+yarn install
yarn run build
yarn link
+
+
+and in your project folder:
+yarn install
yarn link "aws4embeddedlinux-cdk-lib"
yarn run build
+
+
+This will link through the system node_modules install.
++Note:
+You should not install / reference the
+aws4embeddedlinux/aws4embeddedlinux-cilibrary in yourpackage.jsonwhen using this approach.
++Note:
+After changing the code for the
+aws4embeddedlinux/aws4embeddedlinux-cilibrary, you will need to runyarn run buildfor changes to be available in your current project.
++Note:
+When using a system node install on Linux, this can require sudo access. +To avoid this, use a node version manager or set a node prefix.
+
AWS Secrets Manager is the preferred method for adding and using secrets in your pipelines.
+The service provides a structured means of access and avoids the pitfalls of putting secrets in environment variables, source repos, etc.
+The following steps detaisl at a high level, how you can enable the use of AWS Secrets Manager in your pipelines:
+Create a Secret in Secrets Manager and add your secret value.
+Grant access permissions to the CodeBuild pipeline project.
+Create a Policy Statement which allows secretsmanager:GetSecretValue for your secret.
Add this policy statement to the buildPolicyAdditions props for the EmbeddedLinuxPipelineStack. e.g.
import * as iam from "aws-cdk-lib/aws-iam";
const projectPipeline = new EmbeddedLinuxCodePipelineStack(app, "MyPokyPipeline", {
projectType: ProjectType.Poky,
ecrRepository: <ecrRepository>,
ecrRepositoryImageTag: <ecrRepositoryImageTag>,
pipelineSourceBucket: <SourceBucket>,
pipelineArtifactBucket: <ArtifactBucket>,
pipelineOutputBucket: <OutputBucket>,
vpc: <vpc>,
encryptionKey: <encryptionKey>,
buildPolicyAdditions: [
iam.PolicyStatement.fromJson({
Effect: "Allow",
Action: "secretsmanager:GetSecretValue",
Resource:
"arn:aws:secretsmanager:us-west-2:123456789012:secret:my-secret-??????",
}),
],
});
+
+
+The secret can then be used in the CodeBuild Project by adding it to the BuildSpec.
+env:
secrets-manager:
SECRET_VALUE: "<Secret ARN>"
+
+
+See the CodeBuild Documentation for more details.
+CVE checking is enabled in the reference implementations. Details on this can be found in the Yocto documentation.
+ +See SECURITY for more information about reporting issues with this project.
+ +See CONTRIBUTING for more information.
+ +This library is licensed under the MIT-0 License. See the LICENSE file.
+ +Properties to allow customizing the build.
+Optional ReadonlydescriptionA description of the stack.
+Optional ReadonlyenvThe AWS environment (account/region) where this stack will be deployed.
+Set the region/account fields of env to either a concrete value to
+select the indicated environment (recommended for production stacks), or to
+the values of environment variables
+CDK_DEFAULT_REGION/CDK_DEFAULT_ACCOUNT to let the target environment
+depend on the AWS credentials/configuration that the CDK CLI is executed
+under (recommended for development stacks).
If the Stack is instantiated inside a Stage, any undefined
+region/account fields from env will default to the same field on the
+encompassing Stage, if configured there.
If either region or account are not set nor inherited from Stage, the
+Stack will be considered "environment-agnostic"". Environment-agnostic
+stacks can be deployed to any environment but may not be able to take
+advantage of all features of the CDK. For example, they will not be able to
+use environmental context lookups such as ec2.Vpc.fromLookup and will not
+automatically translate Service Principals to the right format based on the
+environment's AWS partition, and other such enhancements.
// Use a concrete account and region to deploy this stack to:
// `.account` and `.region` will simply return these values.
new Stack(app, 'Stack1', {
env: {
account: '123456789012',
region: 'us-east-1'
},
});
// Use the CLI's current credentials to determine the target environment:
// `.account` and `.region` will reflect the account+region the CLI
// is configured to use (based on the user CLI credentials)
new Stack(app, 'Stack2', {
env: {
account: process.env.CDK_DEFAULT_ACCOUNT,
region: process.env.CDK_DEFAULT_REGION
},
});
// Define multiple stacks stage associated with an environment
const myStage = new Stage(app, 'MyStage', {
env: {
account: '123456789012',
region: 'us-east-1'
}
});
// both of these stacks will use the stage's account/region:
// `.account` and `.region` will resolve to the concrete values as above
new MyStack(myStage, 'Stack1');
new YourStack(myStage, 'Stack2');
// Define an environment-agnostic stack:
// `.account` and `.region` will resolve to `{ "Ref": "AWS::AccountId" }` and `{ "Ref": "AWS::Region" }` respectively.
// which will only resolve to actual values by CloudFormation during deployment.
new MyStack(app, 'Stack1');
+
+
+Optional ReadonlystackName to deploy the stack with
+Optional ReadonlytagsTags that will be applied to the Stack
+These tags are applied to the CloudFormation Stack itself. They will not +appear in the CloudFormation template.
+However, at deployment time, CloudFormation will apply these tags to all
+resources in the stack that support tagging. You will not be able to exempt
+resources from tagging (using the excludeResourceTypes property of
+Tags.of(...).add()) for tags applied in this way.
Optional ReadonlynotificationSNS Topic ARNs that will receive stack events.
+Optional ReadonlysynthesizerSynthesis method to use while deploying this stack
+The Stack Synthesizer controls aspects of synthesis and deployment, +like how assets are referenced and what IAM roles to use. For more +information, see the README of the main CDK package.
+If not specified, the defaultStackSynthesizer from App will be used.
+If that is not specified, DefaultStackSynthesizer is used if
+@aws-cdk/core:newStyleStackSynthesis is set to true or the CDK major
+version is v2. In CDK v1 LegacyStackSynthesizer is the default if no
+other synthesizer is specified.
Optional ReadonlyterminationWhether to enable termination protection for this stack.
+Optional ReadonlyanalyticsInclude runtime versioning information in this Stack
+Optional ReadonlycrossEnable this flag to allow native cross region stack references.
+Enabling this will create a CloudFormation custom resource +in both the producing stack and consuming stack in order to perform the export/import
+This feature is currently experimental
+Optional ReadonlypermissionsOptions for applying a permissions boundary to all IAM Roles +and Users created within this Stage
+Optional ReadonlysuppressEnable this flag to suppress indentation in generated +CloudFormation templates.
+If not specified, the value of the @aws-cdk/core:suppressTemplateIndentation
+context key will be used. If that is not specified, then the
+default value false will be used.
Optional ReadonlypropertyA list of IPropertyInjector attached to this Stack.
+ReadonlyecrECR Repository where the Build Host Image resides.
+ReadonlyecrTag for the Build Host Image
+ReadonlyvpcVPC where the networking setup resides.
+Optional ReadonlybuildAdditional policy statements to add to the build project.
+ReadonlyencryptionThe encryption key use across
+Select options for the BuildImageCodePipelineStack.
+Optional ReadonlydescriptionA description of the stack.
+Optional ReadonlyenvThe AWS environment (account/region) where this stack will be deployed.
+Set the region/account fields of env to either a concrete value to
+select the indicated environment (recommended for production stacks), or to
+the values of environment variables
+CDK_DEFAULT_REGION/CDK_DEFAULT_ACCOUNT to let the target environment
+depend on the AWS credentials/configuration that the CDK CLI is executed
+under (recommended for development stacks).
If the Stack is instantiated inside a Stage, any undefined
+region/account fields from env will default to the same field on the
+encompassing Stage, if configured there.
If either region or account are not set nor inherited from Stage, the
+Stack will be considered "environment-agnostic"". Environment-agnostic
+stacks can be deployed to any environment but may not be able to take
+advantage of all features of the CDK. For example, they will not be able to
+use environmental context lookups such as ec2.Vpc.fromLookup and will not
+automatically translate Service Principals to the right format based on the
+environment's AWS partition, and other such enhancements.
// Use a concrete account and region to deploy this stack to:
// `.account` and `.region` will simply return these values.
new Stack(app, 'Stack1', {
env: {
account: '123456789012',
region: 'us-east-1'
},
});
// Use the CLI's current credentials to determine the target environment:
// `.account` and `.region` will reflect the account+region the CLI
// is configured to use (based on the user CLI credentials)
new Stack(app, 'Stack2', {
env: {
account: process.env.CDK_DEFAULT_ACCOUNT,
region: process.env.CDK_DEFAULT_REGION
},
});
// Define multiple stacks stage associated with an environment
const myStage = new Stage(app, 'MyStage', {
env: {
account: '123456789012',
region: 'us-east-1'
}
});
// both of these stacks will use the stage's account/region:
// `.account` and `.region` will resolve to the concrete values as above
new MyStack(myStage, 'Stack1');
new YourStack(myStage, 'Stack2');
// Define an environment-agnostic stack:
// `.account` and `.region` will resolve to `{ "Ref": "AWS::AccountId" }` and `{ "Ref": "AWS::Region" }` respectively.
// which will only resolve to actual values by CloudFormation during deployment.
new MyStack(app, 'Stack1');
+
+
+Optional ReadonlystackName to deploy the stack with
+Optional ReadonlytagsTags that will be applied to the Stack
+These tags are applied to the CloudFormation Stack itself. They will not +appear in the CloudFormation template.
+However, at deployment time, CloudFormation will apply these tags to all
+resources in the stack that support tagging. You will not be able to exempt
+resources from tagging (using the excludeResourceTypes property of
+Tags.of(...).add()) for tags applied in this way.
Optional ReadonlynotificationSNS Topic ARNs that will receive stack events.
+Optional ReadonlysynthesizerSynthesis method to use while deploying this stack
+The Stack Synthesizer controls aspects of synthesis and deployment, +like how assets are referenced and what IAM roles to use. For more +information, see the README of the main CDK package.
+If not specified, the defaultStackSynthesizer from App will be used.
+If that is not specified, DefaultStackSynthesizer is used if
+@aws-cdk/core:newStyleStackSynthesis is set to true or the CDK major
+version is v2. In CDK v1 LegacyStackSynthesizer is the default if no
+other synthesizer is specified.
Optional ReadonlyterminationWhether to enable termination protection for this stack.
+Optional ReadonlyanalyticsInclude runtime versioning information in this Stack
+Optional ReadonlycrossEnable this flag to allow native cross region stack references.
+Enabling this will create a CloudFormation custom resource +in both the producing stack and consuming stack in order to perform the export/import
+This feature is currently experimental
+Optional ReadonlypermissionsOptions for applying a permissions boundary to all IAM Roles +and Users created within this Stage
+Optional ReadonlysuppressEnable this flag to suppress indentation in generated +CloudFormation templates.
+If not specified, the value of the @aws-cdk/core:suppressTemplateIndentation
+context key will be used. If that is not specified, then the
+default value false will be used.
Optional ReadonlypropertyA list of IPropertyInjector attached to this Stack.
+ReadonlypipelineThe pipeline source bucket
+OptionalpipelineThe pipeline source prefix
+ReadonlypipelineArtifact bucket to use
+ReadonlyecrThe ECR Repository to push to.
+ReadonlyencryptionThe encryption key use across
+Properties to allow customizing the build.
+Optional ReadonlydescriptionA description of the stack.
+Optional ReadonlyenvThe AWS environment (account/region) where this stack will be deployed.
+Set the region/account fields of env to either a concrete value to
+select the indicated environment (recommended for production stacks), or to
+the values of environment variables
+CDK_DEFAULT_REGION/CDK_DEFAULT_ACCOUNT to let the target environment
+depend on the AWS credentials/configuration that the CDK CLI is executed
+under (recommended for development stacks).
If the Stack is instantiated inside a Stage, any undefined
+region/account fields from env will default to the same field on the
+encompassing Stage, if configured there.
If either region or account are not set nor inherited from Stage, the
+Stack will be considered "environment-agnostic"". Environment-agnostic
+stacks can be deployed to any environment but may not be able to take
+advantage of all features of the CDK. For example, they will not be able to
+use environmental context lookups such as ec2.Vpc.fromLookup and will not
+automatically translate Service Principals to the right format based on the
+environment's AWS partition, and other such enhancements.
// Use a concrete account and region to deploy this stack to:
// `.account` and `.region` will simply return these values.
new Stack(app, 'Stack1', {
env: {
account: '123456789012',
region: 'us-east-1'
},
});
// Use the CLI's current credentials to determine the target environment:
// `.account` and `.region` will reflect the account+region the CLI
// is configured to use (based on the user CLI credentials)
new Stack(app, 'Stack2', {
env: {
account: process.env.CDK_DEFAULT_ACCOUNT,
region: process.env.CDK_DEFAULT_REGION
},
});
// Define multiple stacks stage associated with an environment
const myStage = new Stage(app, 'MyStage', {
env: {
account: '123456789012',
region: 'us-east-1'
}
});
// both of these stacks will use the stage's account/region:
// `.account` and `.region` will resolve to the concrete values as above
new MyStack(myStage, 'Stack1');
new YourStack(myStage, 'Stack2');
// Define an environment-agnostic stack:
// `.account` and `.region` will resolve to `{ "Ref": "AWS::AccountId" }` and `{ "Ref": "AWS::Region" }` respectively.
// which will only resolve to actual values by CloudFormation during deployment.
new MyStack(app, 'Stack1');
+
+
+Optional ReadonlystackName to deploy the stack with
+Optional ReadonlytagsTags that will be applied to the Stack
+These tags are applied to the CloudFormation Stack itself. They will not +appear in the CloudFormation template.
+However, at deployment time, CloudFormation will apply these tags to all
+resources in the stack that support tagging. You will not be able to exempt
+resources from tagging (using the excludeResourceTypes property of
+Tags.of(...).add()) for tags applied in this way.
Optional ReadonlynotificationSNS Topic ARNs that will receive stack events.
+Optional ReadonlysynthesizerSynthesis method to use while deploying this stack
+The Stack Synthesizer controls aspects of synthesis and deployment, +like how assets are referenced and what IAM roles to use. For more +information, see the README of the main CDK package.
+If not specified, the defaultStackSynthesizer from App will be used.
+If that is not specified, DefaultStackSynthesizer is used if
+@aws-cdk/core:newStyleStackSynthesis is set to true or the CDK major
+version is v2. In CDK v1 LegacyStackSynthesizer is the default if no
+other synthesizer is specified.
Optional ReadonlyterminationWhether to enable termination protection for this stack.
+Optional ReadonlyanalyticsInclude runtime versioning information in this Stack
+Optional ReadonlycrossEnable this flag to allow native cross region stack references.
+Enabling this will create a CloudFormation custom resource +in both the producing stack and consuming stack in order to perform the export/import
+This feature is currently experimental
+Optional ReadonlypermissionsOptions for applying a permissions boundary to all IAM Roles +and Users created within this Stage
+Optional ReadonlysuppressEnable this flag to suppress indentation in generated +CloudFormation templates.
+If not specified, the value of the @aws-cdk/core:suppressTemplateIndentation
+context key will be used. If that is not specified, then the
+default value false will be used.
Optional ReadonlypropertyA list of IPropertyInjector attached to this Stack.
+ReadonlypipelineThe pipeline source bucket
+OptionalpipelineThe pipeline source prefix
+ReadonlypipelineThe pipeline artifact bucket to use
+OptionalpipelineThe pipeline artifact bucket prefix to use
+ReadonlypipelineThe pipeline output bucket to use
+OptionalpipelineThe pipeline output bucket prefix to use
+ReadonlyecrECR Repository where the Build Host Image resides.
+ReadonlyecrTag for the Build Host Image
+ReadonlyprojectThe type of project being built.
+ReadonlyvpcVPC where the networking setup resides.
+Optional ReadonlybuildAdditional policy statements to add to the build project.
+Optional ReadonlyenvironmentAdditional build environment variables to the build project.
+ReadonlyencryptionThe encryption key use across
+Optional ReadonlysourceCustom asset to be provided when using ProjectType.Custom
+Select options for the PipelineResourcesStack.
+Optional ReadonlydescriptionA description of the stack.
+Optional ReadonlyenvThe AWS environment (account/region) where this stack will be deployed.
+Set the region/account fields of env to either a concrete value to
+select the indicated environment (recommended for production stacks), or to
+the values of environment variables
+CDK_DEFAULT_REGION/CDK_DEFAULT_ACCOUNT to let the target environment
+depend on the AWS credentials/configuration that the CDK CLI is executed
+under (recommended for development stacks).
If the Stack is instantiated inside a Stage, any undefined
+region/account fields from env will default to the same field on the
+encompassing Stage, if configured there.
If either region or account are not set nor inherited from Stage, the
+Stack will be considered "environment-agnostic"". Environment-agnostic
+stacks can be deployed to any environment but may not be able to take
+advantage of all features of the CDK. For example, they will not be able to
+use environmental context lookups such as ec2.Vpc.fromLookup and will not
+automatically translate Service Principals to the right format based on the
+environment's AWS partition, and other such enhancements.
// Use a concrete account and region to deploy this stack to:
// `.account` and `.region` will simply return these values.
new Stack(app, 'Stack1', {
env: {
account: '123456789012',
region: 'us-east-1'
},
});
// Use the CLI's current credentials to determine the target environment:
// `.account` and `.region` will reflect the account+region the CLI
// is configured to use (based on the user CLI credentials)
new Stack(app, 'Stack2', {
env: {
account: process.env.CDK_DEFAULT_ACCOUNT,
region: process.env.CDK_DEFAULT_REGION
},
});
// Define multiple stacks stage associated with an environment
const myStage = new Stage(app, 'MyStage', {
env: {
account: '123456789012',
region: 'us-east-1'
}
});
// both of these stacks will use the stage's account/region:
// `.account` and `.region` will resolve to the concrete values as above
new MyStack(myStage, 'Stack1');
new YourStack(myStage, 'Stack2');
// Define an environment-agnostic stack:
// `.account` and `.region` will resolve to `{ "Ref": "AWS::AccountId" }` and `{ "Ref": "AWS::Region" }` respectively.
// which will only resolve to actual values by CloudFormation during deployment.
new MyStack(app, 'Stack1');
+
+
+Optional ReadonlystackName to deploy the stack with
+Optional ReadonlytagsTags that will be applied to the Stack
+These tags are applied to the CloudFormation Stack itself. They will not +appear in the CloudFormation template.
+However, at deployment time, CloudFormation will apply these tags to all
+resources in the stack that support tagging. You will not be able to exempt
+resources from tagging (using the excludeResourceTypes property of
+Tags.of(...).add()) for tags applied in this way.
Optional ReadonlynotificationSNS Topic ARNs that will receive stack events.
+Optional ReadonlysynthesizerSynthesis method to use while deploying this stack
+The Stack Synthesizer controls aspects of synthesis and deployment, +like how assets are referenced and what IAM roles to use. For more +information, see the README of the main CDK package.
+If not specified, the defaultStackSynthesizer from App will be used.
+If that is not specified, DefaultStackSynthesizer is used if
+@aws-cdk/core:newStyleStackSynthesis is set to true or the CDK major
+version is v2. In CDK v1 LegacyStackSynthesizer is the default if no
+other synthesizer is specified.
Optional ReadonlyterminationWhether to enable termination protection for this stack.
+Optional ReadonlyanalyticsInclude runtime versioning information in this Stack
+Optional ReadonlycrossEnable this flag to allow native cross region stack references.
+Enabling this will create a CloudFormation custom resource +in both the producing stack and consuming stack in order to perform the export/import
+This feature is currently experimental
+Optional ReadonlypermissionsOptions for applying a permissions boundary to all IAM Roles +and Users created within this Stage
+Optional ReadonlysuppressEnable this flag to suppress indentation in generated +CloudFormation templates.
+If not specified, the value of the @aws-cdk/core:suppressTemplateIndentation
+context key will be used. If that is not specified, then the
+default value false will be used.
Optional ReadonlypropertyA list of IPropertyInjector attached to this Stack.
+Readonlyresource_The resource prefix
+Optional ReadonlyecrThe ecr repository name - if not provided then the name will be '{prefix}-{account}-{region}-repo'
+Optional ReadonlypipelineThe artifact bucket name - if not provided then the name will be '{prefix}-{account}-{region}-artifact'
+Optional ReadonlypipelineThe source bucket name - if not provided then the name will be '{prefix}-{account}-{region}-source'
+Optional ReadonlypipelineThe output bucket name - if not provided then the name will be '{prefix}-{account}-{region}-output'
+Optional ReadonlyloggingCloudwatch logging bucket name - if not provided then the name will be '{prefix}-{account}-{region}-logs'
+
The stack for creating a build pipeline.
+See EmbeddedLinuxCodeBuildProjectProps for configration options.
+