Operations | Monitoring | ITSM | DevOps | Cloud

I recently had a cloud migration client who was at the beginning stage of their discovery phase and looking to jump straight to “which database platforms should I be using in the cloud?” - a tall ask you might say, but following the three steps below they were able to discover and analyze all of their database servers in just two weeks.

If you are not familiar with CloudFormation, an easy way to define it is AWS CloudFormation is an AWS service that uses template files to automate the setup of resources. It can also be described as an infrastructure automation or Infrastructure-as-Code (IaC) tool. You can use CloudFormation to automate the configuration of workloads that run on the most popular AWS services, including their managed Kubernetes offering, the Elastic Kubernetes Service, or EKS.

The majority of engineers know that a minor misconfiguration might lead to some big troubles. Usually, we tend to forget the importance of that tense when we are configuring a new tool or a new service, as our focus is initially to make the tool functional and to evaluate if it fits our needs. Mattermost Cloud hosts thousands of workspaces which each one needs to have a different database backend, as in Mattermost we think that isolation is one very important aspect in our security guidelines.