We are pleased to announce support for authenticating S3 connections using AWS IAM role assumption, improvements to metadata fields for datasets published from the System of Record, Curator Hub and queue improvements, a new Tenant Operator role, and more!

Authenticate to S3 Connections with IAM Role Assumption

Tamr Cloud now supports authenticating to S3 using AWS IAM role assumption. With this method, Tamr obtains short-lived credentials via sts:AssumeRole on each use; no long-lived access keys are stored.

See Configuring S3 Assume Role Authentication for configuration instructions.

Improved Create and Update Time Fields when Publishing from the System of Record

For consistency with the create and update fields returned in our API responses, which provide the timestamp of the date and a record was created or updated, you can now include createTime and updateTime fields when publishing these datasets from the System of Records:

• RealTime Records
• RealTime Relationships
• RealTime Tamr ID Mapping.

For the Source Records dataset, you can include the updateTime.

These new fields replace the createdMs and updatedMs fields for new publish destinations.

Existing publish destinations are not impacted. For backwards compatibility, the existing createdMs and updatedMs fields continue to be available (but marked as deprecated).

See Publishing from the Tamr RealTime Datastore for more information about these datasets.

Upgraded Curator Hub and Queues

Earlier this week, we announced our improved Curator Hub landing page, along with:

• Improved match explainability
• New queue filters for sub-status, confidence scores, and search labels
• Configurable curation queues
• New Queues API
• Webhook notifications for curation events

See What's New: Upgraded Curator Hub and Queues for more information.

Tenant Operator Role

In case you missed it, a new Tenant Operator user role is now available - enabling you to give users permission to manage specific system settings without allowing them access to users, project data, or project resources. See the What's New: Tenant Operator Role announcement for more details.

Bug Fixes and Other Improvements

• For data products with a System of Record, data product curators can now use Curator Hub to review items in queues associated with the data product. See Data Product Permissions
• If you are using the Records API, you can now work with Tamr to configure merge rules for attribute groups (or sub-records), such as addresses, emails, and phones. See tamr.api.v1alpha1.Records.
• Resolved an issue in which source records were not marked as verified automatically when golden records were merged.
• General usability, styling, and performance improvements.