Skip to main content

​
Intro

Cloud Amplifier provides a native integration with cross-cloud systems to unlock data products at the speed your business needs them.
cloud amplifier image.png

​
Why Cloud Amplifier?

  • IT limitations — IT alone cannot realize the full potential of data. A broad, inclusive approach with all LOBs is required, and all valuable data is not yet controlled by IT.
  • Increased stress and time constraints — Business users demand timely access to data products, increasing the pressure to deliver.
  • Rigidity and friction in data processes — Rigid processes and tooling prevent the quick building of flexible databases, requiring too much time and effort.
Cloud Amplifier can provide solutions for these issues and more.
ca image 2.png
This article provides information about configuring Cloud Amplifier for your Domo environment in the following topics:

​
Required Grants

After Cloud Amplifier is enabled for your Domo environment, you can assign the following Cloud Amplifier grants to manage access to these features:
  • Manage Cloud Accounts — Allows a user to add/remove cloud accounts and add/remove tables from a cloud account. This grant also allows a user to change the default storage cloud.
    Note: This grant must be assigned to a user with the Manage DataSet grant to work properly.
  • Override Default Cloud — Allows a user to use any storage cloud account that is shared with them instead of the default cloud. If you do not have this grant, you can’t use any other cloud besides the default cloud.
    Note: This grant must be assigned to a user with the Edit DataSet or Manage DataSet grant to work properly.

​
Access Cloud Amplifier

If you’re on a consumption agreement, you can access Cloud Amplifier from the Data Center. See Setup below. If you’re not on a consumption agreement, you can enable Cloud Amplifier for your instance by contacting your Domo account team.
cloud amplifier.jpg

​
Setup

After Cloud Amplifier is enabled for your account, you can connect your existing data warehouses from the providers listed below. Each provider has their own setup requirements; follow the links below to see our setup documentation for each provider. Available providers include:

​
Defaults

Cloud Amplifier allows you to specify a default storage account for all DataSets. Changing these settings does not change existing DataSets or DataFlows. These defaults are only used for new assets.

​
Best Practices

We recommend that you choose a default storage cloud. To do this, follow the steps below after Cloud Amplifier is enabled for your account. Before completing this task, make sure that you have the Override Default Cloud grant.
  1. In the Domo navigation header, select More > Admin. The Admin Settings display.
  2. Under Features, select Cloud Amplifier. The Cloud Amplifier page displays.
  3. Select an option from the Select the default storage cloud dropdown.
    Note: We recommend setting up your Cloud Amplifier connections using a service account.
If you need to move a DataSet from one warehouse to another, you can use Magic ETL to copy a specific DataSet hosted in your database and materialize it in Domo, where it runs on a schedule.

​
Use Advanced Scheduling for Data Freshness

With Cloud Amplifier, you can use Advanced Scheduling to control when to check for data updates in your sources. This allows you to check for updates only when necessary and helps reduce data processing costs. You can either use basic data freshness checks or advanced checks for any new or existing Cloud Amplifier integration. Follow these steps to configure them for an existing cloud connection:
  1. Navigate to Data > Data Warehouse (cube icon) and select Manage Cloud Connections.
    Advanced scheduling - Warehouse page.png
  2. Choose any native integration engine by selecting a tile or selecting See more for additional integration options.
    Advanced scheduling - Engines.png
  3. (Conditional) Choose an existing integration by hovering over your integration and selecting (wrench icon) > Edit account. Otherwise, select + Add New Integration. The integration wizard displays.
    Advanced scheduling - Edit account.png
  4. In the integration wizard, enter the necessary account information and navigate to the Data Freshness Checks step.
  5. Configure your data freshness checks using the settings in either the Basic or Advanced tab. Learn more about the basic and advanced settings below.
    Advanced scheduling - Settings.png
  6. Select Next to finish configuring your integration.

​
Basic Settings

Update Frequency

Description

Every 15 minutes

Checks every 15 minutes, all day or during the active hours range.

Every 30 minutes

Checks every 30 minutes, all day or during the active hours range.

Every hour

Checks every hour, all day or during the active hours range.

Every day

Checks once per day at the specified time, including weekends (Saturday and Sunday).

Every weekday

Checks once per day at the specified time, but not on weekends (Saturday and Sunday).

Every week

Checks once per week on the selected day and at the specified time.

Every month

Checks once per month on the selected date at the specified time

​
Advanced Settings

