Release 2.4.0

August 20, 2024

What’s New?

Connector 2.4 brings updates to AWS connectors and bug fixes.

Common Features

Introduced Validation to Protect Service Account Connectors

We have introduced a new validation feature designed to protect service account
connectors from accidental deletion. This enhancement ensures the integrity of your Snapshot-based scan configurations by preventing the unintentional removal of essential service accounts.

When performing a delete operation on a connector that is registered as a service account, the system now returns a message requesting you to deregister the connector before proceeding with the deletion. This validation is crucial as service accounts are pivotal for successful scan operations.

Delete service account dialog box

To deregister a service account, refer to the "Deregister a Service Account" API in the Connector API Guide.

Amazon Web Services

Added Support for New Regions in AWS Connectors

With Connector 2.4.0, you can select additional regions when configuring an AWS connector. This new support allows organizations to leverage AWS’s expanding infrastructure while ensuring all their assets are monitored and protected effectively, regardless of their geographic location.

Regions Introduced

Global

Asia Pacific (Melbourne) ap-southeast-4
Europe (Spain) eu-south-2
Europe (Zurich) eu-central-2
Israel (Tel Aviv) il-central-1
Middle East (UAE) me-central-1
Asia Pacific (Hyderabad) ap-south-2

To select these regions, you can navigate to the Connector application > Amazon Web Services > Create/Edit a Connector > Go to the Region Selection screen > Select the required region.

New regions in region selector screen

New Tokens

Snapshot-based Scan Tokens

Tokens introduced for AWS and Azure connectors.

Name	Description	Example
isServiceAccount	Find connectors that are registered as a service ac	`isServiceAccount: true`

Issues Addressed

We fixed an issue where Azure connectors returned an 429 error and failed to populate the inventory accurately.
We fixed an issue where the OCI connectors of some customers were stuck in a "Queued" state.
We fixed an issue where the AWS Organization connector with Cloud Perimeter Scan enabled returned errors after the scheduled auto-run.