Articles in this section

Run operations on different servers in stacks

integrator.io is a distributed system where different components can run on different servers to perform multiple operations efficiently. You can store references to other servers in the stack, and integrator.io can invoke resources on servers you reference in the stack during runtime. Hooks and wrappers are integrator.io extensions that run on separate servers that integrator.io can call during runtime. A stack can be one server or a set of servers running behind a load balancer. Store the system token for the stack as an environment variable (INTEGRATOR_EXTENSION_SYSTEM_TOKEN) on the server where the extension code is running.

integrator.io supports execution of extension functions through the following extension types:

  1. Express based app running on a server

  2. AWS Lambda.

Note

Click Resources > Stacks to see the list of all previously created stacks.

Create an AWS Lambda stack

Use the following steps to create a AWS Lambda stack:

  1. Navigate to Resources > Stacks. You'll need to have Developer Mode enabled to access Stacks.

  2. Click + Create stack.

  3. In the Name field, enter an appropriate name for the stack that you are about to create.

  4. Use the drop-down list in the Type field to select AWS Lambda.

    4403977512973-awsLambdaStacks.png
  5. Enter the Access Key Id and the Secret Access Key.

  6. Select the region from the AWS Region drop-down list.

  7. Enter the Function name.

  8. Select C#, Java, Node.js, or Other from the Language drop-down list.

  9. Click Save & close.

Create a server stack

Use the following steps to create a server stack:

  1. Navigate to Resources > Stacks. You'll need to have Developer Mode enabled to access Stacks.

  2. Click + Create stack.

  3. In the Name field, enter an appropriate name for the stack that you are about to create.

  4. Use the drop-down list in the Type field to select Server.

  5. Enter the server URL in the Host field.

  6. Click Save & close.

Share stacks with other users

Use the following steps to share a stack:

  1. Click Resources > Stacks to see the list of all previously created stacks.

  2. Click the Actions overflow (...) menu for the stack and select Share stack.

  3. Click +Invite user.

  4. Enter the email address of the integrator.io user you want to share the stack with.

The user you've shared a stack with receives a notification that the stack has been shared with them. Until they accept the shared stack with the link in the notification, the Status column value displays as Pending. Once the user accepts, this value changes to Accepted. Click Refresh to see the latest status of your invitation.

After the invited user accepts the shared stack, the stack is available from that user's flow pages.

Remove user access to a shared stack

Use the following steps to remove user access to a shared stack:

  1. Click Resources > Stacks to see the list of all previously created stacks.

  2. Click the Actions overflow (...) menu for the shared item and select Share stack.

  3. You can use the Off/On toggle to temporarily remove a user’s access from a stack. To permanently remove access, click the trash icon in the Action column next to the user whose access to the stack you want to remove.

The share request is permanently deleted from the system, so you must send a new invitation to reshare the stack with that user. You can’t remove user access from a shared stack if the stack is currently in use by that user. In such cases, an error message displays and the share request will not be removed. You can only remove user access to a stack if the stack's reference has been removed from all connections, imports, and exports.

Was this article helpful?
0 out of 0 found this helpful

Comments

2 comments
Date Votes
  • Hi Tom,
    Is there any way to see who shared a stack with a user?

    0
  • Hi Lawrence Morales,

    You can use the audit logs to see the history of modifications to the connection that uses the stack. Let me know if that gets you to the information you're looking for.

    Tom

    0

Please sign in to leave a comment.