Four Key Things to Consider When Deploying Atlassian Data Center on AWS

November 15, 2019 | by Anjana Ramesh | Posted In Agile, Atlassian, Cloud

Things to Consider When Deploying Atlassian Data Center on AWS

Atlassian recommends Data Center for its large enterprise customers whose teams grow by leaps and bounds in order to benefit from greater scalability, better performance, and disaster recovery. You can either deploy Atlassian Data Center products in your existing hardware setup and configure it optimally or opt for a third-party cloud environment such as AWS or Microsoft Azure to cut down on the cost while maintaining control over your data.

Though hosting Atlassian Data Center on AWS is unarguably beneficial in a lot of aspects, the migration process is complex and demands a demonstrated expertise to pull it off. In this blog, we discuss some of the key things to consider for a successful AWS migration.

The scope and depth of the AWS platform

Before embarking on the AWS migration journey, you need to consider a myriad of factors to gauge if the default settings will be the best option for your deployment or you should customize it to fit your technical needs. AWS released 1957 new services and features as of 2018 particularly in areas such as Machine Learning and Artificial Intelligence, Internet of Things (IoT), and Serverless Computing.

The various combinations of these services and features throw a gamut of choices before you during implementation, which adds up to the complexity of the migration process. However, choosing the right set of services is imperative to make a seamless shift to AWS cloud.

Data security and compliance

While AWS is responsible for the security of the cloud infrastructure, the onus for the security of your data is on you. Essentially, running applications and services in cloud environments entails shared responsibilities for data security and compliance.

It is therefore critical to understand and document which security tasks are handled by the cloud provider and which tasks need to be handled by you. This should also be in line with any compliance requirements applicable to your industry.

Importance of getting various stakeholders on board

Deploying your Data Center products on AWS can be a full-fledged project that calls for defined roles and responsibilities across teams. It is important to align all key stakeholders who are likely to be impacted as a result of the migration and enroll them as a part of the process to ensure task completion and resolution of cross-functional issues.

User identity and access management

Most enterprises retain their identity management services and data sources within their premises, despite moving the other services to the cloud. This means there needs to be a bi-directional syncing mechanism between the on-premise identity system and the applications outside of the organization’s network that need the identity information of the users to grant access.

AWS offers different options like using federated single sign-on (SSO) and multi-factor authentication to handle identity and access management. Nevertheless, before taking the plunge, you need to understand the journey thoroughly.

Based on your team’s level of expertise, your migration complexity, and timeline, you may need to opt for a qualified managed service provider to seamlessly deploy, manage and provide maintenance for your Atlassian Data Center products on AWS. You might especially need an expert migration partner if you have limited internal resources to assist with project management, planning, and execution or have a complex migration scenario involving a large number of Atlassian users. Many organizations also tend to rely on the expertise of a managed service provider when they have specific compliance and security requirements.

To learn more about how to make the most of your Atlassian Data Center on AWS, download our white paper here.

This blog is Part 2 of a three-part series. Check out Part 1 here and Part 3 here.

To learn more and get started, contact us.