Overview
Runlayer issues the Sentry Relay credentials for your deployment. Keep them outside Git and deliver them through the deployment platform’s secret mechanism. Expected fields:Kubernetes with Runlayer Operator
Place the values in a Kubernetes Secret in the tenant namespace. The default Secret name isrunlayer-sentry-relay; required keys are public_key,
secret_key, and id.
Enable the component in RunlayerInstance:
spec.components.sentryRelay.secretRef when the Secret name or key names
differ. See Optional component Secrets.
Do not place Relay credentials in instance values. Use External Secrets,
Terraform, or the customer’s approved secret-delivery controller.
ECS with Terraform
On ECS the Relay credentials are three keys of the provisioned tenant secret,restricted/<project>-<env>-provisioned in your AWS account, which Runlayer
creates and fills alongside the WorkOS and Resend keys: SENTRY_RELAY_PUBLIC_KEY,
SENTRY_RELAY_SECRET_KEY and SENTRY_RELAY_ID (the backend reads SENTRY_DSN
from the same secret). Terraform never reads these values; the module only looks
the secret up and points the Relay task at it. No external program runs during
terraform plan, and nothing credential-related is passed as a Terraform input.
See Secrets management.
Because Terraform cannot see whether the secret carries Relay credentials,
sentry_relay_enabled (default true) decides on its own: set it to false
for a deployment Runlayer has not issued Relay credentials to, which also keeps
frontend Sentry off. Set sentry_dsn to the backend DSN the secret carries when
you want frontend Sentry; it never reaches tasks.
Rotation
- Runlayer writes a new version of the provisioned tenant secret (ECS) or you update the Kubernetes Secret.
- Restart or roll out the affected workload (on ECS, force a new deployment of the Relay and backend services; no Terraform change is needed).
- Verify Relay health and backend event delivery.
Troubleshooting
- Missing Secret: confirm namespace, Secret name, and key selectors.
- Relay disabled: confirm
spec.components.sentryRelay.enabled. - ECS Relay task fails to start: confirm the provisioned tenant secret’s current version carries all six keys; ECS rejects a reference to a missing JSON key.
- No events: verify outbound HTTPS to Sentry and the Relay configuration.
Security
- Never commit credential values.
- Restrict Secret read access to the Relay workload and deployment controller.
- Rotate immediately after suspected exposure.
- Audit Secrets Manager reads and Kubernetes Secret updates.