Skip to main content

Purpose and scope

SuprSend BYOC is a shared-responsibility service. SuprSend runs and maintains the application and the resources it provisions, and the client owns its AWS account, its governance and its own security monitoring. This document sets that boundary for new and existing BYOC clients. This is different from selfhosting SuprSend where the user owns everything. In BYOC, SuprSend runs in the client’s AWS account. SuprSend provisions the AWS resources the platform needs (network, Kubernetes cluster, databases, storage) and deploys and operates the application on them. SuprSend owns resources it provisions and deploys. The client owns the account those resources live in, and anything not listed in this document.

Responsibility matrix

SuprSend owns the application and every AWS resource it provisions. The client owns the AWS account and everything else.

Commitments and limits

  • Kubernetes version: SuprSend keeps EKS on the latest supported Kubernetes version.
  • Upgrades needing downtime: SuprSend requests a maintenance window from the client and performs the upgrade.
  • Audit logging: covers AWS API activity (CloudTrail). Client can create alerts on top of the audit trail if needed.
  • Encryption keys: data is encrypted with AWS-managed keys.