🔗Connector

Connectors in our platform are represented as arrows in the UI flowing from one resource to another resource. They visually show how different resources are connected in the architecture.

Connectors are created by using the arrow tool and dragging it from one resource to another.

Connector flowing from one resource to another resource

Connecting Resources

Connectors can only connect two resources if their input and output types match up as a valid pair. When you enter the connector tool, incompatible resources will be greyed out and only relevant resources highlighted to show possible connections.

Compatible resources highlighted and incompatible ones greyed out when creating a connector

There are different subtypes of connections depending on the resource types being connected.

For example, an S3 trigger connector has properties to specify if it should activate on object creation or deletion events.

Some common examples:

• Connect an S3 or SQS trigger to a Lambda Function to activate the function
• Connect a CloudWatch alarm to a Load Balancer to modify it when thresholds are crossed

Permissions

In many cases, creating a connector will also automatically grant the necessary read permissions for the receiving resource to access the source resource.

For example, connecting an SQS Queue to a Lambda Function allows the function to read messages from the queue.

Example of a connector granting permissions from one resource to another