{"id":6618,"date":"2024-07-30T18:04:45","date_gmt":"2024-07-30T22:04:45","guid":{"rendered":"https:\/\/www.exchangedefender.com\/blog\/?p=6618"},"modified":"2024-07-30T18:08:51","modified_gmt":"2024-07-30T22:08:51","slug":"livearchive-cloud-considerations-it-works-everywhere","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2024\/07\/livearchive-cloud-considerations-it-works-everywhere\/","title":{"rendered":"LiveArchive Cloud Considerations: It Works Everywhere!"},"content":{"rendered":"\n
<\/div>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Over the past month we’ve been holding LiveArchive Workshop Series<\/a><\/strong> with clients who want to get LiveArchive deployed and staff trained in under 1 hour<\/strong>. It’s going well and the question we get the most is: “Will it work on Azure\/Linode\/Oracle\/___?<\/em>!” Yes, it works with ALL public and private clouds because it’s built on top of open source technology standards that everyone offers. In order to deploy LiveArchive <\/strong>you’d follow the same principles and steps outlined in our Cloud Backend Setup<\/strong><\/a> at Amazon AWS, Microsoft Azure, Oracle Cloud, Google Cloud (even if you host it yourself on your own network\/hardware<\/em>). All public clouds offer containerized services and the Docker containers that make up LiveArchive are mariadb:latest, minio\/minio:latest,<\/strong><\/em> and exchangedefender\/livearchive-webmail:latest<\/strong><\/em>.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\n
\"\"<\/a><\/figure>\n<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Navigating IT Politics <\/strong><\/h3>\n\n\n\n
<\/div>\n\n\n\n

Now that you know ExchangeDefender LiveArchive works on all the popular cloud providers, it’s time to pick one. Here are 3 things to keep in mind:<\/strong>

1) Your choice will typically be controlled by the clients existing infrastructure and vendor policies – if they are an all Microsoft shop you’ll likely be deploying LiveArchive on Microsoft Azure. Regardless of your choice of cloud vendor, you will still get the same LiveArchive performance and keep in mind that full source code for the entire stack is available here<\/strong>: https:\/\/github.com\/exchangedefender\/livearchive-webmail<\/a>. Having access to the code gives you the ability to optimize, customize, and future-proof your setup.

2) You will need access to DNS. <\/strong>In order to deploy LiveArchive you will need to create a CNAME for the LiveArchive UI which is required in order to request an SSL certificate.

3) You will need to allow several network policies <\/strong>on your choice of public or private cloud. Specifically, you will need to allow tcp ports 80\/443 for the web services and you will need to allow tcp ports 9000\/3306 to our LiveArchive network so that we can store your messages and message metadata. Cost is also an important criteria for many organizations so we recommend researching cloud cost calculators<\/a><\/strong>

This way you can see who will give you the best bang for the buck currently vs. over time as your organization grows. If you’re trying to keep the costs to a minimum<\/strong> your best option is going to keep minio and MariaDB services self-hosted or on semi-dedicated\/VPS\/colo deployment and to only put the LiveArchive Web UI in the cloud.

<\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n


We look forward to seeing you in our workshops, and keep in mind you can get it going in under 10 minutes just by following these steps<\/a>!
<\/strong>
<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[73,51,32,180],"class_list":["post-6618","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-backup","tag-email","tag-exchangedefender","tag-live-archive"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/6618","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=6618"}],"version-history":[{"count":18,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/6618\/revisions"}],"predecessor-version":[{"id":6641,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/6618\/revisions\/6641"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=6618"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=6618"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=6618"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}