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

What AWS architecture for Jira & Confluence using SSL

M Amine
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 19, 2018


We are planning to deploy Jira, Confluence and Crowd (server, not Data Center) on AWS. 

Jira and Confluence have to use SSL. So we are faced with two options:

  1. Option 1:
    1.  Deploy a reverse proxy (like nginx for eg.) on an EC2 instance on a public subnet 
    2. + Configure nginx to use SSL (according to Atlassian documentation)
    3. + Add a NAT Gateway in order to connect the public subnet to the private subnet
    4. + Use Jira, Crowd & Confluence and Database (RDS) on a private subnet 
  2. Option 2:
    1. Use a NAT GATEWAY on a public subnet 
    2. + Use Jira, Crowd & Confluence on a private subnet and configure Jira, Crowd & Confluence to use SSL

Cann't really say what is the best option. 

Any thoughts? Share your experience :)

kind regards



Log in or Sign up to comment