fsx for openzfs multi-az in shared vpc is unsupported
Open
Nobody has claimed this yet.
aws
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
We ran into this with a customer and have opted to go with single-az in the meantime.
Creating OpenZFS Multi-AZ file systems in shared subnets from a participant account is currently not supported. The subnets provided must be owned by the AWS account submitting the request.
It appears that this feature is functional for the fsx ontap filesystem type: https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/creating-file-systems.html#fsxn-vpc-shared-subnets
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. First verify the AWS support and account-ownership constraints for FSx for OpenZFS Multi-AZ in shared VPC subnets, then locate the toolkit path that creates this filesystem type. Done would require a defined change or an explicit decision that the limitation must be documented or handled differently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100