Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Nov 11, 2020 - 00:00 EST
Scheduled
TIBCO Mashery performs scheduled maintenance weekly, every Tuesday starting at 9:00 PM PST/ Wednesday 00:00 AM EST.
These weekly releases are a combination of product feature releases, bug fixes and customer specific deployments. Latest updates to the TIBCO Mashery cloud platform are posted on community site at https://community.tibco.com/wiki/tibco-mashery-release-notes
As always, unless otherwise noted, these releases are zero down time with no impact to any area of the TIBCO Mashery service.
If you have any questions or concerns about this release then please contact us via the TIBCO Support Portal (https://support.tibco.com).
----ACTION REQUIRED BY 2/2/21 for Call Log Export (ECLE) Users to avoid delivery disruption -----------
Summary: Having launched native S3 bucket encryption and assumed-role access to customer buckets, TIBCO Cloud Mashery is announcing the End of Life for the original IAM based bucket access policy. Customers not upgrading to the new functionality prior to 2/2/21 will have call log delivery disrupted until the new functionality is configured. We are extending the existing deadline by 3+ months to ensure customers have a sufficient notice period. The new functionality is available now, please do not delay your upgrade to the last minute and risk an interruption of delivery. If you are using the Call Log Export feature, please read the full message below and share within your organization.
Dear Customer, As a current user of our Call Log Export feature, you are enjoying the benefits of having call log data delivered to your S3 bucket for use in your own data warehouse. We recently launched field masking for Call Log Exports and we continue to listen to your requests for increased security. We are happy to announce that we have launched support for native S3 Server-Side Encryption.
This new functionality is available now! To help you take advantage of this new feature, we have created a CloudFormation template, which will automate the creation of the required configurations and produce the artifacts that will need to be configured within Mashery so that we can begin delivering logs to your S3 bucket(s), which will be encrypted on the server side.
Please log in to your API Control Center, select the Call Log Exports option from the Analyze menu, and then the call log export profile you would like to update or create a new profile. You will see that there is a new Bucket Encryption option and a notification describing the change.
Follow the links in the notification to familiarize yourself with the change. When you are ready to make the changes, execute the steps in the setup instructions link. You will need the CloudFormation template provided in the instructions.
When you have completed the changes, it will take roughly 3 hours for the new configuration to become active. After this period has passed, you can check that S3 is encrypting the logs by selecting an object in the bucket, then navigating to the Properties tab and looking for "AWS-KMS" on the Encryption card. Once confirmed, you can remove the original bucket policy.
Note: only files uploaded after the configuration is live will be encrypted, existing files will remain unencrypted.
We selected native S3 Server-Side Encryption using KMS and other security best practices such as assumed-role access to your bucket because it should have minimal or no impact on your integration with S3 CLI, API, or SDK, while delivering enhanced security.
Because security is more important than ever, we are disabling the existing IAM based bucket policy functionality on 02/02/2021, which means any ECLE configuration that has not been upgraded to Encryption/Assumed-role access will no longer receive logs. Please note that we will not be able to change this date.