I have been working on a project of migrating Atlassian suites (Confluence/Jira/...) to AWS. This is not a simple lift and shift migration. We actually redesigned everything from ground up. Here is the CICD that I designed. The source codes are stored in on-premise BitBucket, the build tools is AWS Dev Tools (mainly CodeBuild). Development … Continue reading CICD Design for Atlassian Suites in AWS
When building Confluence Data Center on AWS, I was wondering how Confluence Data Centre manages the index file. As we run Confluence cluster in auto-scaling group, the Confluence nodes come and go (not that frequent though, as Confluence is not good at dynamic scaling. It is more schedule based scaling). The newly launched instance gets … Continue reading How Confluence Data Center Manage the Index File?
Stateful Set in Kubernetes is specifically designed for stateful application, and it works well with Confluence Data Center. This is how I designed to run Confluence Data Center on Kubernetes (AWS EKS). And here is a quick demo of scaling up and down.
Based on the Atlassian quick start of Confluence Data Center on AWS, I have made my own version of it. Here are a few customisations that I have introduced. Customisation One: Remove public subnets. To meet the security compliances, we can not use public subnets. All ingress/ egress traffics should go through central managed reverse/ … Continue reading Customised Quick Start of Confluence Data Center on AWS
I have been working on the Confluence space archiving project recently. Here is my design which is already in production. And it works like a charm 🙂 I will explain a bit deeper into the two major automations: Confluence Online Archiving Automation The Online archiving does 3 things: Set the space status to Archive. This … Continue reading Confluence Auto Archive Solution
If your synchrony cluster failed to start in AWS, the Collaborative Edit in Confluence will not work. And if your environment meet all the following criteria. Then I think you are in the right place. As I had the same issue, and finally figured it out that Synchrony has seperate JVM settings. The proxy settings … Continue reading Synchrony cluster failed to start with outbound proxy in AWS
The major reason that I replaced Flannel with Weave Net as the Kubernetes CNI is that Flannel does not support multicast. I did not realize it until my test Confluence DC cluster became dysfunctional. There are two Confluence nodes in the Confluence DC cluster. Each one is a pod, they are working fine when they … Continue reading Replace Flannel with Weave Net in Kubernetes