Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to shutdown nodes in AWS Jira Data Center

I am using AWS Jira Data Center with the default configuration from the CloudFormation stack template. This has one node.

I am using this for testing only. I'd like to shut it down when not in use.

When I shut down the EC2 host for the Jira node, the auto scaling group automatically restarts it.

I've tried detaching it and also changing the min number of nodes in cluster from 1 to 0, but neither work.

Any ideas?



1 answer

0 votes

An Amazon EC2 Auto Scaling (AS) configuration has three relevant settings to manage capacity:

  1. minimum size - AS ensures your group never goes below this size
  2. maximum size - AS ensures your group never goes above this size
  3. desired capacity - AS ensures that your group has this many instances (either because you manually set the value, or in case you have defined scaling policies, AS adjusts the desired capacity "within your minimum and maximum number of instances, based on the criteria that you specify")


The aws-quickstart/quickstart-atlassian-jira/.../quickstart-jira-dc.template.yaml CloudFormation template does not expose the desired capacity and has a default minimum and maximum size of 1, resulting in:

  • detaching an instance does not alter the Auto Scaling group configuration, which is why AS starts a new instance when you cause it to be below its minimum size of 1
  • terminating an instance has the same effect, causing AS to start a new instance to reach its minimum size of 1
  • changing the minimum size to 0 does not automatically change the desired capacity, if there are no resp. scaling policies configured


You can easily achieve the desired outcome by setting both minimum and maximum size to 0, which will cause AWS to automatically reduce the desired capacity to 0 and terminate the instance.

Alternatively you can only set the minimum size to 0 and manually set the desired capacity of the Auto Scaling group to 0 as well (via the AWS console or AWS CLI).


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Data Center

Architect your Atlassian Data Center Application (Jira, Confluence, Bitbucket) in Azure

Hello folks! To the member of organizations who are still running their Atlassian applications on the server, we are on the side of the bridge, and if we need to sail the boat with confidence either...

306 views 0 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you