[Bug]: vpc not created on getting started

[csantanapr]

Welcome to Amazon EKS Blueprints!

• Yes, I've searched similar issues on GitHub and didn't find any.

Amazon EKS Blueprints Release version

master commit b0d8671

What is your environment, configuration and the example used?

Using macOS
Terraform

❯ terraform version
Terraform v1.2.1
on darwin_amd

AWS CLI

❯ aws --version
aws-cli/2.7.4 Python/3.9.11 Darwin/21.4.0 exe/x86_64 prompt/off

What did you do and What did you see instead?

Using a fresh aws account, no VPC in west-2, only the default vpc there

Following getting started here https://aws-ia.github.io/terraform-aws-eks-blueprints/getting-started/

git clone https://github.com/aws-ia/terraform-aws-eks-blueprints.git
cd examples/eks-cluster-with-new-vpc/
terraform init
terraform plan

Running the apply stated in the doc to create VPC

terraform apply -target="module.aws_vpc"

It doesn't create the VPC, here is the output

❯ terraform apply -target="module.aws_vpc"

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.
╷
│ Warning: Resource targeting is in effect
│ 
│ You are creating a plan with the -target option, which means that the result of this plan may not represent all of the changes
│ requested by the current configuration.
│ 
│ The -target option is not for routine use, and is provided only for exceptional situations such as recovering from errors or
│ mistakes, or when Terraform specifically suggests to use it as part of an error message.
╵
╷
│ Warning: Applied changes may be incomplete
│ 
│ The plan was created with the -target option in effect, so some changes requested in the configuration may have been ignored and the
│ output values may not be fully updated. Run the following command to verify that no other changes are pending:
│     terraform plan
│ 
│ Note that the -target option is not suitable for routine use, and is provided only for exceptional situations such as recovering from
│ errors or mistakes, or when Terraform specifically suggests to use it as part of an error message.
╵
╷
│ Warning: Redundant ignore_changes element
│ 
│   on .terraform/modules/eks_blueprints.aws_eks/main.tf line 298, in resource "aws_eks_addon" "this":
│  298: resource "aws_eks_addon" "this" {
│ 
│ Adding an attribute name to ignore_changes tells Terraform to ignore future changes to the argument in configuration after the object
│ has been created, retaining the value originally configured.
│ 
│ The attribute modified_at is decided by the provider alone and therefore there can be no configured value to compare with. Including
│ this attribute in ignore_changes has no effect. Remove the attribute from ignore_changes to quiet this warning.
╵
╷
│ Warning: Experimental feature "module_variable_optional_attrs" is active
│ 
│   on .terraform/modules/eks_blueprints_kubernetes_addons.ondat/locals.tf line 2, in terraform:
│    2:   experiments = [module_variable_optional_attrs]
│ 
│ Experimental features are subject to breaking changes in future minor or patch releases, based on feedback.
│ 
│ If you have feedback on the design of this feature, please open a GitHub issue to discuss it.
│ 
│ (and 72 more similar warnings elsewhere)
╵

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Additional Information

No response

[vara-bonthu]

@csantanapr can this be closed as well?

[csantanapr]

@vara-bonthu this is a dupe and is working for me now with correct module command “terraform apply -target=module.vpc”