SwiftStack Filesystem Gateway

Amanda -

The SwiftStack Filesystem Gateway exposes object-stored data as SMB/CIFS or NFS files to file-based applications. In addition, SwiftStack object storage can be accessed using the Gateway or through the Swift HTTP RESTful API, so the same data can be accessed as either files or objects.

The Filesystem Gateway is a component of a SwiftStack deployment and is managed through the SwiftStack Controller’s web interface, including configuring  the desired filesystem mount points and enterprise integrations, including AD/LDAP for the Filesystem Gateway. Once deployed the Gateway bridges the two data types, allowing data to be stored and accessed as an object while also being accessed as a file. 

Learn more about the Filesystem Gateway in our docs: https://swiftstack.com/docs/gateway/intro_overview.html
















When the Gateway is added to a deployment, its management and monitoring is handled by the SwiftStack Controller. This management includes the configuration of performance options as well as external auth systems such as LDAP/AD. As is the case with SwiftStack Nodes, this management channel for the Gateway is independent of the data path.













The Gateway provides file-based applications with access to object-based data that is stored in the SwiftStack Cluster. The Gateway handles access requests by checking for a recent copy of the data in its local cache. If the data is not there, the Gateway will retrieve the data from the Cluster. The data is exposed to the file-based application on the Gateway’s locally configured filesystem mount point. Using a time-based criterion, the Gateway will identify cached data no longer being written to by the application and move that data back into the Cluster.  



As demand increases on the Gateway the most cost-effective and targeted way to meet that need could be to scale out by ingesting additional Gateways and linking them to the Cluster. A multiple gateway solution distributes the demand and ensures there is no single point of failure for the system. Implementing additional Gateways is done on the SwiftStack Controller with no downtime or decrease in performance.




Have more questions? Submit a request


Powered by Zendesk