© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Darryl S. Osborne – Storage Specialist @ AWS

Brad Bressler –Technical Account Manager @ Atlassian

Neal Riley – Enterprise Evangelist @ Atlassian

December 2, 2016

Atlassian & Amazon EFSCase Study: How Atlassian Used Amazon EFS with JIRA

to Cut Costs and Accelerate Performance

STG207

What to Expect from the Session

Deeper understanding where Amazon EFS sits within our storage

portfolio

Benefits of Amazon EFS

Know why Atlassian chose Amazon EFS and how it benefits their

customers

Batches and Streams

Direct

Connect

Snowball 3rd Party

Connectors

Transfer

Acceleration

Storage

GatewayKinesis Firehose

File

Amazon EFS

Block

Amazon EBS (persistent)

Object

Amazon GlacierAmazon S3Amazon EC2

Instance Store (ephemeral)

AWS Storage Overview

Operating shared file storage today is a pain

App owners and

Developers

Business

Managers

IT administrators Estimate demand

Procure, setup, maintain hardware & space

Provide demand forecasts/business case

Limited flexibility and agility

CAPEX & over-buy

Constant upgrade/refresh cycle

What if you could…

App owners and

Developers

Business

Managers

IT administrators Eliminate management & maintenance

Scale

Migrate code, apps, tools

Build new cloud-native apps

Predict cost & eliminate CAPEX

Increase agility

Less time managing file system

Fully managed file system for EC2

File system access semantics that works with standard OS APIs

Now on-premises NFS clients over AWS Direct Connect

Sharable across thousands of clients

Grow elastically to petabyte scale

Highly available and durable

Strong consistency

What is Amazon EFS?

We focused on changing the game

Simple Elastic Scalable

1 2 3

Highly Durable

Highly Available4

Amazon EFS is Simple

Fully managed

No hardware, network, file layer

Create a scalable file system in seconds!

Seamless integration with existing tools and apps

NFS v4.1—widespread, open

Standard file system access semantics

Works with standard OS file system APIs

Simple pricing = simple forecasting

1

Amazon EFS is Elastic

File systems grow and shrink automatically

as you add and remove files

No need to provision storage capacity or

performance

You pay only for the storage space you use,

with no minimum fee

2

File systems grow to petabyte scale

Throughput & IOPS scale automatically as

file systems grow

Consistent low latencies regardless of file

system size

Support for thousands of concurrent NFS

connections

Amazon EFS is Scalable3

Designed to sustain Availability Zone (AZ)

offline conditions

Resources aggregated across multiple AZs

Superior to traditional NAS availability

models

Appropriate for Production / Tier 0

applications

Highly Durable and Highly Available4

If you have an EC2 application or use case that requires a

file system AND

• Requires multi-attach OR

• Multi-AZ availability/durability OR

• GBs/s throughput OR

• Requires automatic scaling (grow/shrink) of storage

Do you need an EFS file system?

In which regions can I use EFS today?

US East (N. Virginia) – us-east-1

US East (Ohio) – us-east-2

US West (Oregon) – us-west-2

EU (Ireland) – eu-west-1

More coming soon!

Who is Atlassian?

6 offices

worldwide

1,800+

Atlassians

1

7

We believe behind every great

human achievement, there is a team.

Our mission is to unleash the

potential in every team.

17

DISCUSS

What we do for teams

ORGANIZE

COMPLETEWITH YOU R TEAM

Technical Account

Management

We make big teams

successful

Enterprise

Evangelist

Your technical guides in the

evaluation process for

Atlassian enterprise offerings

The need for EFS with JIRA

for Business Teams

Project planning

Progress tracking

The JIRA familyTrack, report, & discuss

for IT Teams

Incident & request tracking

Self-service

SLAs and reports

for Software Teams

Sprint & release planning

Agile boards

Development reports

JIRA Server Deployment

Database

Application Node

Volume storage

Just text by itself,

for impact.

Data Center is the future

Confidential

JIRA Data Center Deployment

Shared Database

Node 2

Shared storage

Node 1 Node 3

Load Balancer

We dogfood allthethings

• Big cool statistic

• 2,56

• Add-Ons in Marketplace

support.atlassian.com

History of SAC

Moving SAC to Data Center

Downtime

Single Server

As load increases… A single server is not enough

Choosing Data Center

HA Provides Redundancy and Scale

Shared Database

Node 2

Shared storage

Node 1 Node 3

Load Balancer

Choosing Data Center

Infrastructure Mountain

Application

Downtime

On Premises

Hardware failures UpdatesDisasters

A clear leader in IaaS

Cost Effective High Performance Secure

Shared Database

Node 2

Shared storage

Node 1 Node 3

Load Balancer

Planning the Infrastructure

PostgreSQL ???Java / Tomcat

NginX

Planning the Infrastructure

Shared Storage and Data Center

Shared StorageAttachments Profile Data

Our Business Requirements

Easy to Setup Cost Effective Easy to Maintain

Our Technical Requirements

Perform Disaster Recovery Secure

Investigating Shared Storage

NFS / EC2

Shared Storage on EC2

GlusterFS / EC2

Calculating True Cost

Licensing

NFS / EC2

Planning the Infrastructure

GlusterFS / EC2Maintenance

Amazon Elastic File System (Amazon EFS)

Our Technical Requirements

Performance Disaster Recovery Secure

Our Technical Requirements

Instant Scale

Our Business Requirements

Easy to Setup Cost Effective Easy to Maintain

Amazon EFS

Testing EFS

Wrote Random Files

1KB – 1GB in Size

Read Files Simultaneously

JIRA Data Center Usage Pattern

Consistent Writes

Infrequent Reads

Results: Consistent Throughput

Throughput was consistent

across randomized writes and

frequent reads

Results: Consistent Capacity

As we increased overall reads

and writes, capacity stayed

within threshold

Amazon EFS

Moving to Production

Moving to Production

Region Availability Zones

Amazon EFS Amazon CloudWatch

Support and GetSupport

support.atlassian.com

getsupport.atlassian.comCustomer Requests

Results: Consistent Writes

JIRA Data Center was writing

files to the Elastic File System

consistently with no significant

dips in performance

Results: Consistent Reads

JIRA Data Center was able to

read from EFS, which provided

bursts of throughput on

request.

And We’re Growing!

0

5000

10000

15000

20000

Tickets Per Month

Tickets Per Month

Our Current Infrastructure

• Elastic Load Balancer

• Auto-Scaling Groups

• Amazon Elastic File System

• Amazon Relational Database Service

AWS Quick Starts

Automated deployment of Data

Center to Amazon Web Services,

built by Amazon architects

Announcing support for Data Center on AWS

AWS Quick Starts

Cloud Formation Templates

Available Today

Automated deployment of Data

Center to Amazon Web Services,

built by Amazon architects

Quick and reliable provisioning of

all the components necessary for

auto-scaling Data Center clusters

Now available for JIRA Software

Data Center and Bitbucket Data

Center. Confluence coming soon!

Announcing support for Data Center on AWS

Remember to complete

your evaluations!

Related Sessions

STG202 - Deep Dive on Amazon Elastic Files System

STG208 - Case Study: How Monsanto uses Amazon EFS

with their large scale geospatial data sets

STG206 - Case Study: How Spokeo improved web

application response times with Amazon EFS

Q&A

Amazon EFS

Thank you!