This tutorial will provide you an alternative guide on how you get your first experience with our SAP Trials offered via SAP Cloud Appliance Library. The approach described should enable you to get your trial instance up and running on AWS with minimal configuration effort on Amazon Web Service (AWS). Although we describe this approach we still recommend that you follow the more secure setup descriptions in the tutorial with a virtual private cloud and VPN access http://scn.sap.com/docs/DOC-46629.
Disclaimer
Please keep in mind that this is just a proposal to get you started quickly and only one variant how to realize such a scenario. There are a lot more installation and configuration options which are not shown below. Thus, this might not be the perfect setup for your personal use case. So please consider alternative scenarios explained in the VPC documentation. In addition, we always recommend to set up a billing alert for your AWS account to avoid unpleasant surprises.
Pre-requisites
Alternative Deployment Options
Public VPC Deployment
Next to the mentioned pre-requisites above this deployment option requires the additional step of creating a VPC within your AWS account. (Please Ensure that you are always working in AWS region “US East (N.Virginia)”).
After you have created the VPC you can directly start creating your trial instance via the SAP Cloud Appliance Library Test Drive Center. You will now have the additional option to deploy the instance into the “corporate network” which means into your newly created VPC.
The instance will be directly visible within your EC2 console on AWS, and it will be ready to use after the deployment time of 40 minutes, but until now you will not be able to access it since your VPC is a private network on AWS.
In the first step open the AWS console and navigate to the EC2 service, Elastic IPs. Allocate an Elastic IP for use with VPC:
In the second step select the Elastic IP from the list and click on “Associate Address” and assign it in the upcoming pop-up to your trial instance.
It is important that you notice that you now have exposed the instance to the public internet and that you can access it in the same way as in the first option described above. The differences to the first approach are:
Important:
With regards to security please ensure that you also read the last paragraph of this post which mentions the minimum security options which you should consider with a public deployment.
Security Considerations:
For the above options we recommend the following minimum steps:
This post describes the fastest approach to get access to your trial on AWS. We hope that it is good starting point and that you have fun with the trial and feel motivated to get more familiar with alternative AWS setup options.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
5 | |
3 | |
3 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 |