Amazon FSx recommends choosing an endpoint IP address range that’s within VPC’s IP address range to simplify your networking setup, especially when accessing your data from other AWS services or other networks (on-premises networks or peered networks in AWS).
I'm trying to find this configuration option in https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/fsx_ontap_file_system#endpoint but with no success.
Especially I'm interested in the Floating IP address range outside the VPC configuration.
#FSx for ONTAP - Endpoint IP address range
1 messages · Page 1 of 1 (latest)
Someone from the Terraform team will have to provide an update related to the provider. Back before AWS Re:invent 2022 for multi AZ deployments a FSxN file system's IP address to access the filesystem had to be outside the VPCs being leveraged. This being that floating IP address range you've mentioned. I am only assuming but I'd bet the Terraform provider is lagging a little beyond the enhancement AWS provided near the end of last year per - #|reinvent-2022 message
Looks like endpoint_ip_address_range is the appropriate argument - https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/fsx_ontap_file_system#endpoint_ip_address_range
This is exactly what I would like to understand. Do you know if this is a right chat to ask a question about the timeline implementation of this feature?
For AWS no. This is not something we do. But we have a provider that interfaces with Cloud Manager to create FSxN:
https://registry.terraform.io/providers/NetApp/netapp-cloudmanager/latest/docs/resources/aws_fsx
You may want to raise this as an Issue under the terraform-aws-provider GitHub repo: https://github.com/hashicorp/terraform-provider-aws/issues?q=is%3Aissue+is%3Aopen+fsx
@steady nebula thanks for this comment, but unfortunately CloudManager/BlueXP not an option in the scenario I'м considering. The requirement is to have this feature in aws provider.