Release Date: 8 November 2022 (Updated: 7 November 2022)
TetraScience has released its next version of the Tetra Data Platform (TDP) version 3.3.5. As its major focus, this release addresses changes Amazon recently made to the IAM role trust policy.
Details appear in the following sections:
- Bug fixes
- Deprecated features
- Known issues
Links to Tetra Agents and Artifacts Release Notes are provided in the Other Release Notes section at the end of this topic.
There are no enhancements for this version of the software.
The bug fixes for this release appear below.
IS-107 - AWS recently made changes to their IAM role trust policy that breaks the functionality being used by Tetra Datahubs to get credentials that enable the Agent to upload data via S3. This ticket makes fixes so that the software now works with the new IAM role trust policy.
- This change impacts all organizations created after September 21, 2022. Without this 3.3.5 patch, these organizations will not be able to use S3 Upload (or the Receive Commands feature) on any Agent connected to any Data Hub that tries to use S3 Upload.
- Organizations created before September 21, 2022 use the old IAM role trust policy method. Amazon has allowed any device using the old method a grace period until February 2023 to continue with that method but only for those devices which have done so since June 30th 2022. If any Agent on any Datahub in a given Organization has been online in S3 mode (or with the Receive Commands feature), with a valid connection, since June 30th it will continue to work as will all Agents attached to all Datahubs in that Organization. But, if no Agent has connected in that time then all Agents on all Datahubs in that Organization will no longer be able to work in S3 mode.
- At the end of Amazon’s grace period (February 15, 2023), all organizations will be affected.
DL-911: Addresses a backward incompatible issue that was introduced in v3.3.0. Common and non-common IDS data will now be populated in the original Athena tables, as prior to v3.3.0, and non-common (client/private) data will reside in new Athena tables with a prefix. Non-common Athena data duplication will be discontinued in future releases. Additional information will be highlighted in the release notes for the next major platform version.
- This change impacts customers that process data via client-specific protocols and only impacts data in Athena via SQL access.
There are no minor functionality changes for this release.
Please see our Deprecation Notices to learn more about deprecated features.
- Please see the previous release notes for other known issues.
Updated 3 months ago