Optional configurations

A Managed BYOC deployment works without any of the configurations on this page. Each one is opt-in: turn it on when your organization needs it, either during your initial deployment or later.

Configuration	What it does	How it’s applied
Observability destinations	Sends logs, metrics, and traces to Datadog or to OpenTelemetry and Prometheus endpoints, configured per signal	You store settings in AWS Secrets Manager; Superblocks applies them at the next deployment
Custom resource tags	Applies your organization’s tags to the platform resources Superblocks deploys	You send key/value pairs to your deployment team; Superblocks applies them at the next deployment
Custom WAF rule groups	Attaches your own AWS WAF rule groups to the WAFs that Managed BYOC deploys to protect inbound traffic	You send rule group ARNs to your deployment team; Superblocks attaches them at the next deployment
AWS Network Firewall	Inspects and filters outbound traffic from the Managed BYOC account, using your own firewall or one the bootstrap deploys	You set variables in the bootstrap Terraform and apply it; Superblocks wires the firewall into your instance at the next deployment
Image mirroring and scanning	Superblocks copies Managed BYOC container images into your own registry so you can scan them; your scan results can block a deployment	Contact your deployment team

Request a configuration

To add or change a configuration, follow the steps on its page if it has one, then contact your Superblocks deployment team. If you are still preparing your initial deployment, share your choices with them before the deployment starts so they are included from day one. The deployment guide shows where each step fits.

Deployment models

Architecture

Managed BYOC deployment

Security

Support

Request a configuration