CASE STUDY #1
Triofox and AWS File Gateway work hand in hand
A private investment firm deployed AWS File Gateway to address capacity constraints on its on-premises file server. The company had about 8 TB of data, which is close to the limit of an on-premises file server. Therefore, AWS S3 File Gateway was used to move data from the on-premises file server to Amazon S3. Employees at the corporate site can access SMB shares provided by the on-premises file server and the AWS File Gateway appliance (based on a virtual machine). This worked well until the pandemic broke out in 2020. When everyone started working from home, the problem arose that the on-premises file server and AWS File Gateway are all on-premises appliances, which means access is not easy without an enterprise VPN. And a VPN is considered either a security risk (since it exposes the entire network) or inconvenient. So how can you access files from your employees' home offices without a VPN (but the data is in Amazon S3 anyway)? It's certainly not practical to require every employee to install an AWS File Gateway appliance in every home office to meet access requirements. This is where Triofox comes in. Triofox installs on an Amazon EC2 instance and provides an HTTPS RESTful-based protocol for file access. Triofox also has Windows client agents, macOS agents, web browser agents and Active Directory integration. So when employees work from home, they get a mapped drive to the same Amazon S3 bucket provided by AWS File Gateway. In addition, this solution now provides mobile access, offline editing, and file sharing in the web browser with Active Directory identity integration.