This bug is specific to deploying CloudFormation templates through a CI/CD pipeline, in this case Gitlab. If you are using
the intrinsic function Fn::Import statements in your templates, you may have run into this error message
"Template error: the attribute in Fn::ImportValue must not depend on any resources, imported values, or Fn::GetAZs"
If so, the likely culprit is a reference typo within your import statement. However, if you’ve given the template a
once-over and haven’t found any errors, consider checking the deployment script. When I make use of the Import function
in CloudFormation, I often pass a stack name from the CI script to the template as a parameter to allow the name of the
import target to be dynamically constructed. This allows for more flexibility in using the template, but introduces more
opportunities for typos. If there is an error in that parameter, CloudFormation will be unable to resolve the Import, and
will throw the above error.
This post is part of a series of introductory articles related to building AWS services using AWS CloudFormation. You can read about CloudFormation Conditions and about CloudFormation Parameters in earlier posts
By default, Amazon CloudFormation deploys resources defined in a template in parallel. When you think about it, this makes a lot of sense; deploying in parallel CloudFormation can reduce the amount of time it takes to create the services you’ve defined in your template.
GitLab is an integral part of our day-to-day workload on the AWS platform, as we manage well over 110K lines of CloudFormation code across close to one-hundred AWS accounts.
In addition to using it for our internal development purposes, we also use it to deploy and manage solutions for our managed and OrbitOps customers.
In this article, I’ll walk you through how we currently have GitLab deployed and how we integrate it into our customer’s AWS accounts.
What we’re gonna do tonight is actually work with relatively new feature. We’re gonna have a look at how we can create
VPC prefix lists in Cloud Formation. I actually did a really short demo on this feature weeks ago when this was first
announced at the end June. I guess it’s more than a couple weeks ago now, right?
Jul 26, 2020
Your project next
Have a use case in mind? Let's talk it through.
Send a paragraph about what you're trying to do on AWS. I'll come back with
how I'd approach it, or a pointer to someone better suited.