The advanced data freshness configuration includes the following:

Update Frequency

Days per week

Months

Once a day — Checks once per day. You can set the time and time zone.

Every day — Checks daily.

Every month — Checks every month.

More than once a day — Choose how frequently the checks happen using an hour range.

Specific days of the week — Choose on which days of the week the checks happen.

Specific months — Choose during which months the checks happen.

—

Specific days of the month — Choose on which days of the month the checks happen.

—

​
Federated Data vs. Cloud Amplifier

The table below compares federated data to Cloud Amplifier read and read/write configurations:

Capability

Federated-Direct Query

Cloud Amplifier Integration (Read-Adapter) Cloud Amplifier Integration (Read/Write Adapter)

Visualize data from existing tables
- Create cards
- Create dashboards

✅

✅✅

Visualize on-premise data behind firewall via an agent

✅

❌

❌

Get updated metadata from source tables
- Last updated time
- Updated row count

❌

✅
( Every 15 minutes
Configurable )

✅
( Every 15 minutes
Configurable )

Card Alerts

Screenshot 2023-02-03 at 1.41.27 AM.png

✅
( Every 15 minutes
Configurable ) 		✅
( Every 15 minutes
Configurable )
DataSet Alerts ❌✅
( Every 15 minutes
Configurable ) 		✅
( Every 15 minutes
Configurable )
DataSet Views ✅✅✅
Use data from existing tables in Magic ETL as inputs ❌✅✅
Use data updates from existing tables to trigger other DataFlows ❌✅✅
Custom fiscal calendar for source table data (one per instance) ❌❌✅
Use Domo Connectors, Workbench, SDK, CLI to write to customer-owned EDW/Data Lake Screenshot 2023-02-03 at 1.29.01 AM.pngScreenshot 2023-02-03 at 1.29.01 AM.png

✅

Native direct rewrite

Write Magic ETL output to customer-owned EDW/Data Lake Screenshot 2023-02-03 at 1.29.01 AM.pngScreenshot 2023-02-03 at 1.29.01 AM.png

✅

Native direct rewrite

PDP | Governance ✅✅✅
Domo App Support ✅✅✅
Jupyter Workspace Support ✅✅✅
Domo auto-caching of card loads

Screenshot 2023-03-27 at 10.24.52 AM.png

Set static TTL on each DataSet

✅✅

​
Share a Cloud Amplifier Integration Account (Beta)

If you own a Cloud Amplifier integration, you can share access to the integration and associated account so that others can help with governance of the account and underlying data. There are different levels of access available, depending on your use case. The following table can help you determine the right level of access to grant:

Read

Execute

Share

Write

Delete

Admin

Ability to register new DataSets in Domo

Ability to create new tables on the remote.

Ability to share the integration.

Ability to make changes to the integration and its account

Ability to delete an integration

Full access

Owner

Allows read-write use, sharing, editing, and deleting of the integration.

.png” alt="" />

.png” alt="" />

.png” alt="" />

.png” alt="" />

.png” alt="" />

.png” alt="" />

Can Edit

Allows read-write use, sharing, and editing of the integration, but cannot delete.

.png” alt="" />

.png” alt="" />

.png” alt="" />

.png” alt="" />

Can Share

Allows read-write use and sharing of the integration but cannot edit or delete.

.png” alt="" />

.png” alt="" />

.png” alt="" />

Can Write

Allows read-write use of the integration but cannot share, edit, or delete.

.png” alt="" />

.png” alt="" />

Can Read

Allows read-only use of the integration but cannot write, share, edit, or delete.

.png” alt="" />

No Access

No access to the integration

Follow these steps to share a Cloud Amplifier integration account:
  1. Navigate to the Domo Data Warehouse (Data > Data Warehouse).
  2. Scroll through the Cloud Amplifier Integrations panel and find the integration you want to share. Select it.
  3. Scroll to the Accounts section and choose Share for the account you want to share. The Manage Account access modal displays.
  4. In the modal, locate the individual with whom you want to share the integration and use the dropdown to choose the access level. The table above can help you decide the appropriate level.
  5. Select Apply to save your changes.
  6. Confirm the permissions changes.

​
Technical FAQ

Find answers to frequently asked questions about general topics, caching rules, and external cloud storage.

​
General

