Skip to main content
Springwinter is a control plane for an AWS account you own. The servers, workers, sites, databases, caches, buckets, logs, and metrics for a project are created in that account. Springwinter assumes a role you create, for a call, and does not keep the temporary keys. This section is written so you can hand it to a security reviewer. Each page states what the product does. It does not stand in for a compliance report.

Your account

You launch the CloudFormation stack. The role trusts Springwinter only with this connection’s external ID. You choose the permissions.

Credentials

What Springwinter stores, what it reads from your account, and what it discards after the call.

GitHub

The GitHub App installation is stored. The token used to clone is minted when a build starts and is not stored.

Where the data lives

Compute, databases, caches, logs, and environment variables stay in your AWS account.

People and sign-in

Sessions, API tokens, email codes, and what every person in the organization can do.

Audit

Optional access logs in your account, and what Springwinter itself records about a deploy.

What a reviewer can check

In your AWS account, in the region you chose for the project. Springwinter’s database keeps the organization, the connection, and the record of each resource. It does not replicate your application database or maintain a full CloudWatch log archive. It retains selected operational observations, caches, and project-chat evidence. See Where the data lives.
It can assume the role while the role trusts it and the external ID matches. That is how a deploy, a log view, and a metrics view work. You can remove the role, delete the stack, or take a permission off the role. A later call then fails. Springwinter does not create the stack. See Your AWS account.
No. Each call uses sts:AssumeRole. The temporary keys are not written to the application database and are not written to logs. The account number, the role ARN, and the connection external ID are stored, because the next call has to know which role to assume. See Credentials.
No. The GitHub App installation is stored. An installation token is minted when a build starts, used to clone into CodeBuild in your account, and not stored. See GitHub.
Onto the ECS task definition in your account, in plaintext, which is how ECS stores container environment. Springwinter does not keep a separate table of those values. The Environment page reads the task definition. A deploy that was given variables can still have them in that workflow run’s input, which Springwinter retains with the run. See Credentials.
Everyone in the organization. People you add share the projects, the AWS connection, and the GitHub connection. There are no separate permission levels. See People and sign-in.
A workflow run keeps its lifecycle. Structured logs from those runs omit workflow input, credentials, and AWS responses. An assume-role log line can include the role ARN, the region, and a session identifier. It does not include the external ID or the keys. See Audit.
No. This section describes the access model in the product. It is not a SOC 2 report, an ISO certificate, or a penetration-test letter.

The boundary, in one place