Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated links in the proper manner.

Deploying SoftNAS™ on AWS Outposts

AWS Outposts is a fully managed service that extends AWS infrastructure, AWS services, APIs, and tools to virtually any datacenter, co-location space, or on-premises facility for a truly consistent hybrid experience. AWS Outposts is ideal for workloads that require low latency access to on-premises systems, local data processing, or local data storage. An Outpost is a pool of AWS compute and storage capacity deployed at a customer site. AWS operates, monitors, and manages this capacity as part of an AWS Region. You can create subnets on your Outpost and specify them when you create AWS resources such as EC2 instances, EBS volumes, ECS clusters, and RDS instances. Instances in Outpost subnets communicate with other instances in the AWS Region using private IP addresses, all within the same VPC.

How Outpost Works

AWS Outposts is designed to operate with a constant and consistent connection between your Outpost and an AWS Region. To achieve this connection to the Region, and to the local workloads in your on-premises environment, you must connect your Outpost to your on-premises network. Your on-premises network must provide wide area network (WAN) access back to the Region and to the internet. It must also provide LAN or WAN access to the local network where your on-premises workloads or applications reside.


  • One or more AWS Outposts are installed on-site
  • The AWS Outpost’ compute and storage capacity are available for allocation

Deploying a Buurst SoftNAS instance on AWS Outpost

Deploying a Buurst SoftNAS™ instance on AWS Outpost follows the same steps as deploying in AWS regions. During the AMI launch process the Outpost subnet will be listed as a deployment option.

Stand Alone Instance

SNAP Replicate Disaster Recovery

SnapHA™ High Availability

Supported configurations:

  • HA between 2 subnets on a single Outpost rack
  • HA between 2 Outpost racks in the same data center
  • HA between Outpost on-premises rack and in cloud subnet
    • HA is currently tested and supported for a single VPC
    • A Direct Connect or similar high-speed connection between the on-premise site to AWS is required