Mismatch between lint definitions and Cloudformation for AWS::ECS::Service.NetworkConfiguration.AwsvpcConfiguration
See original GitHub issuecfn-lint version: (cfn-lint --version
)
0.36.0
Description of issue. The linter gives an error, while Cloudformation disagrees. For the resource type AWS::ECS::Service there is a property NetworkConfiguration. According to the Cloudformation documentation the property AwsvpcConfiguration has a lower case v (I confirmed this is actually the case by deploying a Cloudformation stack). The cfn-lint with version 0.36.0 expects AwsVpcConfiguration with an upper case v. With earlier versions this didn’t give any errors. Cloudformation will not accept an upper case v.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (6 by maintainers)
Top Results From Across the Web
ECS::Service AwsVpcConfiguration - AWS CloudFormation
An object representing the networking details for a task or service.
Read more >E3002 Invalid Property Resources/Service ...
cfn-lint 0.37.0 Linter started giving Error on previously valid template wich cloudformation is ok with E3002 Invalid Property ...
Read more >ECS::Service via cloudformation yaml, got Model validation ...
I'm curious how you solved your "expected type: Number" error, as I have the same error for setting up a task definition. It's...
Read more >How to Create an AWS CloudFormation Fargate Template
Add Task Definition. First thing to do, is to create the CloudFormation yaml template. You can do so by means of a text...
Read more >Amazon CloudFormation best practices
You can also choose to integrate cfn-lint in your source code repository's configuration, so that you can perform template validation when you commit...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@p4k03n4t0r this is caused by the ongoing migration of
AWS::ECS::Service
to the CloudFormation RegistryCan workaround with resource-level ignores:
Or use 0.35.1 which is what we did.