Skip to main content
Springwinter’s connection CloudFormation stack creates an AWS Identity and Access Management (IAM) role in your account. Use this reference to review its managed policies, all inline permission statements, and the conditions for assuming the role before you connect AWS.

Scope of this reference

This inventory was checked against the published connection template on 11 November 2026. Your installed stack can use an older version. Review the template in your CloudFormation launch link and the policies attached to your installed role. Template version tag:
The role grants broad access. Many write statements use Resource: "*", without project, tag, or region conditions. These permissions can reach resources outside Springwinter projects. The role can read secrets, read S3 objects, delete resources, create IAM roles, and change inline role policies. The restricted PassRole statements do not restrict the separate IAM role-management statements.

AWS-managed policy

The role attaches ReadOnlyAccess (arn:${AWS::Partition}:iam::aws:policy/ReadOnlyAccess). This adds broad account-wide read permissions beyond the inline statements below. It can include access to data, not only resource metadata. AWS maintains this policy and can change its actions without a Springwinter template update. Review the complete current policy JSON in the AWS ReadOnlyAccess policy reference. The inline inventory below is not the full effective permission set by itself. The template does not attach AdministratorAccess.

Trust policy

The role permits sts:AssumeRole by the AWS account supplied as ControlPlaneAwsAccountId, with a StringEquals condition requiring the connection’s ExternalId. The role name comes from RoleName, with the required format SpringWinter- followed by eight letters or digits. The external ID is a confused-deputy control, not multi-factor authentication.

Complete inline permissions

Each section preserves one policy statement, including its exact action names, resource scope, and conditions. All statements have Effect: "Allow". ${AWS::Partition}, ${AWS::AccountId}, ${AWS::StackId}, and ${RoleName} represent values that CloudFormation resolves for your stack. Fixed arn:aws strings remain as written in the template. A statement’s resource restriction applies only to that statement. Other statements and the attached managed policies can grant overlapping access. AWS service control policies, permission boundaries, and explicit denies can further restrict effective access.
Manage project networks, container services, load balancers, certificates, image repositories, builds, logs, and static website delivery. This also permits IAM role creation and inline policy changes.
Create the service-linked role for Elastic Load Balancing. The service name condition and role ARN limit this statement.
Create the service-linked role for ECS. The service name condition and role ARN limit this statement.
Read EC2 account attributes.
Read security groups associated with VPCs.
Read the connection stack and its change sets.
Create and execute change sets for this connection stack. The change set name must match sw-update-*.
Read the inline policies and managed policy attachments of this connection role.
Through CloudFormation, create, read, version, and delete managed policies under this connection role’s policy path.
Through CloudFormation, attach or detach managed policies from that path on the existing connection role.
Read role policies for the architecture view. This statement targets sw-* roles in your account.
Read AWS-managed and customer-managed IAM policy versions.
Read public access, encryption, and versioning settings. Bucket name patterns are sw-, b, and l*; they are not ownership checks.
Discover log groups.
Manage ElastiCache Serverless caches and create VPC endpoints.
Configure bucket encryption, versioning, CORS, lifecycle, metrics, and access logging. List object versions and delete object versions.
Manage RDS instances, clusters, replicas, snapshots, subnet groups, and parameter groups. Manage and read Secrets Manager secrets. Create KMS grants and use the listed cryptographic operations. RotateSecret is a granted permission; automatic database password rotation is not currently provided.
Discover ECS tasks and start Systems Manager sessions for gateway connections.
Read cost and usage data.
Manage load balancer attributes and database cluster parameter groups. Read S3 objects, including audit log objects.
Discover models and inference profiles. Manage model agreements, use-case submission, and AWS Marketplace subscriptions. This statement does not grant model invocation; selected model access is configured separately on workload roles.
Pass matching ECS task and CodeBuild roles to the services listed in the condition.
Pass matching ECS infrastructure roles to ECS.

Spring Winter model endpoint managed policy

The template creates a customer-managed IAM policy and attaches it to the connection role. CloudFormation creates it under /springwinter/connection/${RoleName}/. This policy adds EC2 launch and lifecycle permissions, instance profile management, and load balancer routing for model endpoints. Some discovery and routing actions have account-wide scope. Review these statements together with the inline policy and AWS-managed ReadOnlyAccess.
Discover GPU images, instances and offerings. Manage security group egress and load balancer target registration and attributes. These actions have no resource restriction in this statement.
Allow launch to reference AMIs and this account’s subnets and security groups.
Allow launch to create instances, volumes and network interfaces with the model endpoint request tag.
Start, stop and terminate instances in this account with the model endpoint tag.
Manage EC2 instance profiles named sw-model-* in this account.
Pass roles named sw-model-* in this account to EC2.

Review updates and revoke access

Read Connect AWS before creating the stack. Review connection stack updates before applying a new template. Publishing a template alone does not update an existing stack. Compatible stacks can receive an operator-triggered rollout of a reviewed version; connections without the scoped updater permissions need a one-time manual update. Removing the connection from Springwinter does not revoke AWS access. Delete the connection CloudFormation stack or remove the role’s trust to stop new role assumptions. Allow for AWS propagation and review active sessions separately. Existing workloads and their roles remain in your account and can continue to incur charges. See Your AWS account for the connection and revocation details.