AWS::UrlSuffix pseudo parameter is not recognized by rule E1019
See original GitHub issue- cfn-lint version: 0.26.3
I am attempting to use a Fn::Sub with the following arguments: https://s3.${AWS::Region}.${AWS::UrlSuffix}/amazoncloudwatch-agent-${AWS::Region}/amazon_linux/amd64/latest/amazon-cloudwatch-agent.rpm
and I am recieving the following error:
E1019 Parameter AWS::UrlSuffix for Fn::Sub not found at Resources/LaunchTemplate/Metadata/AWS::CloudFormation::Init/SharedConfig/files//tmp/amazon-cloudwatch-agent.rpm/source/Fn::Sub
build/sam/template.yml:6178:17
It appears that this rule is too strict or is not aware of the new ${AWS::UrlSuffix}
pseudo-parameter. See the Pseudo Parameter docs for more detail.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
AWS::UrlSuffix pseudo parameter is not recognized by rule ...
cfn-lint version: 0.26.3 I am attempting to use a Fn::Sub with the following arguments: https://s3.${AWS::Region}.
Read more >Pseudo parameters reference - AWS CloudFormation
Lists the details of the available pseudo parameters that are predefined by AWS CloudFormation.
Read more >Pseudo parameters reference - Amazon CloudFormation
Lists the details of the available pseudo parameters that are predefined by Amazon CloudFormation.
Read more >Pseudo parameters - AWS CloudFormation p2.6 - YouTube
Welcome to part 2.6 of this tutorial series on AWS CloudFormation. In this tutorial, I have covered Pseudo parameters in AWS Cloud formation ......
Read more >Pseudo parameters - AWS CloudFormation Workshop
When working with CloudFormation templates, one of the things you should aim for is to write modular and reusable templates to facilitate reuse...
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
Looks like that is how CloudFormation handles it too.
Unresolved resource dependencies [AWS::UrlSuffix] in the Resources block of the template
@kddejong FWIW, CFN to my knowledge has always supported using pseudo parameters in a Fn::Sub. The doc you mentioned gives examples for just two of the pseudo-parameters but doesn’t preclude any others though.