In previous blog posts, we've discussed both the metrics to be mindful of during a catastrophic outage of an Atlassian application, and how to get started with snapshots of your applications in order to protect the[...]

Hopefully, after my last blog post, you've spent some time inquiring and thinking about what would happen if the server hosting your Atlassian applications were impacted by a disaster. Now, let's talk about how to[...]

Do you know where your Jira is hosted? Does it live on that computer under your IT guy's desk? Is it in your company's data center? Is it hosted in a public cloud like Amazon Web Services (AWS)?

It's something many[...]

If you want to run your own Synchrony cluster for Confluence Data Center or you are running in a version that does not provide the "Managed by Confluence" option and still automating the creation / spin up process.

Anybody who has implemented Confluence Data Center 6.0 through 6.11 likely knows that Atlassian has made huge strides in how Synchrony is deployed. But none of those strides have been as awesome as the change introduced[...]

We've been on-boarding more Technical Consultants lately and we've been improving how we introduce them to our technology stack. We had a need to have a learning environment for two technologies:

I love watching baseball. It's relaxing, it makes sense (most of the time) and the teams that win are usually talented and resourceful.

We here at Isos are big fans of Ansible and HashiCorp Packer. We use these tools (among others) to build pipelines that create custom images (including AMIs) for many of our Data Center implementations. During this[...]

In previous blogs I've mentioned how much we love Ansible here at Isos. One of the ways we develop and use our internal roles is via a Vagrant Multi-Machine setup. This multi-machine setup allows us to spin up multiple [...]

During AWS implementations we've always used an Elastic Load Balancer (ELB) in the public subnets in order to route traffic to the application instances in the private subnet. NGINX lived on the application instances.[...]