If there are folders created within the s3 bucket, the ingestion and download file functionality is not working - Known Error

If there are folders created within the s3 bucket, the ingestion and download file functionality is not working Description Issue 1- Folders are created within the S3 bucket to store customers' Zscaler events. The out-of-the-box application did not initially support this multi-level folder structure, but it has been addressed in the latest update set. This fix will be included in the next plugin release.

Issue 2- Folders can be present with the same S3 bucket for both transaction and evidence file. The integration tile did not give the functionality to add folder name separately for both transaction and evidence buckets. This caused evidence json files also to be picked up and ignored by the integration, causing unnecessary noise.

Steps to Reproduce

Create a folder within the s3 bucket and configure zscaler to put events within this folder structure. The ingestion and download evidence file feature is not working.

Integration tile did not support path until the transaction or evidence folders in S3 buckets.

Workaround Fix 1 - As a fix for this, we are providing an update set so that both the ingestion and download evidence file feature is fixed. We have taken into account the multi-level folder structure and updating our code to handle this scenario.

Note- This update set will be marked as 'replace_on_upgrade' true, so that the update of the plugin to the next version is seamless and incorporates all these changes out-of-the box.

Fix2 - A new update set is shared to fix this issue. The integration tile will need to be added and will now accept paths till the respective transaction and evidence folders within the S3 bucket. The update set 2 is marked upgrade safe and will incorporate all the changes out-of-the box in the next version.

Note:- Add new integration tile source details after applying this update set and not use/update existing tile configurations. Special characters in bucket name will not be supported due to issues with encoding of characters ( https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html?icmpid=docs_amazons3_console) .