Skip to content

[Bug]: Lab preparation step fails — “no matching EC2 Subnet found” (Amazon FSx for OpenZFS Workshop) #1543

@rgunasekaran-github

Description

@rgunasekaran-github

Installation method

Own AWS account

What happened?

I’m attempting to follow the Amazon EKS Workshop for FSx for OpenZFS but I’m stuck at the lab infrastructure preparation step. The Terraform run fails with the following error:

╷ │ Error: no matching EC2 Subnet found │ │ with module.lab.data.aws_subnet.private_fsxz, │ on lab/main.tf line 31, in data "aws_subnet" "private_fsxz": │ 31: data "aws_subnet" "private_fsxz" { │ ╵ 🚨 An error occurred, please contact your workshop proctor or raise an issue at https://github.com/aws-samples/eks-workshop-v2/issues The full log can be found here: /eks-workshop/logs/action-1752990972.log

What did you expect to happen?

I expect this lab preparation step to complete successfully so that I can proceed with the FSx for OpenZFS section of the EKS Workshop.

How can we reproduce it?

  • Go to the EKS Workshop for Amazon FSx for OpenZFS.
  • Follow the initial setup steps (select region, bootstrap the environment, etc.).
  • Start the Lab Infrastructure Preparation section.
  • Wait for the Terraform step to execute.
  • Observe the failure during subnet data lookup with the error:

Error: no matching EC2 Subnet found

Note: I used the default settings provided by the workshop and did not modify any Terraform code. The failure occurs early in the process, before any customization is possible.

Let me know if you’d like me to share the full log file or the region I selected.

Anything else we need to know?

  • I used the default VPC setup provided by the EKS Workshop — I did not customize any networking settings.
  • The error seems related to the Terraform aws_subnet data lookup, possibly expecting specific tags or naming that doesn’t match the existing subnets in the region.
  • The workshop didn’t prompt to create or tag subnets manually before this step, so I assume they should be pre-provisioned or auto-discovered.
  • This issue blocks progress at an early stage, so resolving it is critical for continuing the FSx for OpenZFS module.

EKS version

v1.31

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions