Creating an extended integration for RedShift cluster assets (DRA)

Sync Oomnitza with RedShift cluster assets to gain visibility of the properties of provisioned clusters - including general cluster properties, cluster database properties, maintenance and backup properties, and security and access properties. 

Note
A maximum of 100 records is returned.

See AWS API Documentation: DescribeClusters for information on the API that is used in this integration, 

Before you start

Create an integration user

To easily find the records that are uploaded to Oomnitza, it's best practice to create a dedicated user account for each integration. This will make it easier for you to retrieve the records that are uploaded to Oomnitza from the vendor application. 

Creating integration users 

Configure AWS and Oomnitza to use direct role assumption (DRA)

You can use DRA, a single credential, to access multiple accounts or a single account.

You must complete the configuration of AWS and Oomnitza to create the DRA credential record. When created, you can use the single credential to access AWS accounts.  You use the same credential for all the DRA supported AWS integrations that you use to sync data with Oomnitza.

See DRA integrations: Overview. 

Required information

In the Integration details section, when you add the AWS integration, you enter a space-separated list of regions.

See the table in the Region Availability section in Regions, Availability, Zones, and Local Zones. You enter the region value such as us-east-1.  

Adding integrations

1. In Oomnitza, click Configuration> Integrations> Overview.
2. Click Block view
3. Scroll down to the Extended section for asset integrations.
4. Click NEW INTEGRATION.
5. Select the integration in the sidebar.
6. Click ADD.

Integration details overview

More information is provided about the following fields to help you complete the integration:

Installation types

• Cloud. Store credentials in the Oomnitza cloud.
• Local. Store credentials locally. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select cloud as the type of installation. Local installations don't support AWS and OAuth authentication. 

Integration preferences

• Create & Update. Add and update records.
• Create only. Add records.
• Update only. Update records.

Integration details

To review or update the integrations details, click Edit .

1. Update the integration name.
2. Select an installation type.
3. For integration preferences, select an option.
4. Enter the name of the integration user.
5. Select the Enable Cross-Account checkbox. 

Credential details

Select the credentials record that you created for direct role assumption.

See Step 5: Add credentials to Oomnitza. 

Scheduling the integration

By default, data is synced once every day. Change the interval or the time so that the data is streamed when your system isn't busy.

1. Click Edit .
2. Make and save your changes.

Mapping fields to Oomnitza

To map the fields to Oomnitza, click Edit .

  Select Edit integration to add rules for syncing data. Filtering integration results.  
 

You can add new fields to your integration by selecting Add new field   on the mapping page. 
Creating custom API fields. 

Mappings

To map the fields to Oomnitza, click Edit .

You can define rules for your integration by selecting Edit integration on the mapping page. For example, you may only want to run the integration if a certain contact or region exists. See Filtering integration results.  
You can add new fields to your integration by selecting Add new field  on the mapping page. All you need to do is specify the property name. See Creating custom API fields. 

Creating custom mappings

Map AWS Redshift fields to Oomnitza fields to get the user information that you need.

If you want to map the AWS Status field to Oomnitza, complete these steps first:

1. Click Configuration > Data Model > Field Configuration. By default a list of the asset fields are displayed.
2. Click Add field.
3. Name the field AWS Status.
4. Click the Dropdown checkbox.
5. In the Dropdown tab, enter the following options as separate entries: ACTIVE | PROVISIONING | DEPROVISIONING | FAILED | INACTIVE
6. Click CREATE.
7. Return to your integration in the Configuration > Integrations menu.

For the field mapping, it is recommended to follow these steps:

1. Map the Status field to the AWS Status field you created. You can map the fields by:
   • Dragging the source field to the target field on the Oomnitza side
   • Selecting the dropdown arrow on the source field and choosing an appropriate target field from the list.
2. Create a custom mapping for the Cluster Identifier. Complete the following steps:
   1. Click the down arrow on the Cluster Identifier field.
   2. Select Add new Oomnitza assets field.
   3. Change the name of the field to RedShift Cluster ID.
   4. Select the Unique checkbox.
   5. Click CREATE.
3. Assign a sync key to a unique field, such as RedShift Cluster ID.
4. Click UPDATE. 

Tracking information for asset loads 

When the integration is run, you can track the name of the credentials that were used and the source of the data. To do this, you map the following fields to Oomnitza:   

• Connect: Credentials
• Connect: Region
• Connect: IAM Roles

Launching the integration

Your integration is in Draft mode until the required mandatory fields are added. When added, click Launch to activate your integration. 

If you selected Cloud as the installation type when creating the integration, see Running an extended integration

If you selected Local as the installation type when creating the integration, see Running an extended integration locally.

Viewing data ingested by Oomnitza

Viewing ingested asset data

For asset integrations, click Hardware. If the asset integration also ingests software data, click Software.

Viewing ingested user data

For user integrations, click People. If you chose the option to ingest User and SaaS user data, click Software > SaaS, click the SaaS app, and then click the Users tab. 

Related Links

• Running an extended integration
• Troubleshooting integrations
• Mapping extended integrations