Page Comparison

Yes, all passwords are encrypted and stored in a vault provided by AWS. DigitalRoute has no access to the users' passwords, including the credentials configured during a function's configuration, for example, Amazon S3 function.

We have a high-availability system running in multiple data centers at the same time. Security is a high priority to DigitalRoute so we also perform full backups every hour.

Yes. Currently,   Usage Engine is SOC 2 Type 1 certified. To learn more about the SOC 2 Type 1 certification see Security & Compliance.

Yes.   is Usage Engine is ISO27001 certified. To learn more about the ISO certification see Security & Compliance.

After a trial account is expired, all streams and schedules pertaining to your account will be stopped. You can still log into your account but you will not have access to Solutions or Streams view. 

You can access your on-premise data center by using the following white-listed fixed IP addresses in your firewall:

• 63.33.245.80,
• 63.35.38.190,
• 63.35.102.205

Public IPs for US region

• 44.198.146.136
• 52.44.235.9
• 54.146.237.141

If you have trouble connecting to these IP addresses or should you need other connection options, like VPN, please contact our support.

Logs and audits are automatically deleted after 90 days.

The time shown in the logs and metrics follows the local timezone.

You can receive one mail with all files included if you connect all required collectors to the same Email Attachment function. You also need to set the filename option to "Collector filename".

To merge multiple files into one, do the following:

1. Configure forwarder with "custom filename".
2. Cache all records in memory.
3. When meta.lastCall = TRUE, push all record to bucket.

You can refer to the Tutorials for reference or you can also view and import some Example Streams to your account to see how a stream works.

Beta release is like a pre-released version of one or more functions given out to a group of users to test under real conditions. A function in beta release is always alpha tested in-house and is close to the look, feel and functionality of the final version, however, design and features may change. Currently, we don't provide documentation for functions in beta release. 

During the development of  functions of Usage Engine functions are sometimes replaced by more flexible and extended versions. As the development teams strive to make transitions between versions as seamless as possible, the common approach is to migrate any existing configurations without the need of manual intervention. We use the term deprecate to indicate that the new version of a function most likely will not be completely backward compatible with the previous function.

The process of deprecation flows as follows:

1. A new version of a function is developed and ready for launch.
2. The old version is flagged with the word "Deprecated".
3. During a transition period, both versions co-exist, which allows sufficient time for migration. 
4. The old version is removed from Usage Engine.

Common HTTP requests such as POST and GET are limited to 10 MB each. Each individual request instance has its own individual limit.