Stash is now known as Bitbucket Server.
See the

Unknown macro: {spacejump}

of this page, or visit the Bitbucket Server documentation home page.

This page gives an overview of using Stash with AWS


To get started in AWS quickly

... set up a CloudFormation stack using our Quick Start guide.

To learn more about the deployment options for Stash in AWS

... see launching Stash in AWS manually.

Running Stash in the Amazon Web Services (AWS) cloud can give you scalable computing capacity without the need to invest in hardware up front. To this end, Atlassian provides:

  • an Amazon Machine Image (AMI) that you can launch in AWS as a "turnkey" deployment of Stash Server, or use as the starting point for customizing your own more complex deployments,
  • an Amazon CloudFormation template that automates the process of spinning up a Stash Server instance in EC2, and
  • tools and guidelines for backing up, restoring, sizing, and administering your Stash Server instances in AWS.

 Running Stash Data Center in AWS is not supported at this time.

Quick Start guide

The simplest way to launch Stash Server in AWS is to use Atlassian's public Amazon CloudFormation template. See Quick Start with Stash and AWS.

Launching Stash in AWS manually

For more precise control over the components enabled within the Atlassian Stash AMI, including AWS-specific configuration, network and security settings, Launching Stash in AWS manually describes how to launch the AMI by running the EC2 launch wizard.

Performance guidelines

To get the best performance out of your Stash Server deployment in AWS, it's important not to under-provision your instance's CPU, memory, or I/O resources. We provide specific recommendations on choosing AWS EC2 and EBS settings for best performance when running Stash in AWS. See Recommendations for running Stash Server in AWS.

Backing up Stash in AWS

Atlassian also provides Stash DIY Backup utilities that back up and restore your Stash instance in AWS using native AWS snapshots. This provides a number of advantages:

  • Performance: AWS snapshots occur asynchronously resulting in shorter backup downtime for your instances.
  • Durability: The underlying storage of AWS snapshots is in Amazon S3, which is stored redundantly and with high durability. 
  • Availability: AWS snapshots are available across an entire AWS region, and are available for restore even in the event of an outage affecting an entire Availabilty Zone (AZ).

To learn more about how to back up and restore a Stash instance in AWS, see Using Stash DIY Backup in AWS.

The Atlassian Stash AMI

The Atlassian Stash AMI provides a typical Stash Server deployment in AWS, pre-configured and ready to launch. See Launching Stash in AWS manually.

The components bundled in the Atlassian Stash AMI are

  • Stash (either the latest version or a version of your choice, 3.8.0 or higher),
  • an external PostgreSQL database,
  • nginx as a reverse proxy,
  • the Stash DIY Backup utilities pre-configured for native AWS snapshots,
  • an EBS Volume and Instance Store to hold the data.

Administering Stash in AWS

See Administering Stash in AWS for information about performing administration tasks on a Stash instance within AWS, including



Gliffy is unlicensed. Please install a license to draw diagrams in your wiki.

  • configuring variables when launching Stash in AWS
  • maintaining, resizing, upgrading, migrating, and customizing your Stash deployment in AWS
  • additional details about the components within the Atlassian Stash AMI

Securing Stash within AWS

AWS is accessed over the public Internet, so it is important to apply appropriate security measures when running Stash there. See Best practices for securing Stash in AWS for security guidance on a range of security topics, including Amazon Virtual Private Cloud (VPC), Security Groups, and SSL.