Cloud Native Applications in AWS supporting Hybrid Cloud – Part 1

Wednesday, 31 July, 2019

Let us talk first about what is cloud native and the benefits of SUSE Cloud Application Platform and AWS when building cloud native applications.

So, what is a cloud native app?

Usually people mistake a cloud native app with a 12 factor app and that is not correct. 12 factor is a set of good development best practices which should be in place when developing a distributed application involving many teams/vendors or that requires fast, agile development cycles.

How does that differ from developing a cloud native app? As the name implies, cloud native apps are applications built natively on a cloud platform. What exactly does that mean?

First let us talk about the requirements of a cloud native application:

  1. It needs to meet the target load, with a high SLA.
  2. It must adapt to variable loads. Load is not easily predictable as may happen when the application is available for public usage, similar to YouTube or Facebook.
  3. It may be a pay as you go, so it must be cost efficient.
  4. It must be responsive to changes in requirements and have a fast time to market.
  5. It must enable smooth integration with other apps, services, and APIs, with no restriction to enable digital transformation. Put simply, this is the ability to let different business contexts interact together and learn from each other and be highly responsive. If you want more details, you can read about the interview I did for digital transformation Digital Transformation: An Interview with Rania Mohamed (Global Services)
  6. Application development time must be extremely fast without impacting the quality.
  7. It must be highly integrated with the underlying cloud service, to enable native
  8. It must be portable, even though it is leveraging the underlying cloud service, it must allow the ability to be portable across different clouds.
  9. It supports and enables polyglot development languages and methods.

Now that we understand the CNA (Cloud Native App), let us discuss how is that related to MSA (Microservices Architecture).

MSA is an architecture design principle which mainly emphasizes breaking down the application/problem into smaller chunks which are loosely coupled from each other. Such chunks are called microservices. So simply think of a microservice as the smallest standalone service that can ever live independently by itself. Ok but what are the benefits of MSA and how is it linked to CNA?

MSA main benefits are:
  • Efficiency of scalability as just the required service can be scaled and not the whole application or service or module.
  • Enables a high SLA as now we have a set of microservices that can operate independently without impacting another microservice or app or service if it has downtime.
  • Improves development productivity as it enables and supports agile development.

So is MSA another technical term for CNA?

Simply, no. You may have MSA application which is not CNA, but it is very hard or I would even say impossible to have a CNA which is not designed as an MSA. Because MSA fully supports  CNA principles, it achieves some of the main important principles of CNA such as handling of variable load in a very cost efficient way as well as supporting increased development speed and productivity.

Here is the main question — how is SUSE Cloud Application Platform together with AWS help with CNA?

SUSE Cloud Application Platform is a cloud native application platform that offers application runtimes based on the application properties, defined using a buildpack. It enables the developer to really just focus on doing what he/she is best at, which is writing code. Let me put on the developer cap (which I am always honoured to put on and would never put it down) and explain the steps I go through if I am using SUSE Cloud Application Platform:

  1. I am a Java developer so I just focus on writing my Spring MSA and the APIs I consume and offer.
  2. I need a database so I write down in Maven and in the Spring initialization the required configurations for the supported database. I choose to support PostgreSQL and MySQL.
  3. I then create a manifest file which used by a buildpack and then I do the CF push, to push the application into SUSE Cloud Application Platform on AWS.
  4. Then I can provision the database using the SUSE Cloud Application Platform marketplace, which uses the AWS Service broker, to provision a service instance and then bind it to my application.
  5. Voila, I have my application ready to test in the cloud.

So as a developer, I really didn’t get into understanding the AWS cloud or even how to set up a database. I just focus on writing code and my application needs and the platform takes care of the rest.

Now if my application wants to integrate with AWS SQS, all I need to do is to define such dependency and let the service broker together with SUSE Cloud Application Platform handle the load and the binding of the service instances to my application instance.

So in simple terms, SUSE Cloud Application Platform enables native cloud application development as the it will be able to provision and manage a service instance in the cloud using the underlying cloud native language. How does that happen? The magic words are service broker, using the open service broker API.

By using SUSE Cloud Application Platform and AWS, services can be automatically provisioned based on the load on the app workload. Here is what happens during the development lifecycle of an MSA or an app:

  1. Developer decides on the pre-requisite for his/her app, for example the required services and runtime from the underlying CNA platform, regardless the target cloud platform.
  2. Developer chooses the technologies to be used in developing the application.
  3. He/she develops the app and uses CF push to push the application into SUSE Cloud Application Platform.
  4. SUSE Cloud Application Platform offers a marketplace and service catalog showing all the available cloud services based on the configured service broker(s). Think of the service broker as the link between the cloud(s) used by the platform and SUSE Cloud Application Platform. We can have as many service brokers as we want as long as they support Open Service Broker API standards. SUSE Cloud Application Platform highly enables and supports hybrid cloud native applications.
  5. The developer or the operator uses the CF CLI to provision the required services in AWS using the configured AWS Service broker. They can also use SUSE Cloud Application Platform’s Stratos UI to provision the instance and bind it to the pushed application instance.

The following picture depicts the marketplace embedded in Stratos which displays all services offered by the configured service brokers.

In my next post , I’ll discuss two ways to get SUSE Cloud Application Platform installed on AWS and configure the service broker:

An application a year to an application a week on AWS

Thursday, 20 June, 2019

At the recent SUSECON conference in Nashville, Ryan Niksch from AWS discussed how shifting the focus from writing code to deploying applications to production has become more critical as business agility tops the list of customer requirements. He then introduces the benefits of Cloud Foundry in general, and SUSE Cloud Application Platform specifically, including the AWS service broker; its benefits are that it is a containerized distribution of Cloud Foundry that can very quickly and easily be deployed to AWS using a Quick Start template.

SUSE has posted all recorded talks from SUSECON on YouTube. Check them out if you want to learn more about what SUSE has to offer. We’re not just Linux anymore! I’ll be posting more SUSE Cloud Application Platform talks here over the coming days. Watch Ryan’s talk below:

Visit SUSE at SAPPHIRE NOW 2019 and learn more about SUSE solutions for SAP on AWS

Tuesday, 7 May, 2019

Join SUSE and our partners in Booth #2246 at SAPPHIRE NOW 2019, where you can learn more about SUSE solutions for SAP running on Amazon Web Services (AWS) and more. You can download the full SUSE Session Catalog off the SUSE at SAP SAPPHIRE NOW landing page.

