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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,552,691
Community Members
 
Community Events
184
Community Groups

Jira/Confluence deployment Automation on AWS

We are considering to upgrade our Collaboration Tools to new AWS Quick Start templates versions and we found cloud formation parameters of the stack DeploymentAutomation* very promising.

Unfortunately it's not clear from available documentation how properly to use the parameters. Has anybody managed to make them work?

Specifically:

1. How to specify custom DeploymentAutomationRepository? As soon as one of parameters is DeploymentAutomationKeyName I think it is ssh url to the repo.

2. How properly create DeploymentAutomationKeyName in SSM parameter store? As a string or (as I'd expect) as a Secret.

My deployment fails and I see the key rendered in right place but without new lines.

Could any body advise on it?

1 comment

1. it is ssh url

2. securestring

template doesn't handle ssm parameter properly, will try to find time to submit to developers

Comment

Log in or Sign up to comment