ECS Service ARN format broken? #21626
-
Hi! I've got two separate CDK applications... one for my pipeline, the other for the application infrastructure being deployed. The application uses an ECS EC2 Cluster and service. The application infrastructure deploys correctly, and one of the outputs is the ECS service's ARN. When the pipeline gets to it's deploy stage, it fails saying Here's my deploy action (really simple):
The service is higher up in code, and looks like this:
The problem seems to be that the service definition is expecting the old format for a service ARN: Is this a bug in the CDK or is there something I'm missing somewhere? Right now the only fix is to go into the console and fix the inputs. I'd rather not have to do that, obviously as it creates drift. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
In PR request #18140 a new feature flag was added to support the new ECS ARN format. It is available since CDK v2.35.0. The new feature flag Could you please upgrade your CDK version to v2.35.0 or higher (if not already done) and enable the feature flag? |
Beta Was this translation helpful? Give feedback.
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
In PR request #18140 a new feature flag was added to support the new ECS ARN format. It is available since CDK v2.35.0.
The new feature flag
@aws-cdk/aws-ecs:arnFormatIncludesClusterName
is mentioned in the CDK ECS documentation.Could you please upgrade your CDK version to v2.35.0 or higher (if not already done) and enable the feature flag?