From my experience, there are areas in Amazon FSx where more performance is needed, as they will be looking for higher IOPS. Sometimes we go with Weka or other solutions due to this need, so it should have more IO capacity when there is a demand. More performance is needed specifically in the IO area.
Amazon FSx is more costly compared to other storage solutions like EBS or EFS. The auto-scaling feature should be improved, as it currently includes downtime. I need to manually increase the storage, which is not ideal. Integrating FSx with Windows Server is challenging; it's a long process involving Active Directory (AD) setup and synchronization.
A direct FTP feature would be beneficial instead of relying on transmission services. Although I haven't worked extensively with FSx, there seems to be room for more improvement.
In the last month, I've been facing a challenge when doing a failover from FSx side. AWS console does not refresh within a half hour. It sometimes takes more than an hour. So we have to go to FSx command mode to check the status of the file system (read, write, and operational status). That is the main challenge I am facing from the AWS console side regarding the FSx implementation. I wrote a service case with AWS, but they explained it takes some time for disaster recovery purposes, and they were looking into it. As of now, it's not fixed. Secondly, I faced some challenges with mirroring from FSx side, which AWS is providing the services for. Sometimes the pool we use to share the volumes is connecting with all CIFS and NFS mount points. So, we are working on it. We have to do a little bit more work on filtering with that image mirroring and the broken issue. We are not using the console mode. We are using the automation tool Boto3. So, I'm using the FSx module to integrate with Boto3 and Lambda. There are some issues at the sync breaking point, which you can also see on the FSx AWS page. Some applications are active-passive. That is fine; we can set it to work within five to fifteen minutes. But some applications are in an active-active environment with high availability. So that time frame is not sufficient. So I think the product has to be worked on regarding sync mirroring along with the broken issue. I have one more thing. FSx is an Amazon product, so it should have some training provided, like the skill builder AWS offers. I expect that we can also get some training or proper documentation for FSx. That's the main concern from the AWS side because AWS provides FSx support. But I haven't seen good FSx documentation in Skill Builder. That would be really awesome for other users as well. We should get documentation and training related to FSx. We have a number of resources that AWS provides, but I've seen very little documentation, training videos, or anything else specifically for FSx, even though there's no separate training from FSx like AWS provides in Skill Builder for other tools, technologies, and resources. I'd highlight three things. One is during failover. Second is during switchback and switchover. Third is the documentation and training. These three areas are major concerns. In terms of the technology, tool, stability, scalability, and reliability, everything seems good. There's no issue with the tools and technology themselves, just those three things where we need help from the FSx side or AWS side.
File System Software enables efficient management of data by organizing files and directories on storage devices. It is crucial for ensuring data accessibility, storage optimization, and system performance, addressing the complex needs of enterprises handling large volumes of data.This software category is designed to manage file systems on different operating systems, facilitating tasks like file navigation, creation, deletion, reading, and writing operations. Some solutions offer advanced...
From my experience, there are areas in Amazon FSx where more performance is needed, as they will be looking for higher IOPS. Sometimes we go with Weka or other solutions due to this need, so it should have more IO capacity when there is a demand. More performance is needed specifically in the IO area.
Amazon FSx is more costly compared to other storage solutions like EBS or EFS. The auto-scaling feature should be improved, as it currently includes downtime. I need to manually increase the storage, which is not ideal. Integrating FSx with Windows Server is challenging; it's a long process involving Active Directory (AD) setup and synchronization.
A direct FTP feature would be beneficial instead of relying on transmission services. Although I haven't worked extensively with FSx, there seems to be room for more improvement.
In the last month, I've been facing a challenge when doing a failover from FSx side. AWS console does not refresh within a half hour. It sometimes takes more than an hour. So we have to go to FSx command mode to check the status of the file system (read, write, and operational status). That is the main challenge I am facing from the AWS console side regarding the FSx implementation. I wrote a service case with AWS, but they explained it takes some time for disaster recovery purposes, and they were looking into it. As of now, it's not fixed. Secondly, I faced some challenges with mirroring from FSx side, which AWS is providing the services for. Sometimes the pool we use to share the volumes is connecting with all CIFS and NFS mount points. So, we are working on it. We have to do a little bit more work on filtering with that image mirroring and the broken issue. We are not using the console mode. We are using the automation tool Boto3. So, I'm using the FSx module to integrate with Boto3 and Lambda. There are some issues at the sync breaking point, which you can also see on the FSx AWS page. Some applications are active-passive. That is fine; we can set it to work within five to fifteen minutes. But some applications are in an active-active environment with high availability. So that time frame is not sufficient. So I think the product has to be worked on regarding sync mirroring along with the broken issue. I have one more thing. FSx is an Amazon product, so it should have some training provided, like the skill builder AWS offers. I expect that we can also get some training or proper documentation for FSx. That's the main concern from the AWS side because AWS provides FSx support. But I haven't seen good FSx documentation in Skill Builder. That would be really awesome for other users as well. We should get documentation and training related to FSx. We have a number of resources that AWS provides, but I've seen very little documentation, training videos, or anything else specifically for FSx, even though there's no separate training from FSx like AWS provides in Skill Builder for other tools, technologies, and resources. I'd highlight three things. One is during failover. Second is during switchback and switchover. Third is the documentation and training. These three areas are major concerns. In terms of the technology, tool, stability, scalability, and reliability, everything seems good. There's no issue with the tools and technology themselves, just those three things where we need help from the FSx side or AWS side.