On This Page

Home /Cribl Lake 4.20.3

Cribl Lake 4.20.3 ​

PRODUCTDATERELEASEADDITIONAL RESOURCES
Lake2026-10-21MaintenanceKnown Issues, Cribl Search Release Notes

Summary ​

Important Changes

This release includes the following important changes:

New Features ​

This release provides the following improvements:

Outpost Support for Azure Storage Locations ​

You can now bind an Azure Storage Location to an Outpost Group. Cribl Lake then runs Azure management operations for that Storage Location through a connected Outpost instead of directly from the Leader. Those operations include checking access to the storage account and validating its lifecycle and inventory configuration.

Select the Outpost Group when you create an Azure Storage Location, or on the existing Storage Location’s page. A bound Storage Location doesn’t fall back to the Leader, so keep at least one Outpost connected.

Azure Storage Locations that you don’t bind to an Outpost Group work as before. For setup details, see Configure an Azure Storage Location.

Custom Actor Session Tags for Amazon S3 Storage Locations ​

When you create an Amazon S3 Storage Location, you can now customize the value of the Actor session tag that Cribl passes when assuming the IAM role for bucket-level administration, such as lifecycle policy and inventory configuration. Existing Storage Locations continue to use the default value, admin. For configuration details and IAM policy requirements, see Configure an Amazon S3 Storage Location.

Private Endpoints for Azure Storage Locations ​

Azure Storage Locations now have an Enable private endpoint option, so Cribl Search can read their Datasets over a private connection to your storage account instead of the public internet. This lets you search Cribl Lake data when your security policy blocks public access, without maintaining an IP allowlist. After you save, approve the pending connection in Azure before you search. See Approve the Private Endpoint in Azure. Storage Locations without the option turned on work as before.

Fast Release Channel in Cribl.Cloud ​

In Cribl.Cloud, Enterprise customers can now assign each Workspace to the Fast release channel. Cribl publishes new features and services to the Fast release channel approximately weekly, so you can preview them and provide feedback before they become available on the Regular release channel.

Billing Reader Permission for API Credentials ​

Enterprise customers can now assign the Billing Reader Permission on an Organization to API Credentials in Cribl.Cloud. This lets you automate billing and usage reporting without granting broad administrative access to your Organization, Workspaces, or products.

Copilot Is Now Billy ​

The AI assistant formerly known as Cribl Copilot is now Billy. All user-facing text, including titles, tooltips, placeholders, and accessibility labels, now refer to Billy. Billy has the same capabilities as Copilot. Only the name has changed.

Apps ​

The Cribl Marketplace now shows which Apps are Cribl Certified, and installed Apps get tighter control over who can open them and what they can call.

  • Certified Apps. Find Apps that meet Cribl standards for business-critical use with a new Certified filter in the Cribl Marketplace. Publishers request certification once per App, and it carries to each newer version that Cribl approves for listing.
  • App permission models. A newly installed App uses strict policy permissions and can call only the Cribl API endpoints declared in its policies.yml, including when an administrator uses the App. An App that is already installed keeps user-based permissions, where access follows each member’s product permissions and policies.yml can add actions, and you can switch that App to strict policy permissions.
  • Private by default. Newly installed Apps are private. Members and teams can open a new App only after an administrator uses Share to assign them the App user access level. Upgrading an App keeps its existing Share assignments.
  • Ownership transfer. An App owner can transfer a published App to a new owner.

Experience Improvements ​

  • Cribl now applies endpoint-specific rate limits to prevent excessive traffic from interfering with normal operations. When a request exceeds the endpoint’s rate limit, the API returns the HTTP status code 429 Too Many Requests and a Retry-After header that specifies how many seconds to wait before retrying.
  • On the Key-Value Stores tab of an App, you can now edit, clone, or delete individual key-value pairs from the Actions menu. Use this to keep an App’s seeded configuration and secrets up to date, and to duplicate an unencrypted pair instead of recreating it.

Important Changes ​

Cribl Lakehouses Removed from the UI ​

Beginning with Cribl Lake 4.20.0, Cribl Lake no longer includes the Lakehouses UI, and you can no longer create or manage Cribl Lakehouses. Instead, ingest data into Cribl Search lakehouse engines. See Get Data In in Cribl Search.

Cribl Terraform Provider No Longer in Preview Status ​

The Cribl Terraform provider is no longer in Preview status and is now generally available. Use the provider to manage Cribl resources as infrastructure as code across Organizations and Workspaces.

Corrections ​

IDDescription
LAKE-2846
Fixed an issue where a Cribl Lake Destination crashed when an incoming event contained a field named asJSON, and then failed on every event after it. The Destination now processes these events normally.
LAKE-2794Fixed an issue where the Splunk Cloud Self Storage (DDSS) Direct Access Source did not collect data.
LAKE-2828Fixed an issue where Dataset size metrics could lag by up to 15 days, so a Dataset could appear to hold data that its retention period had already removed.
LAKE-2768Fixed an issue where a Cribl Lake Destination showed a Discard changes prompt when you closed it without making changes.
LAKE-2850Fixed an issue where deleting several Datasets at once showed a separate deletion-in-progress message for each Dataset. You now see one message.
LAKE-2743Fixed an issue where, on a standard license, the POST /products/lake/lakes/{lakeId}/direct-access endpoint created a Direct Access Source that stayed in provisioning indefinitely. Like the Lake Sources endpoint, it now rejects the request, because Direct Access requires an Enterprise license.

Other Functional Fixes ​

IDDescription
AI-5079
Cribl AI requests using custom LiteLLM providers no longer include an unsupported parameter that caused errors when routing through Amazon Bedrock. This fix resolves an issue where Cribl AI features, such as Copilot chat and the Test Connection check, failed against Bedrock-backed models. Managed OpenAI providers remain unaffected.
AI-2503Resolved an issue where Cribl AI outbound requests ignored corporate proxy settings, causing features like Copilot, AI suggestions, BYOM providers, and external MCP connections to fail in proxy-restricted environments. All AI traffic now correctly routes through configured proxies, and proxy configuration changes take effect without requiring a Leader restart.
AI-5162Resolved an issue in AI Settings where connection tests failed for custom OpenAI and Azure OpenAI providers.
CRIBL-44834Fixed an issue where editing the key of an existing entry on App Settings > Key-Value Stores created a second key and left the original in place. The key is fixed after you create the entry.
CRIBL-45429Fixed an issue where Upgrade failed for an App imported with Import from Git, reporting that credentials were required, even though the import had already stored those credentials.
CRIBL-45681Fixed an issue where Upgrade on a Pack installed from the Packs Dispensary, or an App installed from the Cribl Marketplace, always reported that the installed version was up to date, even when a newer version was published. Upgrade now uses the current version from the catalog.

SDK Changelogs ​

The Cribl SDKs help you integrate with Cribl and reduce the need for repetitive tasks. We maintain changelogs for each version of the Cribl SDKs in their GitHub repositories: