Creating an extended integration for AWS EC2 assets (DRA)

Sync AWS EC2 with Oomnitza to gain visibility of active and stopped EC2 instances. Information about the instances, such as the state of the instance, network and connectivity, security, resource allocation, and performance details are synced with Oomnitza.

You can use Oomnitza presets to complete actions such as retrieving the average CPU load and instance status, and starting, stopping, and rebooting instances. 

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. 

Creating custom mappings

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

1. Map the AWS EC2 fields to Oomnitza fields and create a custom mapping for the AWS region. To create a custom mapping, do the following:
   1. Click the down arrow on the Region field.
   2. Select Add new Oomnitza assets field.
   3. Change the name of the field to AWS Region.
   4. Click CREATE.
2. Map the Instance ID to the Oomnitza Serial Number field, or a similar field. 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.
3. Click Smart Mapping to automatically detect the appropriate mapping fields
4. Assign a sync key to the Serial Number field.
5. Optional: Create a custom mapping to capture EC2 tags. Complete the following steps:
   1. Click + next to Edit Integration in the upper left of the screen.
   2. Name the field EC2 tag or similar.
   3. For the Field Path, enter {% if instancesSet.get('item').get('tagSet') %}{% set temp = instancesSet['item']['tagSet']['item']%}{%if (temp is defined) and temp%} {{temp | selectattr('key', 'eq', 'foo') | map(attribute='value') | join('')}}{% endif %}{% endif %} - replacing foo with the actual name of your EC2 tag key.
   4. Click Save.
   5. Click the down arrow next to the EC2 tag field that you created.
   6. Select Add new Oomnitza assets field.
   7. Change the name of the field to EC2 tag or similar.
   8. Click CREATE.
6. Click UPDATE. 

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