Bug Fixes:

• Resolved an issue causing AWS RDS Instance ARNs to not be populated during sync.

Improvements:

• Reduced the latency of the hourly sync job by fetching details of unmanaged items in the daily sync job instead.
• Expanded the number of AWS regions that Opal supports.

Bug Fixes:

• Added missing event type labels for proper naming UI in dropdowns.

Fixed resources in certain AWS regions not showing up in Opal.

Fixes an issue where syncing AWS RDS instances would sometimes result in an error showing "invalid RDS instance arn".

Previously, Opal would list all available roles in all resource types when users add new custom roles. However, some roles cant be applied to certain resource types, or some can only be applied to certain resource types, etc. We now will properly show only relevant roles which can actually be applied to the resource being viewed.

A bug had caused Opal to ingest more roles than necessary for GCP resources during a certain period of time. To remedy this, we are deleting custom roles ingested during this time period.

Reworked how Opal handles access to GCP SQL instances. We now better match how the GCP console behaves:

• Roles are no longer inherited into SQL instance resources.
• The SQL instance user list now purely represents the list of users who have been added to the instance, with no role assignment.
• Adding a user to an SQL instance in Opal also adds the Cloud SQL Instance User role to that user in that instance's parent project.
• Removing a user from an SQL instance in Opal does not remove the Cloud SQL Instance User role from that user.

Fixes a bug where when first adding an app/integration, all resources could be imported to Opal even if the import setting is set to manual imports.

Fixed a bug that caused the default request expiration time to not properly match the maximum and recommended durations in the corresponding request configuration.

Available in 1.0.587

Scrolling the Access Review table would sometimes have jumps/glitches when user details were expanded. This is now fixed