We recently ran the “Is Your Organization Atlassian Cloud Ready” webinar. In this webinar we compare and contrast Atlassian Cloud vs. Server—covering considerations like deployment, security and privacy compliance.
We also reviewed the reasons why a migration to Atlassian Cloud would be beneficial, such as: cost and resource savings on physical hardware storage and maintenance, automatic updates, remote access, rigorous security protocols, and instant elastic scalability.
If you didn’t get a chance to watch this important webinar, you can watch it on demand now.
Today, we’re going to recap the question and answer chat from the webinar and include resources to where you can learn more about these topics.
Q: What level of support is included in the Premium subscription?
Premium support differs from the standard support package in two ways. Firstly, it has increased hours of availability. For L1 issues, or the most critical, you get 24/7 support. For L2 issues, or a less critical issue, you get 24 hour support 5 days a week. For standard support, all levels of issues have access to support 9 hours a day, 5 days a week.
The second way it differs is in their initial response time. Again, there is no guaranteed initial response time on standard support, but for Premium support, L1 issues will receive a response within one hour. L2 issues will receive a response within two hours. Find more information on this topic here.
Q. Can you give an example of how the functionality is different on Bitbucket Cloud?
While Atlassian is continually working to get feature parity between the two versions, they’re not there yet. For example, Bitbucket Cloud has a feature called Pipelines, which will allow you to do CI/CD within the app without having to use external build tools like Bamboo or Jenkins. On Bitbucket Server, you will still need to rely on these tools.
However, Bitbucket Server has a feature called “Code Insights.” This is used during Pull Requests to help you identify trends in the code, so you and your teams can know what to zero in on during Code Reviews.
I should note here that Atlassian does not recommend you migrate from Bitbucket Server to Cloud at this time. However, if you would like more information on this migration, you can find it here.
Q: Can I integrate my existing LDAP to Jira Cloud?
Yes, this is entirely possible using Atlassian Access. With Access, you can integrate with Cloud Directory providers such as AzureAD, Okta, Google Cloud Identity, and more! As a bonus, you can also use Access to sync users and groups from these providers to your Cloud instances, meaning you can manage your permissions from one place!
Q: In the past, Atlassian had a really small amount of storage for Cloud. Has that increased now?
While it is true that storage on Atlassian cloud started out small, that’s no longer the case. Now for standard Atlassian Cloud subscriptions, you get 250 GB per application. This is ten times more than when Atlassian Cloud launched! Furthermore, if you have a Premium subscription, you have unlimited storage! That definitely sounds like a reason to consider a Premium subscription.
Q: I know this isn’t Cloud related, but is there some way to make the due date for my licenses the same each year?
A: Yes, there is! This is a concept known as “Co-Termination”, or co-terming for short. Coyote Creek can not only help you co-term your licenses, but when working with us to acquire new licenses, we can make sure to co-term your new purchases to your existing licenses!
Q: Does Atlassian Cloud have service level agreements?
While the free and standard subscriptions tiers do not have a Service Level Agreement (SLA), your Cloud Premium subscription does! With a premium subscription, you can expect 99.9% Uptime. You’d be hard-pressed to match that even with JIRA Server!
Q: We wrote some plugins for Jira that integrate with our internal systems. Will those run in the Cloud?
Unfortunately, they will not. Atlassian’s Cloud products have a very different architecture to their Server and Data Center products. In order to run these plugins, you will have to rewrite them to work with the Atlassian Connect framework, then host a server somewhere on the Cloud (i.e. AWS) to run the application and integrate with Atlassian Cloud.
Q: Can I have more than one Jira instance in the Cloud?
Yes, you can! However, you will need to pay a subscription fee for each JIRA instance you have in the Cloud. However, the great news here is your Site Administrator can manage all of the instances from one place!
Q: Can I integrate JIRA Cloud with my Bitbucket Server Instance?
You absolutely can, but you will have to do your homework first. The first thing you’ll need to do is make sure your Bitbucket Server instance is good to go. This means confirming that it’s Base URL is set correctly, that it has a URL that satisfies the RFC 1738 URL Standards, and that it is setup to use a valid SSL Certificate.
Additionally, you will need to make sure that the Atlassian Cloud IP Range can reach the ports specified in the Compare Atlassian Cloud vs Server Page. This is absolutely a requirement as JIRA Cloud will need to be able to check your Bitbucket Server regularly to keep the information in sync. That means you’ll need to work with your Network Engineers to make sure your firewall is set up correctly. However, once done, the integration works perfectly!
Q: Is Atlassian Cloud FedRAMP Certified?
For some context here, FedRAMP, or the “Federal Risk and Authorization Management Program”, is how the government standardizes what cloud apps it sees as okay to use and which it does not allow use of.
As of February 12, 2020, Atlassian Cloud is not on the FedRAMP list, which means government agencies (and certain contractors) would not be able to use this product.
You can find out more here.
If you have more questions about Atlassian Cloud or would like us to assist you in evaluating whether or not a Cloud migration would suit your organization, please reach out today.
At Coyote Creek as an Atlassian Platinum Solution Partner, we know it’s the human connection that makes the difference in all that we do.