Referenced resources represent cloud resources that have been provisioned separately from the current stack. Regular, non-referenced nodes can interact with referenced resources as though they were provisioned together. Examples include:
- Function nodes can be provisioned within an existing AWS Virtual Private Cloud (VPC) by using a Virtual Network referenced resource
- A new Object Store node can be connected to an existing AWS Lambda function that is managed in another Stackery stack
- An AWS Relational Database Service (RDS) database instance can be referenced in order to provide access for Function and Docker nodes within a stack
Stackery uses information about referenced resources to appropriately provision other nodes in the same stack. For example, if an Object Store node is connected to a referenced AWS Lambda function for notifications, Stackery will add a permission to the Lambda function so that it can be invoked by the Object Store.
Referenced resources support all of the interaction mechanisms of normal, non-referenced nodes. For example, the DNS address of a referenced Database can be obtained using either the ‘address’ referenceable property of a Database node or by connecting a Function node to the referenced Database and retrieving the address from the STACKERY_PORTS environment variable.
Creating A Referenced Resource
To create a referenced resource, begin by dragging the “Referenced Resource” node type from the Add Node menu. A dialog box will prompt you for the Amazon Resource Name (ARN) of the resource you want to reference. The following AWS resources are supported:
|AWS Resource||Amazon Resource Name (ARN) Format||Stackery Node Type|
|RDS Database Instance||
After providing the ARN, the new referenced resource of the matching Stackery node type will be placed on the canvas.
A label used for the node in the canvas.
The Amazon Resource Name (ARN) of the referenced resource.