Cloud Amplifier DataSets operate the same as Domo DataSets. Additionally, Magic ETL can trigger the DataFlow to run when the data is updated in your database.By default, Domo checks the database metadata for updates every 15 minutes.
Magic ETL v2 supports Cloud Amplifier DataSets.
Yes, you can. You can designate DataSets created via Cloud Amplifier as published DataSets to create a virtualized DataSet in a subscriber organization. You can then use the virtualized subscriber DataSeta as an input to Magic ETL transformations and configure it for DataSet Alerts.You can also use DataSets created via Cloud Amplifier with Domo Everywhere Embed.
No.
Not at the moment, but we plan to add this feature soon. In the meantime, we recommend setting your locale to en-US when using Cloud Amplifier.
We have identified an issue affecting old dates—they are incorrectly shifting due to daylight savings time adjustments. We guarantee correct time zone conversions for dates after the epoch start date (January 1st, 1970). Before that, time zone adjustments may be off due to when daylight savings was adopted in the particular time zone.

​
Caching Rules

There are a few scenarios in which Domo always sends a query and never loads from the cache:
  • When you are viewing the DataSet preview on the DataSet’s Details page
  • Whenever a DataSet View loads
  • Whenever a DataSet loads into Magic ETL
In each scenario, we assume you always want to view the most current data, so a query is always initiated. Card query results, however, are saved and loaded from the cache.
When you are viewing a card, Domo first looks for cached query results. If there are no cached query results, Domo initiates a query to the cloud warehouse to get the most current data.
When building or editing a card, new data is needed after every chart modification to visualize the changes. If the Auto Preview option is enabled in Analyzer, there is a new query each time a change is made to the card. It is possible to disable the Auto Preview option; you can then decide when to preview the chart. Each preview effectively sends another query.
Yes.
Card query results are stored for up to 24 hours.
There is no explicit limit on the number of queries cached.
Yes. However, the cache and Time to Live (TTL) is configured for the integration and not for individual DataSets.
Cached data is stored in the same geographical data center as your deployed Domo environment—in an AWS EC2 server using Redis.
All card queries are cached the same in Domo, no matter which cloud data warehouse they come from. However, some warehouses have their own rules for caching query results in addition to those from Domo. These rules vary by warehouse. For example, Snowflake caches query results for every query. You can go to the warehouse’s documentation to read more about how they handle caching results.Given warehouse differences in handling cached results, there may be scenarios in Domo where an action always triggers a query to the warehouse, such as viewing the DataSet preview, but the warehouse does not actually run the query because the results are stored in its cache. In the case of Snowflake, results are returned from the cache.
Yes. However, because the underlying table is a non-materialized view, Domo cannot detect changes and will execute the view query each time data is requested. Domo still detects changes on materialized views.
Yes, it will. However, we are working to optimize this behavior to perform only the necessary joins wherever possible.
Currently, there is no row or data size limit on what is saved in the card cache; however, the card query results are only stored for 24 hours.

​
External Cloud Storage

Not at this time.
Not at this time.
Data can be cached for up to 24 hours, but the cache is cleared when data updates. For customer-managed DataSets, there may be up to a 15-minute delay between when data updates and the cache is cleared.
Yes, Domo operates on your cloud warehouse account.
The method Domo uses to access a cloud warehouse account depends on the warehouse. We recommend using a system or service account, rather than individual user accounts, to grant Domo access to all cloud warehouses. See the individual provider guides listed above to learn how that Domo accesses that particular provider.
This is currently in beta for the Google BigQuery integration.
Yes. By default, you have access to both Domo’s proprietary Adrenaline engine and the Cloud Amplifier engine. You can configure your Domo environment so that only the Cloud Amplifier DataSets are allowed to run in your Domo environment, but Domo Support needs to help with this.
For existing DataSets created via a connector or Domo APIs, you can reach out to Domo Support for assistance to move them to your cloud provider. If those DataSets were created via some other method, you need to recreate those in your cloud provider manually.
Domo’s APIs can be used with any DataSet in a Domo-managed database, as long as that table is in the Domo-managed database that was configured during the write integration step of your Cloud Amplifier setup. Customer-managed databases that exist in the cloud, which Domo can read but not write to, cannot be updated with Domo APIs.This includes but is not limited to, the Stream API, webhooks, custom apps that generate new data such as Form Builder, and managing a DataSet via the DataSet API (such as updating a DataSet, managing personalized data permissions (PDP) policies, changing the owner of a DataSet, exporting a DataSet).For a more comprehensive guide to using the DataSet API, see our developer docs .