IT infrastructure cleverly analysed

In a three-part blog post series late last year, we described how we approach an AWS Optimization and Licensing Assessment (OLA). Today, we present a customer example of how an OLA works in practice and what results can be expected.

Which tool is right for analyzing IT infrastructure?

In October 2022, we were able to carry out an exciting assessment with a European-wide company from Germany. The starting signal was given immediately after the kick-off call, in which we presented the process of the infrastructure analysis and discussed it with the customer. In our case study, it was decided to use the analytics tool “Cloudamize”, as this tool can not only display the performance data of the servers but also their interdependencies.

As an AWS partner, SPIRIT/21 supports different methods of data collection within the framework of the OLAs. Both possible tools - the Migration Evaluator and Cloudamize - offer different advantages. We will be happy to discuss with you which tool best suits your needs in a OLA-Kick-Off-Termin.

Analysis of the IT infrastructure: How does the data analysis work?

The installation and configuration of “Cloudamize” was done quickly. Now the performance data could be collected from the client’s server landscape. After four weeks, the evaluation was carried out.

The Cloudamize team provided a standard analysis that served as a basis for further individual analysis. At SPIRIT/21, we attach great importance not only to present the standard report as a result, but also to take into account the specific interests and circumstances. Inquiries about the collected data were an important source for us to gain further information about the customer’s needs and focus topics. Notes on the current Microsoft licensing were also helpful. With this additional information in hand, the presentation of the results was finalized and presented.

Presentation of the results of the IT infrastructure analysis was divided into three parts:

1. Costing of the environment on AWS,
2. Optimisation of the services used and
3. Optimised cost calculation with concrete suggestions for improvement.

Result of the analysis of the IT infrastructure with an OLA

Looking at the standard scenarios in Cloudamize, it was immediately obvious that the bulk of the costs in the cloud are caused by storage. From the information we received from the customer, we knew that there was a need and interest in a technological change. Thus, we looked at different cloud-optimized scenarios, especially for the backup systems, which accounted for most of the storage cost
We focused particularly on using various AWS backup options. By using S3 with various storage classes (including infrequent access, Glacier Deep Archive), we were able to reduce the calculated backup costs by around 60%.

Here is a list of the AWS services that were used for standard and optimized costing:

Cloudamize standard calculation with EC2 instances

(Existing backup scenario as 1:1 migration taking into account right-sizing)

• 1 EC2 instance r5b.12xlarge (1-year reservation with monthly billing)
• Storage GP3 EBS: 583 TB
• data traffic

Optimised SPIRIT/21 calculation

(with high-availability for the backup server and cheaper storage options)

• 2 EC2 instances r5b.12xlarge (1-year reservation with monthly billing)
• 400 TB S3 Standard
• 50 TB S3 Infrequent Access
• 128 TB S3 Glacier Deep Archive
• 5 TB EBS GP3 (buffer)
• Data traffic (USD 4,000 / year)

We also included solutions such as Amazon FSx for Windows File Server, Amazon RDS for MS SQL, Amazon WorkSpaces and AWS Elastic Disaster Recovery.

In addition to the actual costing and the associated right-sizing advantages, we were also able to present the customer with various options for modernization. These are particularly important in order to design Migration to the cloud as efficiently and sustainably as possible in terms of costs, usage and business value.