Atlassian used Amazon EFS with JIRA to cut costs and accelerate performance. Testing showed Amazon EFS provided consistent throughput and capacity as usage increased. Atlassian now uses EFS for their production JIRA Data Center deployment, which benefits from EFS's automatic scaling, high availability, and lower costs compared to on-premises shared storage.

1. © 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 EFS
Case Study: How Atlassian Used Amazon EFS with JIRA
to Cut Costs and Accelerate Performance
STG207

2. 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

3. Batches and Streams
Direct
Connect
Snowball 3rd Party
Connectors
Transfer
Acceleration
Storage
Gateway
Kinesis Firehose
File
Amazon EFS
Block
Amazon EBS
(persistent)
Object
Amazon GlacierAmazon S3
Amazon EC2
Instance Store
(ephemeral)
AWS Storage Overview

4. 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

5. 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

6.  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?

7. We focused on changing the game
Simple Elastic Scalable
1 2 3
Highly Durable
Highly Available
4

8. 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

9. 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

10. 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

11. 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

12. 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?

13. 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!

14. Who is Atlassian?

16. 6 offices
worldwide
1,800+
Atlassians

17. 1
7
We believe behind every great
human achievement, there is a team.
Our mission is to unleash the
potential in every team.
17

18. DISCUSS
What we do for teams
ORGANIZE
COMPLETE WITH YOUR TEAM

19. Technical Account
Management
We make big teams
successful

20. Enterprise
Evangelist
Your technical guides in the
evaluation process for
Atlassian enterprise offerings

21. The need for EFS with JIRA

22. for Business Teams
Project planning
Progress tracking
The JIRA family
Track, report, & discuss
for IT Teams
Incident & request tracking
Self-service
SLAs and reports
for Software Teams
Sprint & release planning
Agile boards
Development reports

23. JIRA Server Deployment
Database
Application Node
Volume storage

25. text by
itself,
for
Data Center
is the future
Confidential

26. JIRA Data Center Deployment
Shared Database
Node 2
Shared storage
Node 1 Node 3
Load Balancer

27. We dogfood allthethings

28. • Big cool statistic
• 2,
5
• Add-Ons in Marketplace
support.atlassian.com

29. History of SAC

30. Moving SAC to Data Center

31. Downtime

32. Single Server
As load increases… A single server is not enough

33. Choosing Data Center
HA Provides Redundancy and Scale

34. Shared Database
Node 2
Shared storage
Node 1 Node 3
Load Balancer
Choosing Data Center

35. Infrastructure Mountain
Application

36. Downtime

37. On Premises
Hardware failures UpdatesDisasters

39. A clear leader in IaaS
Cost Effective High Performance Secure

40. Shared Database
Node 2
Shared storage
Node 1 Node 3
Load Balancer
Planning the Infrastructure

41. PostgreSQL ???
Java / Tomcat
NginX
Planning the Infrastructure

42. Shared Storage and Data Center
Shared StorageAttachments Profile Data

43. Our Business Requirements
Easy to Setup Cost Effective Easy to Maintain

44. Our Technical Requirements
Perform Disaster Recovery Secure

45. Investigating Shared Storage

46. NFS / EC2
Shared Storage on EC2
GlusterFS / EC2

47. Calculating True Cost
Licensing

48. NFS / EC2
Planning the Infrastructure
GlusterFS / EC2
Maintenance

49. Amazon Elastic File System (Amazon EFS)

50. Our Technical Requirements
Performance Disaster Recovery Secure

51. Our Technical Requirements
Instant Scale

52. Our Business Requirements
Easy to Setup Cost Effective Easy to Maintain

53. Amazon EFS

54. Testing EFS
Wrote Random Files
1KB – 1GB in Size
Read Files Simultaneously

55. JIRA Data Center Usage Pattern
Consistent Writes
Infrequent Reads

56. Results: Consistent Throughput
Throughput was consistent
across randomized writes and
frequent reads

57. Results: Consistent Capacity
As we increased overall reads
and writes, capacity stayed
within threshold

58. Amazon EFS

59. Moving to Production

60. Moving to Production
Region Availability Zones

63. Amazon EFS Amazon CloudWatch

64. Support and GetSupport
support.atlassian.com
getsupport.atlassian.comCustomer Requests

65. Results: Consistent Writes
JIRA Data Center was writing
files to the Elastic File System
consistently with no significant
dips in performance

66. Results: Consistent Reads
JIRA Data Center was able to
read from EFS, which provided
bursts of throughput on
request.

67. And We’re Growing!
0
5000
10000
15000
20000
Tickets Per Month
Tickets Per Month

68. Our Current Infrastructure
• Elastic Load Balancer
• Auto-Scaling Groups
• Amazon Elastic File System
• Amazon Relational Database Service

69. AWS Quick Starts
Automated deployment of Data
Center to Amazon Web Services,
built by Amazon architects
Announcing support for Data Center on AWS

70. 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

71. Remember to complete
your evaluations!

72. 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

73. Q&A
Amazon EFS

74. Thank you!