Sazabi

Bring your own cloud (BYOC)

Run the Sazabi log pipeline in your own AWS account and keep your logs in storage your organization owns, while Sazabi operates the service.

With bring your own cloud (BYOC), the part of Sazabi that receives, processes, and stores your logs runs inside your own cloud account, and your logs are kept in a database account that your organization owns. Sazabi still deploys, upgrades, monitors, and supports the service, so your team does not operate any of it day to day.

BYOC is for organizations whose security, compliance, or contractual requirements say production logs must be processed in their own network and stored in infrastructure they control.

What runs in your account

  • Log intake. Your systems send logs to an intake address inside your own network.
  • Log processing. Parsing, enrichment, and indexing run in your account.
  • Log storage. Your logs are stored in a database account your organization owns.

What stays with Sazabi

The dashboard, the Sazabi agent, notifications, integrations, and billing run in Sazabi's cloud, as they do for every customer. You use Sazabi the same way with or without BYOC.

What you control

  • You review and approve the access Sazabi gets to your account before anything is set up.
  • Sazabi staff have no standing access to your account. Changes are made through an automated, approved process.
  • You can revoke Sazabi's access at any time. While access is revoked, Sazabi can't operate or update the service in your account.

What still reaches Sazabi

BYOC keeps your log storage under your control, but some data still reaches Sazabi so the product can work:

  • Results of the searches and queries that you, the dashboard, and the Sazabi agent run against your logs.
  • Issues and investigations, including sample log lines that show what happened.
  • Prompts containing log excerpts, sent to Sazabi's model providers when the agent investigates. These providers are contractually barred from training on your data, as described in Data handling.
  • Health metrics and the operational logs of the Sazabi service running in your account, which can include log content. Sazabi uses them to keep that service running.
  • Logs from sources that Sazabi connects to on your behalf, such as AWS CloudWatch, which pass through Sazabi on their way to your account.

Availability

BYOC is available on AWS under an enterprise agreement. To find out whether BYOC fits your requirements, contact sales@sazabi.ai.

Further reading