Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS FSx Subnet issue #12601

Closed
ghost opened this issue Apr 1, 2020 · 2 comments · Fixed by #12676
Closed

AWS FSx Subnet issue #12601

ghost opened this issue Apr 1, 2020 · 2 comments · Fixed by #12676
Labels
service/fsx Issues and PRs that pertain to the fsx service.

Comments

@ghost
Copy link

ghost commented Apr 1, 2020

This issue was originally opened by @itdevon as hashicorp/terraform#24517. It was migrated here as a result of the provider split. The original body of the issue is below.


Having issues with AWS FSx, I have two subnets, but the error indicates only a max of 1 subnet.

Terraform Version

Terraform v0.11.14

  • provider.aws v2.55.0

Terraform Configuration Files

resource "aws_fsx_windows_file_system" "orapreshopdbfs" {
storage_capacity = 2000
subnet_ids = ["subnet-1", "subnet-2"]
throughput_capacity = 2048

self_managed_active_directory {
dns_ips = ["10.1.1.1", "10.1.1.2"]
domain_name = "redacted"
organizational_unit_distinguished_name = "redacted"
password = "redacted"
username = "redacted"
}
}

Debug Output

Error: aws_fsx_windows_file_system.orapreshopdbfs: subnet_ids: attribute supports 1 item maximum, config has 2 declared

Expected Behavior

FSx is in mult-zone, so it will need to have two subnets.

Steps to Reproduce

Please list the full steps required to reproduce the issue, for example:

  1. terraform plan

-->

@ghost ghost added the service/fsx Issues and PRs that pertain to the fsx service. label Apr 1, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Apr 1, 2020
@DrFaust92
Copy link
Collaborator

duplicate of #11246

@ghost
Copy link
Author

ghost commented Jul 5, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Jul 5, 2020
@breathingdust breathingdust removed the needs-triage Waiting for first response or review from a maintainer. label Sep 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/fsx Issues and PRs that pertain to the fsx service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants