Running Scroll SDK in Production

Overview

This guide will support DevOps teams in running Scroll SDK in a production environment. This requires many considerations beyond a local Devnet deployment.

For a more hands-on guide looking at specifics, see our Digital Ocean guide, which walks through a full Kubernetes deployment using an easy-to-understand interface. We also have an AWS guide available.

Monitoring

See the Monitoring section for more information.

Ingress

We’re using Nginx and Cert Manager. More info later.

Secrets

We use External Secret Manager to store secrets. This is a Kubernetes-native solution that allows you to store secrets in a separate repository. This is a more secure way to store secrets than in the Scroll SDK repository, but you will still need to bring your own secret management tool. This could be Hashicorp Vault, AWS Secret Manager, or similar.

Our CLI tool currently supports a development mode Hashicorp Vault and AWS Secret Manager. The Digital Ocean guide uses Hashicorp vault, while the AWS guide uses AWS Secret Manager.

Machine Resources

In addition to 3 databases (and an optional database for Blockscout), we’ll be providing guidance on the resources needed for each Scroll service.

Sepolia Configuration

For Scroll’s Sepolia environment, we use the following resources: