Due to my product management role within the SAP Connected Health organization, I want to eat our own dog food / drink our own champagne, so that I have hands-on experience and really can put myself into the shoes of our customers.
Therefore, I decided to give our cloud-based trial version of the SAP Connected Health platform and SAP Medical Research Insights a try on Amazon AWS by using the SAP Cloud Appliance Library (CAL). My colleague Enakshi Singh recently announced this in a blog entry.
A first starting point is definitely the document “Getting Started Guide for SAP Connected Health Platform and SAP Medical Research Insights, Cloud Appliance Library – Trial Version”. However, as I didn’t have any hands-on experience with both Amazon AWS and the SAP Cloud Appliance Library yet, I needed a little bit of additional help, which I would like to share here.
First, when I naively created a new AWS account and created a new user, I forgot to assign the privileges needed by the SAP Cloud Appliance Library for creating a new instance. Fortunately, this is explained step-by-step in the following video on YouTube:
Once an AWS Account and a user has been created, it is fairly easy to create an instance from the SAP Cloud Appliance Library using the Amazon AWS credentials, i.e. the Access Key ID and the Secret Access Key. The trial version of the SAP Connected Health platform can be found by searching under “Solutions”:
Clicking “Create Instance” brings up the dialog where the Amazon AWS credentials need to be provided:
That’s more or less it for creating a trial instance! The newly created instance should show up under “Instances”:
The last thing that needs to be done is defining the “Access Points”, i.e. the ports that need to be opened, so that the application and maybe the database can actually be accessed from a browser and maybe SAP HANA Studio or via SSH:
It should now be possible to access the system via the following URL:
The pre-configured users including their passwords are listed in the Getting Started Guide mentioned above. If you cannot access the system, you might want to restart the instance after you have configured the “Access Points”, i.e. doing a “Suspend” followed by an “Activate”.
For cost control reasons, you also might want to define a schedule for activating and suspending the instance or a budget within the Amazon AWS management console.
Enjoy the trial!