Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to Upgrade Jira Data Center on AWS

Hi Team,


We are using AWS Quick Start ( to run our own Jira SM setup in AWS.

Now that we want to upgrade the Jira SM version to 4.22.1 from 4.13.4, cloudformation update stack is failing VPSStack as the Export from VPCStack is being used by another stack.

Embedded stack arn:aws:cloudformation:eu-west-2:*********:stack/atlassian-sandbox-jira-service-management-VPCStack-****/*********************** was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: Export JSM-SBX-BastionPrivIp cannot be updated as it is in use by atlassian-sandbox-jira-service-management-JiraDCStack-***********

I tried removing that direct export and used a workaround with parameters but no luck so far. I highly appreciate any help to unblock me here


Thanks in advance


3 answers

0 votes


Please do scaling directly via the autoscaling group:

AWS console -> ec2 -> Auto scaling -> Auto scaling groups -> your stack ASG -> edit desired min and max capacity to the needed number.

This is depressing seeing this coming from someone in the Atlassian team. You've probably snatched this info from:

However, that suggestion contradicts other documentation:

It's not a working workaround if you need to make ANY changes to the stack. So we need to be able to make those changes in the stack without this error, especially for upgrades.

I have exactly the same problem with 1 out of 3 of our environments

Export ATL-Jira-DevBastionPrivIp cannot be updated as it is in use by Jira-Dev-JiraDCStack

It's a complete blocker, and a bug, yet nobody seems to be taking it seriously.

Look at the instructions for upgrading on the AWS Stacks:,current%20template%20and%20click%20Next.

It leaves us dead in the water, this needs an urgent fix.

Like Arthur likes this
Arthur Rising Star Dec 21, 2022

It really is a shame that atlassian doesn't have a fix for this critical bug. It also occurs for confluence stacks.

Hi Harish,

i did run in the same Problem.

Any solution found?



Hi Harish,

Did you resolve this?

If so, how?

I just ran into a similar problem when performing the Atlassian Performance testing, where I need to scale up from 1 to 2 nodes in the data center cluster.

My error:

Embedded stack arn:aws:cloudformation:eu-central-1:948378585301:stack/Jira-DM-PerfTest-Enterprice-2022-T1-VPCStack-1P8O7SLFYNF4I/c07c2e90-f070-11ec-a074-06c427dcdb5c was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: Export ATL-BastionPrivIp cannot be updated as it is in use by Jira-DM-PerfTest-Enterprice-2022-T1-JiraDCStack-D439FRHDRKPJ



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events