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:UpdateInstanceInformation
ec2messages:*
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
AmbassadorImage
toProxyImage
. - Rename parameter from
AmbassadorCommand
toProxyCommand
. - Rename parameter from
AmbassadorPort
toProxyPort
. - Rename parameter from
AmbassadorEnvironment1Key
toProxyEnvironment1Key
. - Rename parameter from
AmbassadorEnvironment1Value
toProxyEnvironment1Value
. - Rename parameter from
AmbassadorEnvironment2Key
toProxyEnvironment2Key
. - Rename parameter from
AmbassadorEnvironment2Value
toProxyEnvironment2Value
. - Rename parameter from
AmbassadorEnvironment3Key
toProxyEnvironment3Key
. - Rename parameter from
AmbassadorEnvironment3Value
toProxyEnvironment3Value
.
Deprecation warnings
ecs/cluster
: The parameterDesiredCapacity
will be removed in v11 (not needed anymore)jenkins/jenkins2-ha-agents
: The parameterAgentDesiredCapacity
will be removed in v11 (not needed anymore)state/rds-aurora-serverless
: The parameterEngine
will be removed in v11 (replaced byEngineVersion
)