Creating an extended integration for GCS buckets

Integrate Google Cloud with Oomnitza to gain detailed visibility of Google Cloud Storage buckets across multiple  projects. This integration syncs vital information about each bucket, including timestamp, location and identification information.

This integration offers the flexibility to specify multiple Project IDs, enabling thorough aggregation of buckets across various projects. 

Navigation

Create the asset integration

Custom mappings

Before you start

You will need to have the following information to hand when creating the integration in Oomnitza:

1. Your Google Cloud Project IDs

Enter a list of Google Cloud Project IDs.

The Project ID is case sensitive, so please make sure you have the correct spelling with upper and lower case characters, or else the integration will fail with a not authorized message.

2. Your Google credentials

You will be prompted to enter your Google Cloud Client ID, Secret, and scopes before you run the integration. For information on credentials see, Google (OAuth 2.0) credentials to Oomnitza.

Please use the following scopes when working with this integration:

• https://www.googleapis.com/auth/cloud-platform
• https://www.googleapis.com/auth/cloud-platform.read-only 
• https://www.googleapis.com/auth/devstorage.full_control 
• https://www.googleapis.com/auth/devstorage.read_only
• https://www.googleapis.com/auth/devstorage.read_write 

The authenticated user must also have the storage.buckets.list IAM permission to use this method. For further information, refer to Google Cloud Documentation: Buckets list

Creating the asset integration

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 type

Select Cloud if you want to store credentials in the Oomnitza cloud.

Select Local if you want to store credentials locally. Local extended integrations do not support AWS and OAuth authentication. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select Cloud.

Integration preferences

By default, the option Create & Update option is selected. Select this option  when you want to edit records and add new records. If you want to edit records and not add new records, select Update Only. If you only want to add new records, select Create Only.

Integration details

To review or update the integrations details, click Edit .

1. Update the integration name if necessary. 
2. Select an installation type.
3. For integration preferences, select an option.
4. Enter the name of the integration user.

Credential details

If you selected Cloud as the installation type, choose one of the following options:

• Select the credentials that were created for the integration.
• Edit the credentials that were created for the integration.
• Create new credentials

Schedule

By default, data is streamed to Oomnitza once every day.

You can configure the schedule to meet your needs such as changing the interval or changing the time so that the data is streamed when your system isn't busy.

1. Click the Edit .
2. Configure your schedule.
3. Click Update.

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 the GCP bucket fields to Oomnitza fields and create custom mappings to get the information that you need.

Complete these actions:

1. Click Smart Mapping to automatically detect appropriate mapping fields. Values from the integration can also be dragged to the appropriate field on the Oomnitza side, or selected from the integration field dropdown.
2. Create a custom mapping for the ID field. To create a custom mapping, complete the following steps:
   1. Select the down arrow on the ID field.
   2. Select Add new Oomnitza field.
   3. Change the name of the field to Bucket ID.
   4. Select the Unique checkbox.
   5. Click CREATE. 
3. Assign a sync key to the Bucket ID field.
4. Click UPDATE. 

Custom mappings

Connector Sync Time
Created at
ID
Kind
Last updated at
Name
Project Id
etag
location
metageneration
selfLink
storageClass

 Learn more about mapping

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