← Back to list

Elaboration of Executive Presentation of Infrastructure costs for an SAP Migration project from…

In this project based on a real-world scenario, I acted as a Cloud Architect and created an executive presentation of infrastructure costs…

Brian Leding · 2023-12-21 23:42 · 1 claps · 2.4 min read
#aws #aws-pricing-calculator #aws-ec2 #aws-rds #aws-support-services
Open on Medium ↗
Wiki topics: ☁️ · DevOps & Cloud 🏛️ · Architecture 📊 · Economic Policy

Elaboration of Executive Presentation of Infrastructure costs for an SAP Migration project from On-Premises to AWS

In this project based on a real-world scenario, I acted as a Cloud Architect and created an executive presentation of infrastructure costs for a SAP migration project from On-Premises to AWS.

Tools Used to Create the Estimate and the Presentation

Tools Used to Create the Estimate and the Presentation

My mission was to estimate the costs of migration to AWS. To do this, I needed to gather the necessary pieces of information to be able to create the most accurate estimate. Each component of the customer’s infrastructure had to be considered. What were the components of the current on premises infrastructure? How was this infrastructure organized? What kind of support did the customer need? How long did they need to realize cost savings? The number of servers, the applications, the database storage, and the network requirements were all pieces of those questions.

As it turned out, there were three basic segments to their environment. The production, staging, and development organizations each needed applications servers, and database storage. Each segment had different infrastructure requirements as shown in the diagram below.

Criteria Gathered to Create the Estimate

Criteria Gathered to Create the Estimate

The AWS Pricing Calculator allowed me the flexibility to enter each item individually with the respective requirements. For example for the production environment, they needed five servers each running eight CPUs and sixteen GB RAM with two TB of block storage. On the other hand the staging environment only needed three servers each running four CPUs and eight GB RAM with one TB of block storage. I added each segment into estimate for three year term including the EC2 instances for the application servers, the AWS Elastic File Storage for the NFS reqirements, the Elastic Load Balancers, the RDS Storage of Oracle, and the Enterprise Support Plan for the highest level of support. Once all the data was entered, I could see the estimated costs both monthly and annually to the customer.

AWS Pricing Calculator

AWS Pricing Calculator

From here I exported the data into a .csv file and then using Microsoft Power Point, I created a presentation to illustrate the estimate with monthly and annual costs to the customer as shown below.

Exported .csv file loaded nto Microsoft Excel

Exported .csv file loaded nto Microsoft Excel

Cover Sheet

Cover Sheet

Monthly Costs

Monthly Costs

Annual Costs

Annual Costs

After the customer accepted my proposal, I begin the planning stages of the migration, executed the migration, and saved the customer money.


메타데이터
post_id
f3dbbb3a6589
slug
elaboration-of-executive-presentation-of-infrastructure-costs-for-an-sap-migration-project-from-f3dbbb3a6589
url
https://medium.com/@brianleding/elaboration-of-executive-presentation-of-infrastructure-costs-for-an-sap-migration-project-from-f3dbbb3a6589
canonical_url
https://medium.com/@brianleding/elaboration-of-executive-presentation-of-infrastructure-costs-for-an-sap-migration-project-from-f3dbbb3a6589
author_url
https://medium.com/@brianleding
status
ok
fetched_at
2026-06-27 07:40:21