Analyzing your IT-Infrastructure

Taking an analytical look at your IT-Infrastructure - with AWS' Optimization and Licensing Assessment

Taking an analytical look at your IT-Infrastructure - with AWS' Optimization and Licensing Assessment

In a three-part blog series, we described (late 2022) how we leverage the AWS Optimization and Licensing (OLA) approach. Today, based on a customer example, we will show how an OLA works in real life and what results one can expect when performing an OLA.

In October 2022, working together with a German company that operates throughout Europe, we had the opportunity to perform a fascinating assessment. Work began in earnest immediately after a kick-off call in which the infrastructure analysis procedure was presented and discussed with the customer. In our case, it was decided that the analytics tool "Cloudamize“ would be used to perform the analysis. In addition to delivering server performance numbers, this tool is also able to identify dependencies between them.

Which Analysis Tool is the Right One?

In our role as an AWS-partner, SPIRIT/21 supports various methods of data collection as part of the OLA. The two available tools - Migration Evaluator and Cloudamize - offer their own unique advantages. If you are interested in learning which tool best suits your requirements, we'd be happy to organize a joint OLA-Kick-Off-Meeting for you.

How is the Data Evaluation Performed?

The installation and configuration of “Cloudamize” were quickly completed. The performance data from the customer's server landscape could begin to be collected. Four weeks later, the evaluation of the results could begin.

Using the analysis-tool, the Cloudamize team produced a standard evaluation that served as the basis for additional individual analyses. For SPIRIT/21, it is important to present not only the standard-report, but also to reflect the results in terms of the customer's specific interests and circumstances. Questions regarding the collected data are an important source for better understanding the customer's needs and topics of interest.

Hints about the customer's current Microsoft-Licensing also proved very helpful. With this additional information in our pocket, we were able to finalize and present the overall results.

The presentation consisted of three parts:

1.) Calculation of the costs of the environment running on AWS;

2.) Optimization of the utilized services; and

3.) An optimized cost calculation with concrete proposals for how costs could be further optimized.

What Results Were Attained?

When reviewing the standard Cloudamize scenarios, it was immediately apparent that most of the cloud costs arose were storage related. Due to the information provided by the customer, we knew that there was a desire and interest in changing the underlying technology.

Knowing that most of the cost was associated with the backup infrastructure, we began by considering various cloud-optimized AWS-Backup options. When simulating the use of S3 with different storage-classes (e.g. Infrequent-Access, Glacier Deep Archive), we calculated that the backup-costs could be reduced by up to 60 %.

Listing the AWS services, that were to be deployed which the standard or optimized calculation:

Cloudamize Standard Calculation with EC2-instances

(Existing backup scenario, using right-sizing)

  • 1x r5b.12xlarge (1 year No Upfront Reservation)
  • GP3 EBS: 583 TB
  • Network traffic

Optimized SPIRIT/21 Calculation

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

  • 2x r5b.12xlarge (1 year reservation with monthly payment)
  • 400 TB S3 Standard
  • 50 TB S3 Infrequent Access
  • 128 TB S3 Glacier Deep Archive
  • 5 TB EBS GP3 (Buffer)
  • Network traffic (4,000 US$/year)

Solutions such as Amazon FSx for Windows File Server, Amazon RDS for MS SQL, Amazon WorkSpaces and AWS elastic Disaster Recovery were also taken into consideration.

This meant that in addition to the raw calculation and the associated right-sizing benefits, we could also present the customer with various modernization options. These are particularly important with respect to cost, usage and business value when designing a maximally efficient cloud migration.

What Happens After the OLA?

In order to continue supporting our customer on their journey to the cloud, our consultants are accompanying their transformation to a hybrid-cloud environment with a customer-specific cloud strategy.

The result? It is planned to implement the developed options for modernization during the migration to AWS.

An OLA can be an excellent starting point for your individual journey to the cloud. It will be financially covered by AWS - no costs arise for you throughout this process. If you would also like to profit from this offer, contact us here to arrange your personal OLA-Kick-Off meeting.

Mario Krämer, Projekt Manager | Public Cloud

mkraemer@spirit21.com

Wir nutzen sogenannte Cookies, um Daten darüber zu bekommen, wie und mit welchen Endgeräten unsere Seiten besucht werden. Das hilft uns sehr dabei, die Seiten noch interessanter und bedienungsfreundlicher zu machen. Dabei berücksichtigen wir natürlich Ihre Präferenzen und schalten das SPIRIT/21-Analytics nur dann scharf, wenn Sie durch einen Klick auf „Cookies akzeptieren“ Ihr Einverständnis geben. Sie können Ihre Einwilligung jederzeit mit Wirkung für die Zukunft widerrufen. Weitere Informationen finden Sie unter Cookie Einstellungen und in unserer