Skip to main content
Springwinter deploys and manages resources inside your AWS account using a dedicated IAM role that you create through a CloudFormation stack. You remain in full control of that role — you can inspect its permissions, restrict it further, or delete it at any time. Springwinter never receives long-lived AWS credentials; instead, it assumes the role on demand using a secure external ID unique to your account, and the temporary session keys it receives expire automatically.

How the connection works

When you launch the CloudFormation stack, AWS creates a single IAM role in your account. That role’s trust policy allows only the Springwinter control plane to assume it, and only when it presents your unique external ID — a connection-specific value that helps prevent confused-deputy access. An external ID is not multi-factor authentication. Each time Springwinter needs to take an action in your account — creating a service, reading a log group, fetching a cost estimate — it calls sts:AssumeRole, receives short-lived credentials scoped to that session, uses them for the operation, and discards them. No access keys are ever written to a database. Preventing new role assumptions does not by itself cancel work already in progress. Review active AWS sessions when revoking access; see AWS role-session revocation.

Connect your AWS account

1

Open Cloud settings

Open Settings → Cloud and select Connect AWS. Enter the 12-digit AWS account number. Springwinter prepares the stack name, role name, and connection external ID.
2

Review the prepared stack

Open the CloudFormation link in the AWS account you entered. Keep the prepared stack name, role name, and external ID. Review the template and its permissions before approving IAM changes.
3

Create the stack

Create the stack in AWS and wait for CREATE_COMPLETE. Check its Events tab if creation fails. Completion time depends on AWS and account configuration.
4

Save and verify the connection

Return to the open Springwinter dialog and save. Springwinter checks that it can assume the prepared role with the connection external ID. You do not paste a role ARN into this flow. Resolve a failed verification before deploying resources.
The connection role does not attach AdministratorAccess. It includes service-management permissions and AWS-managed ReadOnlyAccess, which grants broad reads across the AWS account, including resources outside Spring Winter projects. AWS can change this managed policy. Review the complete template before approving it. Preflight rejection for missing required permissions prevents that launch from starting. Later AWS failures can still leave partially created infrastructure; inspect the workflow and cleanup outcome.

Required IAM permissions

See CloudFormation permissions for the complete inline action list, resource scopes, trust conditions, and the attached managed policy. The template includes account-wide AWS-managed ReadOnlyAccess alongside management permissions in the categories below. This table summarizes use; it is not the complete policy. Capability checks can reject missing required launch permissions before provisioning. They do not guarantee that every later AWS action will succeed under service control policies (SCPs), permission boundaries, quotas or changing account state.

What Springwinter stores

Springwinter stores only the metadata necessary to locate and assume your role:
  • AWS account number — to scope API calls to your account
  • Role name and ARN — to construct the AssumeRole call
  • External ID — to satisfy the trust policy condition
  • Connection status — active or disconnected
Temporary session credentials returned by sts:AssumeRole are used in memory for a single operation and are never written to disk or a database.
Use AWS CloudTrail with the management and data event coverage your review requires. Calls made through the connection role carry an assumed-role identity; workload and build roles have their own identities. Do not assume default event history captures every data-plane action.

Disconnect your AWS account

To revoke Springwinter’s access, delete the CloudFormation stack from your AWS Console (CloudFormation → Stacks → select the Springwinter stack → Delete). Deleting the stack removes the IAM role, immediately preventing any further AssumeRole calls. Deleting the role blocks new assumptions after AWS processes the change. Review or revoke active sessions separately when required. Workload resources are not deleted by removing the connection stack, and can continue to incur AWS charges.

Update the connection stack

Spring Winter checks whether your connection stack uses the current CloudFormation template. If it needs an update, the dashboard shows Your AWS connection needs an update. Select Update now to open the review guide. Publishing a template does not itself update your stack. Spring Winter operators can start a reviewed version rollout for compatible stacks. Some changes, including initial updater permissions or managed-policy attachment changes, require manual review and update. For a manual update, review the stack and template in AWS. Keep the existing parameter values. Review the requested permissions, then apply the update in CloudFormation if you agree. Wait for CloudFormation to show UPDATE_COMPLETE, then return to Spring Winter and select Check update status. The notice clears after Spring Winter verifies the installed template version. Closing the guide does not mark the update complete. Spring Winter reuses a successful check for up to one hour. Select Check again to bypass that cache. A failed check does not mean that your connection is current.