Skip to main content
Last updated on

Akamai WAF connector limitations

Beta

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Akamai WAF from the Previews page. See Manage Databricks previews.

The managed Akamai WAF connector ingests only the akamai_waf_events table, and Akamai retains SIEM events for 12 hours, which limits how far back the connector can ingest.

General software as a service (SaaS) connector limitations​

The limitations in this section apply to all SaaS connectors in Lakeflow Connect.

  • When you run a scheduled pipeline, alerts don't trigger immediately. Instead, they trigger when the next update runs.
  • When a source table is deleted, the destination table is not automatically deleted. You must delete the destination table manually. This behavior is not consistent with Spark Declarative Pipelines on Lakeflow behavior.
  • During source maintenance periods, Databricks might not be able to access your data.
  • If a source table name conflicts with an existing destination table name, the pipeline update fails.
  • Multi-destination pipeline support is API-only.
  • You can optionally rename a table that you ingest. If you rename a table in your pipeline, it becomes an API-only pipeline, and you can no longer edit the pipeline in the UI.
  • If you select a column after a pipeline has already started, the connector does not automatically backfill data for the new column. To ingest historical data, manually run a full refresh on the table.
  • Databricks can't ingest two or more tables with the same name in the same pipeline, even if they come from different source schemas.
  • The source system assumes that the cursor columns are monotonically increasing.
  • The connector ingests raw data without transformations. Use downstream Spark Declarative Pipelines on Lakeflow pipelines for transformations.

Connector-specific limitations​

The limitations in this section apply to the Akamai WAF connector.

  • The connector ingests a single table, akamai_waf_events. It doesn't ingest other Akamai APIs or resources.
  • Akamai retains SIEM events for 12 hours. The connector can't ingest events older than this retention window. Schedule the pipeline to run at least every 12 hours. See Fetch security events.
  • SCD Type 2 isn't supported. WAF logs are append-only.
  • You must provide 1 to 1,000 Web Security Configuration IDs in config_ids.
  • EdgeGrid credentials expire after 2 years by default. After they expire, create new credentials and update the Unity Catalog connection.
  • The connection Host must be a hostname without https:// and must end with .cloudsecurity.akamaiapis.net or .luna.akamaiapis.net.
On this page