Myappsoftware Logo Myapp Software
Generic selectors
Exact matches only
Search in title
Search in content

SAP in the cloud

SAP in the cloud

Implementation of SAP solutions

MyappSoftware combines years of SAP load experience to create integrated solutions that run on AWS for our customers. Our AWS certified team are experts in automating SAP load deployments, as well as managing legacy datacenter or on-premises enterprise migrations.

When our client uses SAP and seeks to eliminate the complexities of managing and scaling their solutions in their company or to accelerate and automate the implementations of their business applications in AWS, we must ensure that our client chooses the best SAP licensing options and Network services, security, storage, monitoring and administration of SAP systems on AWS.

As one of the best practices, MyappSoftware has focused on providing solutions to clients based on the SAP workloads in which we have experience, seeking the best conditions.

SAP solutions we support

  • SAP S / 4 HANA
  • SAP NetWeaver
  • SAP Business One, SAP HANA version
  • SAP Business One, SAP Microsoft SQL version
  • SAP Business One, SAP PostgreSQL version
  • SAP Business One, version SAP Oracle

Operating Systems

  • Microsoft Windows Server
  • SUSE Linux
  • SUSE Linux Enterprise Server (SLES)
  • RedHat Enterprise Linux (RHEL)

SAP licensing

For the proper use of SAP licenses take into account which scheme is the best suited to the needs of customers, always thinking of causing savings and supporting the customer's investment.

Quick guides to implement SAP

Here are quick guides to SAP implementation of AWS best practices.

Implementation of a SAP HANA environment - SAP S / 4HANA

This is an example of how to implement and configure SAP in your AWS account

  • An architecture with high availability that encompasses two availability zones
  • A VPC configured with public and private subnets in accordance with AWS best practices. This provides the network infrastructure for the deployment.
  • On public subnets, network address translation (NAT) managed gateways to allow outgoing Internet access to SAP instances on private subnets.
  • Optional resources implemented in public subnets:
    • On public subnets, an optional Linux bastion host in an Auto Scaling group to allow Secure Shell (SSH) inbound access to Amazon Elastic Compute Cloud (Amazon EC2) instances on private subnets.
    • An optional Remote Desktop Protocol (RDP) Windows Server that hosts SAP GUI and third-party front-end applications to manage SAP systems on private subnets.
  • Resources implemented in the private subnet:
    • Multiple Amazon EC2 instances to host the HANA and S / 4HANA ASCS database, PAS and an optional AAS. For standard and distributed installation options, see the implementation guide.
    • / Sapmnt directory, created on a Network File System (NFS) or Amazon Elastic File System (Amazon EFS) to share SAP files among all S / 4HANA instances.
    • For multi-node HANA database deployment, an NFS mounted in / usr / sap directory to share files between all nodes on the HANA database server.
    • An optional automated installation of SAP S / 4HANA and SAP HANA.
  • An Identity and Access Management (IAM) role to access the necessary AWS services through deployment processes.
  • Three security groups for restricted inbound access from the optional bastion host, between database instances, and for application access to the database.
  • AWS command line interface (AWS CLI) and an instance role to access the Amazon Simple Storage Service (Amazon S3) bucket installation software.
  • An exclusive Amazon Route 53 private hosted zone to host the HANA database and S / 4HANA server names.

This example supports the SUSE Linux Enterprise Server (SLES) operating system for SAP S / 4HANA instances. SAP HANA is supported with a choice of Linux operating systems: (SLES, SLES for SAP, or Red Hat Enterprise Linux (RHEL).

AWS solutions to consider

Taking these workloads into account, we will keep a strict control of solutions, as well as the different control mechanisms that have:

  • Patching vulnerabilities
  • Streamline problem detection
  • User friendly automation
  • Improve visibility and control
  • Manage hybrid environments
  • Maintain security and compliance

For the implementation of SAP solutions, take into account the following AWS services that will give us the option of being able to migrate SAP workloads, using the best practices of AWS.

  • AWS System Manager
  • Amazon EC2
  • Amazon Simple Storage Services (S3)
  • Amazon RDS
  • AWS Lambda
  • AWS Database Migration Service
  • Amazon WorkSpaces
  • AWS License Manager
  • AWS Directory Service
  • Amazon EFS
  • Amazon Route 53

AWS System Manager

It gives us visibility and control over the infrastructure on AWS, provides us with a unified user interface so that we can view operational data from various AWS services, and allows us to automate operational tasks across all AWS resources. With System Manager we can group the resources of each application, for example Amazon EC2 instances, Amazon S3 buckets or Amazon RDS instances, view operational data for monitoring and troubleshooting, and act on resource groups. System Manager simplifies application and resource management, speeds detection and resolution of operational problems, and makes it easy to use and manage infrastructure safely at scale.

All other AWS services described in the list must be considered according to the type of workload that will be migrated or lifted in AWS infrastructure.

Deliverables to the customer

  • Delivery CheckList Document SAP section


Case Studies


The American School of Tegucigalpa




Get Solution

Call us at

Guatemala: +502 22143200
Mexico: +55 8114-1300

or leave us your information here

AWS competition

AI & Machine learning


Business connectivity

Managed services

Apps in the cloud

Data engineering

Cloud adoption


Other Solutions


I'm interested


I'm interested


I'm interested