Enhancements, Fixes and Known Issues 11/07/2024

The following enhancements and fixes are found in this release, dated 11/07/2024.

Expanded Coverage

Custom CloudFormation tags are now inherited by Cloud Connector resources

In order to comply to a rule, when specific custom tags are required on all resources in an AWS account, an option to add a list of tags to Elastio CloudFormation stack has been introduced. If you add your tags when deploying Elastio to the CloudFormation stack, they will be inherited by all resources created in regional Cloud Connector stacks as well.

Updated AWS AMI images

AWS AMI images Elastio uses to operate were updated to incorporate fixes from the latest upstream release.

LVM support introduced

Starting from this version, Elastio can scan LVM on AWS volumes and snapshots, as well as Azure LVMs, if they are located on a single storage device. Each logical volume is scanned in a separate child job and gets dedicated scan results in a separate attachment.

Improved User Experience

Elastio threat scans can now be customized by increasing the maximum number of errors allowed before the scan job is marked as failed

In cases where an asset contains a big number of inaccessible objects, and this is expected from the end user, an environment variable ‘ELASTIO_MAX_SCAN_ERRORS_ALLOWED’ can be set to control the number of errors that will get ignored.

Custom prefix and suffix fields introduced to Elastio Cloudformation

Elastio CloudFormation stack can now include custom prefix and/or suffix that will be applied to the names of the roles and managed policies that Elastio creates.

Bug Fixes

• Previously when an unreadable object was identified by an S3 bucket scan, the scan job would fail. This behavior has been fixed to skip inaccessible objects, those will be reported separately as such in the scan report.

---