Connecting to an AWS instance for SAP BusinessObjects BI4.x

This document is part of the series Getting Started with SAP BusinessObjects BI4.x on AWS

You can connect to an Amazon Web Services (AWS) instance by selecting a system meeting your sizing requirements as defined in an earlier steps. If you have not yet provisioned an AWS Instance for your SAP BusinessObjects BI4.x deployment , please start reading the provisioning guidelines available on : BI@AWS 02 : Provisioning a AWS instance for SAP BusinessObjects BI4.x

Prerequisites:

• An Amazon Web Services account
  Note: When you create an account, you are automatically signed up for all AWS services. However, you will only be charged for the services you use.
• Go through the SAP BusinessObjects What's New Collection to gain insight in what your best version is.
• Understanding the support of deploying an SAP BusinessObjects BI4.x system on AWS as documented in http://service.sap.com/sap/support/notes/1656250
• An up and running AWS Instance meeting the requirements as described in Provisioning a AWS instance for SAP BusinessObjects BI4x
• The Instance ID as received in the previous step
  
• Recommended : Setup your Virtual Private Cloud (VPC) connector. The VPC is recommended by Amazon, setting up a VPC is described in the document from SAP HANA ONE (AWS VPC setup) however the steps are equal for any SAP deployment.

Assign Elastic IP:

1. Have your AWS Image up and running in your preferred region
2. Note the fact that no Public IP has been assigned in the sample setup. If you have a public IP assigned, please validate if this has been defined as a Elastic IP. In case you have no Elastic IP assigned, your Public IP may change after restarting your Image, driving potential issues while connecting into your SAP BusinessObjects environment. Additionally it is not recommended to have the SAP BusinessObjects BI Platform (BIP) being deployed against a dynamic IP, as BIP has bindings with the IP.
   
   Image may be NSFW.
   Clik here to view.
3. To assign a static public IP, we have to create a Elastic IP.
   for information about the Elastic IP, please check : Elastic IP Addresses - Amazon Elastic Compute Cloud
   
   Creating an Elastic IP can be done via the menu bar on the left under -> Network & Security -> Elastic IPsImage may be NSFW.
   Clik here to view.
   
   
4. Navigate to "Elastic IPs" and select "Allocate New Address" to start the creation of an Elastic IP
   
   Image may be NSFW.
   Clik here to view.
5. You will get a confirmation IF you want to allocate a new IP. Select "Yes, Allocate" to generate a new Elastic IP
   Note: Creating Elastic IP's without using them will result in an additional charge
   
   Image may be NSFW.
   Clik here to view.
6. Your Elastic IP is generated and can be assigned to your Instance
   Image may be NSFW.
   Clik here to view.
   The IP created will be listed under your Elastic IP's
   Image may be NSFW.
   Clik here to view.
7. Now having the Elastic IP created, we can assign this to our Instance, enabling a fixed IP for usage outside AWS. To assign the IP to you Instance, select Action -> Associate Address
   Image may be NSFW.
   Clik here to view.
8. Select the Instance ID from your system and confirm via "Associate"
   Image may be NSFW.
   Clik here to view.
9. If we move back to the EC2 screens, we will see that the Elastic IP has been assigned to the Instance
   Image may be NSFW.
   Clik here to view.

Connecting to AWS Instance running Windows

Now that we have assigned a public IP to the AWS Instance, we can connect to the AWS instance using Microsoft Remote Desktop

1. Before connecting to the Windows Instance, we need to set an Administrator password to enable a logon. To decode the Administrators password from the key file generated during instance a few steps are required. If you have already set your Windows Password, please continue with step 5
   
   - Select the instance you want to retrieve the Windows Password
   - Navigate to Actions -> Get Windows Password
   Image may be NSFW.
   Clik here to view.
2. Choose the key pair file as stored while creating the instance
   Image may be NSFW.
   Clik here to view.
3. Once the Key Pair is loaded, the value will be visible, select "Decrypt Password" to get the Windows PasswordImage may be NSFW.
   Clik here to view.
4. The Windows Password is shown, note down to password or copy this for later use
   Image may be NSFW.
   Clik here to view.
5. Start your Remote Desktop via your preferred path :
   - Start -> Run -> mstcs.exe
   - Start -> All Programs -> Accessories -> Remote Desktop Connection
   - Start -> Run -> Remote Desktop
   
   Enter the IP Number as recorded for the Public IP of you Instance
   Image may be NSFW.
   Clik here to view.
6. On the Credentials Screen, enter you credentials to connect to the AWS Windows Instance. Please note to connect with .\Administrator to force the use of the local authentication model within the AWS Instance
   Image may be NSFW.
   Clik here to view.
7. Depending on your security settings, a security popup may appear
   Image may be NSFW.
   Clik here to view.
   Accept the warning (and if preferred select the tickbox "Don't ask me again for connections to this computer")
8. You can now work on your AWS Instance and start the installation of SAP BusinessObjects BI4.x. Please continue with : Deployment and Configuration of BI4x on AWS
   
   

Connecting to AWS Instance running Linux

To be added

Back to the Main Page for Deploying BI4.x against Amazon Web Services