New: Become a sponsor via GitHub Sponsors!
Migrate from v9 to v10
*
If you have SystemsManagerAccess set to true, we previously attached the managed policy AmazonEC2RoleforSSM but now only attach the following IAM permissions:
ssmmessages:*ssm:UpdateInstanceInformationec2messages:*
This reducdes the permissions but is sufficient to make SSM Session Manager and Run Commands work.
To restore the previous permissions (which are not following the least privilege principle), set the new parameter ManagedPolicyArns to arn:aws:iam::aws:policy/service-role/AmazonEC2RoleforSSM.
fargate/service-*
- Rename parameter from
AmbassadorImagetoProxyImage. - Rename parameter from
AmbassadorCommandtoProxyCommand. - Rename parameter from
AmbassadorPorttoProxyPort. - Rename parameter from
AmbassadorEnvironment1KeytoProxyEnvironment1Key. - Rename parameter from
AmbassadorEnvironment1ValuetoProxyEnvironment1Value. - Rename parameter from
AmbassadorEnvironment2KeytoProxyEnvironment2Key. - Rename parameter from
AmbassadorEnvironment2ValuetoProxyEnvironment2Value. - Rename parameter from
AmbassadorEnvironment3KeytoProxyEnvironment3Key. - Rename parameter from
AmbassadorEnvironment3ValuetoProxyEnvironment3Value.
Deprecation warnings
ecs/cluster: The parameterDesiredCapacitywill be removed in v11 (not needed anymore)jenkins/jenkins2-ha-agents: The parameterAgentDesiredCapacitywill be removed in v11 (not needed anymore)state/rds-aurora-serverless: The parameterEnginewill be removed in v11 (replaced byEngineVersion)