You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS have long had an option to use a new format for ECS arns for services, tasks and container-instances, see https://aws.amazon.com/blogs/compute/migrating-your-amazon-ecs-deployment-to-the-new-arn-and-resource-id-format-2/
What's new is that from October 2020 these options default to on for new accounts, and April 2021 they become mandatory for all accounts. So from that latter date our existing empire controllers will see a mix of old & newer formats.
I've tested this by making a new account with the options turned on and it mostly works. The only fault I've found so far is that emp ps breaks, giving a "invalid ARN resource" error, likely from
AWS have long had an option to use a new format for ECS arns for services, tasks and container-instances, see https://aws.amazon.com/blogs/compute/migrating-your-amazon-ecs-deployment-to-the-new-arn-and-resource-id-format-2/
What's new is that from October 2020 these options default to on for new accounts, and April 2021 they become mandatory for all accounts. So from that latter date our existing empire controllers will see a mix of old & newer formats.
I've tested this by making a new account with the options turned on and it mostly works. The only fault I've found so far is that
emp ps
breaks, giving a "invalid ARN resource" error, likely fromempire/pkg/arn/arn.go
Lines 63 to 77 in 7ab6b86
Anybody else come across this?
The text was updated successfully, but these errors were encountered: