AWS Integration

The AWS Integration allows you to automatically import a connection folder hierarchy that mirrors your AWS Organization folder structure, with a connection folder for each AWS OU and a connection for each account in your AWS organization.

The AWS integration will automatically keep the configuration up to date as your organization changes, adding, removing, and modifying connections and folders as accounts and OUs are created, deleted, or changed in your AWS Organization.

Creating the AWS Integration

You can create an integration for a tenant or an organization, and where you create the integration affects the scope of the resources it creates; the resulting connections and folders can only be shared within the entity in which it was created.

First, navigate to the Integrations page for the appropriate resource:

• To configure an AWS integration for your Tenant, click the double arrow button from the tenant switcher at the top of the Pipes console, select your tenant, and then select Tenant Settings. This option will only be visible in a custom tenant for which you are a tenant owner. Once you've selected your tenant, go to the Integrations tab to manage the integrations for the tenant.
• To configure an AWS integration for your Organization, click the double arrow button from the organization switcher at the top of the page and select the organization from the dropdown. Once you've selected your organization, go to the Integrations tab to manage the integrations for the organization.

Next, click the New Integration button. You will be asked to select an integration to create.

Select AWS and click Next.

Provide a Handle for the integration.

This handle should be meaningful and must be unique for all integrations in the tenant (including any org-level integrations). Click Next.

Configure the Discovery Settings, including the credentials that Pipes should use to discover the organization's resources.

These credentials need permission to read the organization data in the AWS Organizations master account. You may either authenticate using a cross-account role (recommended) or an access key pair.

• To use a cross-account role, select Cross-Account Role from the Access Mode dropdown. You will need to create a role in the account that has the correct trust policy and permissions. You can do this manually, or Pipes can generate a Terraform or CloudFormation template for you to download and run. Depending on your preference, follow the Automatic Setup or Manual Setup instructions, then enter the Role ARN and External ID. Click the Test Discovery button to verify that the credentials are configured correctly.

• To use a key pair, select Access Key from the Access Mode dropdown. Enter the Access Key and Secret Key.

Click Next.

Configure the Connection settings.

Optionally, provide a Handle Prefix to be pre-pended to the names of connections created from this integration. This is optional but may be useful for organizational purposes, or to ensure the uniqueness of the generated connection handles.

Next, set up the trust relationship for the discovered accounts. In order for Pipes to access the discovered accounts, a cross-account role must be created in each discovered account. You can set these roles up manually, or Pipes can generate a CloudFormation StackSet to help automate the process. Depending on your preference, follow the Automatic Setup or Manual Setup instructions, then enter the Role Name and External ID. Pipes will dynamically generate the Role ARN for each discovered account based on its ID and the provided Role Name. Choose the Regions that you would like configured in the child connections.

If desired, you can set advanced options for the child connections.

These options will be inherited by all connections imported by the integration. You can also set or change these options on a per-connection basis after the connections have been imported.

Click the Test Connection button to verify that the credentials are configured correctly, then click Next.

Finally, select the Permissions.

The permissions on this screen apply to the top-level folders and therefore to all connections and folders discovered by this integration. If you want to assign permissions more granularly, on a per-subfolder or per-connection basis, select No Permissions at this time, and then manage the permissions on the connections and folders once they have been discovered.

Note also that All Workspaces will not only add permissions for the existing organization workspaces but will also allow access for any new workspaces that are created.

After you have made your selections, click Create Integration. Pipes will begin discovering your accounts and OUs and creating folders and connections.

Modifying the AWS Integration

After you have created an integration, you can change its Handle, Handle Prefix, or Credentials. You can also change the Permissions and Handle individually for each child folder or connection.

Modifying the integration after it has been created will potentially impact any workspaces that use its connections!

• Changing the Handle Prefix will change the handles of all of its connections. This means that the schema names will change in any workspace to which they are attached. The schema names, in turn, impact the search path and aggregators that use wildcards.
• Discovery of accounts and OUs occurs using the supplied Credentials. If changing the credentials affects access to these accounts and OUs that will be reflected in the folders and connections. For example, if the new credentials do not have access to some OUs or accounts that were visible to the previous credentials, then the corresponding folders and connections will be deleted and removed from any workspaces where they are attached.

To modify the integration, navigate to the Integrations page for the appropriate resource:

• To configure an AWS integration for your Tenant, click the double arrow button from the tenant switcher at the top of the Pipes console, select your tenant, and then select Tenant Settings. This option will only be visible in a custom tenant for which you are a tenant owner. Once you've selected your tenant, go to the Integrations tab to manage the integrations for the tenant.
• To configure an AWS integration for your Organization, click the double arrow button from the organization switcher at the top of the page and select the organization from the dropdown. Once you've selected your organization, go to the Integrations tab to manage the integrations for the organization.

In the list of integrations, click the gear icon next to the integration that you want to modify.

You can change credentials used for discovert in the Discovery Settings section of the Config tab.

You can also change the Connection Settings from the Config tab, including the Handle Prefix, Regions, the connection credentials, and the Advanced Options,

Make the desired changes and click Save.

You can modify the Handle from the Advanced tab.

Enter the new handle and click Save.

You can view the connection tree from the Connections tab. Click on a connection or folder to view or change its properties. You can change the Permissions and Handle from its Settings tab.

Deleting the AWS Integration

You can delete an integration from its Advanced page.

If you delete an integration, all of its associated folders and connections will be deleted and removed from all workspaces. This action is not reversible!

Navigate to the Integrations page for the appropriate resource:

• To delete an AWS integration for your Tenant, click the double arrow button from the tenant switcher at the top of the Pipes console, select your tenant, and then select Tenant Settings. This option will only be visible in a custom tenant for which you are a tenant owner. Once you've selected your tenant, go to the Integrations tab to manage the integrations for the tenant.
• To delete an AWS integration for your Organization, click the double arrow button from the organization switcher at the top of the page and select the organization from the dropdown. Once you've selected your organization, go to the Integrations tab to manage the integrations for the organization.

Go to the Advanced page and click the Delete Integration button.

You will be asked to enter the handle to confirm deletion.

If you wish to permanently delete the integration and all of its resources, click Delete.