The following SUSE partners are presenting topics related to running SUSE solutions for SAP applications on the AWS Cloud in the SUSE Theater located in our booth (Booth #2246).

  • Tuesday, May 7th at 3:30 PM EDT |  SAP S/4 HANA: Whys and Hows  | Speaker: Darren Mitchell | Director, Managed Services Solutions/Innovations | Itelligence
  • Wednesday, May 8th at 11:00 AM EDT | Optimize Your Digital Transformation Journey – Learn how to Migrate to SAP HANA, or SAP S/4HANA on SUSE into the Cloud | Speaker: Patrick Osterhaus | Chief Technology Officer | Protera Technologies
  • Wednesday, May 8th at 11:30 AM EDT | SAP on AWS: Serving the Need of the Most Demanding SAP Customers | Speaker: Brian Griffin | SAP Cloud Architect | AWS
  • Wednesday, May 8th at 12:00 PM EDT | Accelerate S4 – Deploy a Fully Production-ready SAP S4 Environment in Hours | Speaker: Ben Lingwood | CTO | Lemongrass


Be sure to also check out SUSE’s and our partner’s sessions being presented at the AWS Booth Theater (Booth #2000). Full schedule and more, including other AWS sessions, are located on the AWS at SAPPHIRE NOW landing page.

  • Tuesday, May 7th at 11:30 AM EDT | Enhancing High Availability of SAP on AWS with SAP SUSE Cluster Connector | Speaker: Peter Schinagl | Senior Technical Architect | SUSE
  • Wednesday, May 8th at 2:30 PM EDT | L.B. Foster Use Case: SAP S/4HANA Migration to the AWS Cloud with 100% Project Success | Speaker: Patrick Osterhaus | Chief Technology Officer | Protera Technologies
  • Wednesday, May 8th at 4:00 PM EDT | SAP on AWS Enabled Innovation | Speaker: Eamonn O’Neill | Co-Founder and CEO Americas | Lemongrass
  • Thursday, May 9th at 1:00 PM EDT | SAP Subscription-Based Licensing for Life Sciences Firms | Speaker: Brian Everett| Industry Solution Principal, Life Sciences | Itelligence
  • Thursday, May 9th at 3:00 PM EDT | SAP to AWS – Insight from the Middle of a Migration | Speaker: Eamonn O’Neill | Co-Founder and CEO Americas | Lemongrass

SUSE Linux Enterprise Server for Arm 15 on AWS

Monday, 1 April, 2019

SUSE is excited to launch SUSE Linux Enterprise Server for Arm on AWS, backed by a Trial Subscription Program and also available via AWS Spot Instances to get started on your next innovation. Today’s innovators are testing new architecture designs to build products in increasingly more efficient, cost-effective, scalable, and secure ways. The Arm architecture is critical in this diverse ecosystem and its’ adoption by Amazon Web Services in November 2018 was a huge milestone for the market. While Arm is prevalent in the mobile market and the chip most likely powering the device in your pocket – the technology is also critical in powering IoT devices and applications in the machine learning space.

A1 Instances powered by the AWS Graviton Processor

Ever since AWS released the AWS Nitro System in 2017 – a combination of dedicated hardware and lightweight hypervisor, which maximizes resource efficiency while supporting familiar AWS and Amazon EC2 instance capabilities – the doors have been opened to increasing choice of EC2 instances. In November 2018, AWS launched the A1 instance – the first instance powered by the AWS-built Graviton processor – featuring 64-bit Arm Neoverse cores. These general-purpose instances are 40% less expensive than instances using the same number of vCPUs and DRAM and are currently available in the US East (N. Virginia and Ohio), US West (Oregon) and EU (Ireland) regions.

The Most Cost-Effective Enterprise Developer Experience for Arm-based Architecture on AWS

When we first released SUSE Linux Enterprise Server for Arm back in 2016 – we received many inquiries about exciting use cases. Take the Knorr-Bremse success story for example – they are a German manufacturer of rail and commercial vehicle components that employ over 27,000 workers around the world. Together – we helped “smarten” their factory floor with SUSE Linux Enterprise Server for Arm powering their monitoring systems for manufacturing operations – helping maintain uptime and improve production efficiency.

Now starting this week, you’ll be able to provision SUSE Linux Enterprise Server 15 for Arm AMIs directly within the EC2 console. To save further costs – available with SUSE Linux – you can also make Spot Instance requests which can drive costs even lower. Additionally, you can procure a 60-day trial subscription by going to the

page here and requesting a Trial Subscription Code to be registered on a BYOS system (found in the Community AMIs section of the EC2 console).

SUSE and AWS are excited to hear feedback, and work with our joint customers on innovation. Reach out to us at to let us know what you’re working on and the potential to receive proof-of-concept infrastructure credits for qualified projects.

About SUSE Linux Enterprise Server for Arm 15

SUSE Linux Enterprise Server for Arm is an enterprise-grade Linux distribution that is optimized for unique 64-bit Arm chip capabilities and now available on Amazon EC2 A1 instances. Learn more about SLES for Arm or you can register for your free trial subscription here.

About Amazon EC2 A1 Instances

Amazon EC2 A1 instances deliver significant cost savings and are ideally suited for scale-out and Arm-based workloads that are supported by the extensive Arm ecosystem. A1 instances are the first EC2 instances powered by AWS Graviton Processors that feature 64-bit Arm Neoverse cores and custom silicon designed by AWS. Learn more:

Meet the SUSE Public Cloud Experts at AWS re:Invent

Tuesday, 13 November, 2018

The month of November brings along the changing of leaves, the return of pumpkin spice, Thanksgiving with family and friends and colder temps.  However, fall isn’t the only thing in the air!

The 7th annual AWS re:Invent returns to Las Vegas, Nevada on November 26-30 and SUSE will be in attendance! Have a question you need answered? Schedule a meeting ahead of time:

What is AWS re:Invent?

AWS re:Invent, hosted by Amazon Web Services (AWS), is the largest gathering of the global cloud computing community, where customers learn more about the latest from AWS. The event features keynote announcements, training and certification opportunities, access to more than 2,000 technical content sessions, a partner expo, networking and social events, and so much more.  It is the ideal event for partners, developers and engineers, system administrators, systems architects, and technical decision makers.

Meet the SUSE Team There!

Attending AWS re:Invent and want to learn more about enterprise open source solutions for running SAP or Kubernetes-based containers on the AWS Cloud?  You’re in luck because these will be some of the topics our SUSE experts will cover and answer questions about in the SUSE booth (#1304) located in the Expo!

On Tuesday, November 27th from 5:10-5:30pm, join one of our partners, itelligence, for their theater session in the Expo and hear all about how SAP S/4HANA on AWS is accelerating the fight against cancer.  Exact Sciences (Exact), maker of ColoGuard, a noninvasive colon cancer screening test, partnered with itelligence to migrate to SAP S/4HANA on SUSE Linux Enterprise Server running on AWS while maintaining compliance controls consistent with HIPAA security and privacy rules. Please join the session to learn how SUSE is aiding in these efforts. Reserve your seat for session DEM86 Supporting an Early Cancer Detection Vision with SAP S/4HANA on AWS (requires AWS re:Invent registration) on Tuesday, November 27th, 5:10 PM – 5:30 PM, Kumo Theater, Expo Hall, Venetian Level 2.

And in true SUSE fashion, it wouldn’t be an event without some cool SUSE games and give-a-ways.  Swing by the SUSE booth (#1304) for a chance to pick up some cool SUSE swag. Not attending the event but want to learn more about the SUSE/AWS partnership? Check out .

SUSE Linux Enterprise Server for SAP Applications Available on AWS High Memory Instances

Tuesday, 23 October, 2018

Amazon Web Services (AWS) has released Amazon EC2 High Memory instances which are part of the Memory Optimized Instance Category. The new instances are purpose-built to run large in-memory workloads, including SAP HANA. The SUSE and Amazon engineering teams collaborated to ensure SUSE Linux Enterprise Server (SLES) and SUSE Linux Server for SAP Applications were supported on the day of the release in the Amazon Marketplace. Below are the new instance type vCPU, RAM and bandwidth specifications, as well a link with all the instance families available on the AWS platform:

Link to the entire Amazon Web Services Instance family.

New Instance Performance Perks

The new High Memory Instances have introduced quite a few innovations and improvements when compared to the previous Memory Optimized Instances: X1 and X1e that greatly improve high memory workloads such as SAP HANA. The improvements to the instances have resulted in a new benchmark of 480,600 SAP Application Performance Standard (SAPS) for the 6 TiB instance (u-6tb1) up from the previous best 131,500 SAPS for the x1e.32xlarge which has 3,904 GiB of RAM and 128 virtual cores.

Below are just a few improvements introduced with the new instance type.

  • Upgraded Processing: The EC2 High Memory instances are the first Amazon EC2 instances powered by an 8-socket platform with the latest generation Intel® Xeon® Platinum 8176M (Skylake) processors. The previous X1 and X1e High frequency Intel Xeon E7-8880 v3 (Haswell) processors. Previously the highest available vCPU count was 128, but now customers can deploy SUSE Linux enterprise Server and SUSE Linux Enterprise Server for SAP Applications on systems with 448 hyperthreaded cores (224 physical cores).
  • Increased Memory: Previously the highest memory available was 1,952 GiB in memory available on the x1.32xlarge instance. With the introduction of the new instances, customers can choose to run the 448 logical cores with 6TiB, 9 TiB or 12 TiB.
  • Elastic Block Storage (EBS) and Network Bandwidth: The systems are designed with the key service level agreements for dedicated EBS and network bandwidths. EBS has a dedicated 14 Gbps connection to ensure optimum disk performance and a separate 25 Gbps for networking.
  • High Memory Instance SAP Benchmark


Cloudy Infrastructure

It’s important that cloud service providers update their infrastructure to meet customer requirements. It is just as important that the new systems introduced are available through the standard APIs and/or the administrator control panel. Amazon Web Services provides you the same management experience when managing instances ranging from the t3.nano with 0.5 GiB of RAM to the systems which start at 6 TiB of RAM. This is an important detail since the new High Memory Instances are bare metal servers based on Amazon’s Nitro technology which is a combination of AWS-built hardware and software components that provide customer’s full access to the hardware resources.

The High Memory Instances are a new variation from other Nitro (bare metal) instances since the High Memory Instances use EBS storage as opposed to other Nitro instances which use local NVMe. This difference allows the High Memory Instances to support terabytes of datasets which makes the systems ideal for running large enterprise databases, including SAP Certified production installations of SAP HANA in-memory database in the cloud. Additionally, AWS has integrated the new instance type into the SAP HANA Quick Start Deployment. It provides customers and partners the ability to launch an SAP HANA High Availability cluster using SUSE Linux Enterprise Sever for SAP Applications.

To learn more about review the Quick Start documentation as well as a SUSE and Amazon created white paper outlining the best practice for SAP HANA SR Performance Optimized Scenario on the AWS Cloud.

If you have any questions please email us at

Changing Instance Types In AWS For SLES 12 SP2 And SLES 12 SP3 Based HVM Instances (and later)

Sunday, 12 August, 2018

Ever tried to switch instance types from lets say t2 to m5 on SLES 12 SP3 (including SLES For SAP)? Well if you did you were in for a bad surprise in that your instance would no longer boot. Switching the instance type back away from the newer instance types c5, m5, m5d…. and restarting the instance would get everything working again. That’s of course not the way we want things to behave.

The issue has been fixed in images with a date stamp later then 20180810. For running instances addressing the issue is reasonably straight forward.

Update 2021-01-07:

Yeah well the issue was fixed in images after 20180810. But then We dropped the config when SLE 15 was released and with the kernel change in SLE 12 SP5 the virtio module disappeared from the kernel. However, not until SLE 15 SP2 did dracut trigger an error and thus generate an insufficient initrd for type switching. Meaning is you are running an instance based on SLE 15 or later from an image with a date stamp prior to 20210107 you need to check if /etc/dracut.conf.d/07-aws-type-switch.conf exists. If it does not exist create it with the content shown below. If it does exist, at least 2 image refreshes were pushed out that contained virtio you want to fix it before you attempt to switch instance types between Nitro and Xen based instance types.

And now I get to claim again, instances started from images with a date stamp later than 20210107 require no action for instance type switching.

End Update 2021-01-07:

As root run:

For SLES 12 SP4 and earlier based instances:

echo ‘add_drivers+=” ena ext4 nvme nvme-core virtio virtio_scsi xen-blkfront xen-netfront “‘ >> /etc/dracut.conf.d/07-aws-type-switch.conf mkinitrd

Update 2021-01-07:

For SLES 12 SP5 and later based instances

echo 'add_drivers+=" ena ext4 nvme nvme-core xen-blkfront xen-netfront "' >> /etc/dracut.conf.d/07-aws-type-switch.conf mkinitrd

End Update 2021-01-07:


Newer instance types present the root volume to the guest instance from NVMe devices, while older instance types present the root device as a virtual block device. While all SLES 12 SP2 and SP3 images boot on either instance type, during initial boot the initrd gets regenerated to fit the instance type. This has the effect that when booting on the older instance types drivers needed to boot on newer instance types get removed from the initrd and vice-versa. The config change above simply makes sure that the necessary drivers for both instance types get included in the initrd when it gets regenerated and thus the problem is fixed.

What if?

What if your running instance has a longer history? Meaning way back when you started with a SLES 11 based instance or anything in between and you have been migrating your instances. Well as far as the EC2 framework is concerned you are still running an instance of the image you started and older images do not support the new instance type. Therefore EC2 will not let you switch.

SUSE powers SAP HANA system replication in AWS cloud

Tuesday, 31 July, 2018

We did it again! SAP’s LinuxLab is an excellent place for collaboration projects. Architects from Amazon Web Services and SUSE developed a brand-new best practice available at The new guide explains how to automate SAP HANA system replication (SR) in the AWS virtual private cloud with SUSE cluster technology. The solution is of course based leading operating system – SUSE Linux Enterprise Server for SAP Applications. The guide focuses on the performance optimized scenario which allows the fastest takeover procedure to the secondary site.

SAP HANA in the cluster

Content of the new Guide

The guide explains the architecture of the SAP HANA SR in the cloud, supported scenarios and typical prerequisites. One of the most important prerequisites covers the implementation of a reliable fencing (“Shoot The Other Node In The Head “- STONITH) method. STONITH helps the cluster to ensure that a lost cluster node is definitely not running resources (like SAP HANA) any more when the cluster decides to takeover those workloads and resources.

The setup procedure is also described step-by-step, beginning with preparing the AWS environment, then installing SAP HANA up to integrating the database into the SUSE cluster.

After the setup procedure the document discusses administrative do-and-don’t as well as  points to additional external resources providing further information.

Moving a workload architecture from “on-premise” to a cloud forces some additional setup steps. Therefore the guide describes the steps needed in AWS as well as the steps to install and integrate SAP HANA into the SUSE cluster.

Configuration Steps Overview

At the begin of the setup you prepare the AWS environment. The guide explains the AWS terminology and topology such as regions, availability zones and AWS virtual private network. It describes all needed steps to prepare your AWS environment to be ready to install SAP HANA into your systems and to integrate your database into the SUSE cluster. In particular it explains the concept of the AWS virtual private cloud (VPC) as network component, the use of overlay IP addresses and routing changes. This concept allows clients to connect transparently whenever the cluster processes a takeover from one availability zone to an other.

The next main step describes the installation of  SAP HANA in both AWS regions, including setting up SAP HANA system replication. NOTE: This section was added more as a reference to allow an easy setup description, but does not of course replace the original SAP installation and administration documentation. You should always read and follow the SAP documentation in addition to our procedure.

After the successful  implementation of the system replication we recommend to test this functionality via manual test takeovers. This checks that everything is ready for the cluster integration.

Now it’s time to setup the SUSE cluster. The resource agents SAPHana and SAPHanaTopology are handling the SAP HANA database in both availability zones. These resource agents are exclusively part of the  SLES for SAP Applications product. You can use them without paying additional fees. In this phase of the project you will install the cluster software. Then you build the base cluster configuration and add the resources controlled by the cluster. The required resources include the STONITH method, the overlay IP address and the routing entries.

Finally you integrate the already running SAP HANA system replication pair using the SAPHana* resource agents.

What’s next?

Visit our SUSE best practice library.  Have a look at the document “SAP HANA High Availability Cluster for the AWS Cloud” and start you project to automate SAP HANA system replication using the SUSE cluster solution.


SAP Enqueue-Replication High Availability on AWS Virtual Private Cloud powered by SUSE Linux Enterprise Sever for SAP Applications 12

Monday, 16 July, 2018

SUSE architects have improved the cluster architecture to be fully compatible with the updated SAP certification for SAP NetWeaver cluster integration. SAP released this updated SAP certification under the name NW-HA CLU 740. SUSE passed this certification on SUSE Linux Enterprise Server for SAP Applications 12 for both Intel X64 and IBM Power little endian platforms. SUSEs cluster architecture is now “SAP certified – Integration with SAP NetWeaver”. You can implement this cluster solution on bare-metal, virtualized and public cloud systems such as Amazon Web Services.

A team of AWS and SUSE architects have written a brand new best practice guide to help customers implement the new NW-HA CLU 740 cluster architecture and to achieve the following goals:

  • Integration of the cluster with the SAP start framework sapstartsrv to ensure that maintenance procedures do not break the cluster stability
  • SAP Rolling Kernel Switch (RKS) awareness
  • Standard SAP installation to improve support processes

The best practice guide is available at

The cluster resides in one AWS region. You should stretch the cluster over multiple availability zones. This concept reduces the chance of a complete failure. The guide explains the needed steps required in AWS virtual private cloud as well as the configuration and setup of the SUSE cluster framework.

As always it is a good principle to design clusters to be as simple as possible to mitigate operational errors. Testing of the complete setup as well as expected scenarios and behaviors is crucial.

As a starting point the guide also describes to test the AWS specific cluster resource agents manually.

Download the setup guide today and start your project with SUSE Linux Enterprise Server for SAP Applications 12 on AWS virtual private cloud.

Meet SUSE at AWS Summit San Francisco!

Monday, 2 April, 2018

This Wednesday, April 4th 2018 at the Moscone Center in San Francisco we invite you to network with our team of cloud solution architects at AWS Summit San Francisco at Booth 1122. We look forward to engage with you there and wanted to share a peak at some of the great topics we expect will come up in case you can’t make it:

Cloud-Native Linux Tools and Features

Did you know that SUSE Linux Enterprise Server has a number of tools to enhance your experience building and delivering on AWS? New additions such as SUSE ‘IPA’ facilitate and simplify automated testing in the public cloud, with the ability to also integrate it with openQA and even AWS lambda.

Transitioning to SAP HANA and S/4HANA on AWS

Moving to SAP HANA on AWS helps you quickly modernize business operations by providing you with improved efficiency and real time analytics – but are you unlocking AWS innovation beyond the infrastructure?

Some of the greatest customer stories we’ve heard this year are about fast-moving enterprise companies migrating mission-critical apps to cloud combined with the guidance of trusted experts that understand the depth of the AWS service portfolio. Luckily for you, right next to us you’ll find Lemongrass, an SAP on AWS APN Competency and key SUSE partner, at booth 1118. Learn from our wide variety of shared customer experiences and talk to us about your current SAP modernization efforts.

Optimizing IT Operations on AWS

Rapid technology advancements such as those announced every year at AWS events create endless new opportunities – but also bring many new management challenges. What can you do to reduce the complexity?

Ask us about SUSE Manager 3.0, and how you can quickly deploy a solution that will help you optimize operations on public cloud. Many of our customers and partners are using this solution to maintain secure, highly-available environments that are cross-platform and cross-cloud.

Containerized Applications on AWS

SUSE has decades of experience helping customers move to the next phase of IT. In the world of containers for example we’ve been enabling you to deploy containerized workloads on AWS leveraging AWS EC2 Container Service since 2015. Now, you’ll find new SUSE solutions like SUSE CaaS Platform leveraging Kubernetes technology to help you automate deployment and scaling for your container-based applications on AWS.

If you want to schedule a meeting in advance – reach out to us today!