Summary
During the month of April 2019, as new AWS regions were added, Trend Micro Deep Security AWS account synchronization failures were observed by customers. This issue was a result of an API change in AWS to facilitate the introduction of new AWS regions.
AWS and Trend Micro worked quickly to resolve the issue, and a resolution within AWS was implemented as of 1AM US EDT (UTC -4) on April 27, 2019.
Details
The following Trend Micro customers would have been impacted if they had met all of the following criteria:
- Deep Security deployed as software (on premise) or through AWS Marketplace or Azure Marketplace
- Deep Security Release 10.0 or later
- One (1) or more AWS accounts (also known as cloud connectors) are configured
Trend Micro Deep Security as a Service (DSaaS) customers were not impacted by this issue. We are aware that some DSaaS customers were seeing a synchronization error; however, this error was scoped/limited only to the region that failed - not to the synchronization of other regions.
There is a possibility that some affected customers that are using AWS marketplace AMI offers (not SaaS) based on per host-hour consumption-based pricing may observe inaccuracies in the billing for this period. Trend Micro is in the process of performing the analysis to determine if this is indeed the case and welcomes customers using AWS marketplace AMI offers (not SaaS) to inquire further about the event for more information if necessary.
