Security Log Forwarding now available

We are excited to announce the general availability of Security Log Forwarding for Aura Enterprise customers.

This feature allows customers to set up and configure Security log forwarding process(es) in the Aura console, where the destination is a cloud logging service. The supported targets are Google Cloud Logging in GCP, Cloudwatch in AWS and Log Analytics in Microsoft Azure. If multiple regions are in use, a separate log forwarding process can be defined per cloud provider and region.

Once the target is set up, all security logs from AuraDB Enterprise and AuraDS Enterprise instances in the same cloud provider and region will be forwarded to the defined logging service.

To access Log forwarding:

Navigate to the Neo4j Aura Console in your browser.
Select Log forwarding from the sidebar menu.

This will display a list of currently configured log forwarding processes for the active tenant. If no log forwarding process is set up, a button to do so is displayed in the center of the page.

Documentation for setting up the service is available here.

Aura Database and Analytics services are business critical for our users. We have requests to introduce more capabilities enabling access to logs and metrics to derive actionable insights using your choice of monitoring platform.
We have a strong roadmap of observability sharing features including security logs, query logs and other capabilities. Many of these logs can be of significant size hence we will introduce in the future a new consumption based billing model including cloud egress costs.
We believe security is of paramount importance hence we have decided to make security logs available for you initially at no extra charge
.