Content Package:Amazon Elastic Compute Cloud (EC2) Integration · in Amazon EC2 through the...

SmartCloud Control Desk 7.5.1.1

Content Package: Amazon ElasticCompute Cloud (EC2) Integration

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 37.

This edition applies to version 7, release 5, modification 1, fix pack 1 of SmartCloud Control Desk and to allsubsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Amazon Elastic ComputeCloud integration overview . . . . . . 1

Chapter 2. Prerequisites . . . . . . . . 5

Chapter 3. Preparing Amazon EC2 forthe integration . . . . . . . . . . . . 7Creating an Amazon Web Services account . . . . 7

Chapter 4. Installing integrationcomponents . . . . . . . . . . . . . 9Installing the content package . . . . . . . . 9Installing the content package behind a firewall . . 9Installing the PSI package . . . . . . . . . 10

Error detection and recovery . . . . . . . 12

Chapter 5. Configuring SmartCloudControl Desk for the Amazon EC2integration . . . . . . . . . . . . . 13Configuring required Jython packages . . . . . 13

Downloading required Jython library packages 13Copying Jython packages. . . . . . . . . 14

Importing the SSL certificate. . . . . . . . . 15Obtaining the Amazon certificate . . . . . . 15Importing the SSL certificate into WebSphereApplication Server . . . . . . . . . . . 16

Enabling the My Resources navigator. . . . . . 18Activating the escalation to poll status . . . . . 19Configuring end points for the Amazon EC2integration. . . . . . . . . . . . . . . 20

Configuring domains for the Amazon EC2integration. . . . . . . . . . . . . . . 20Configuring the sample Red Hat Enterprise Linuxcatalog offering . . . . . . . . . . . . . 21

Chapter 6. Using the integration . . . . 23Requesting a virtual machine instance on AmazonEC2 . . . . . . . . . . . . . . . . . 23Viewing the status of a deployment request . . . 24Starting, stopping, or deleting VM instances . . . 24

Chapter 7. Administering virtualmachine deployments . . . . . . . . 27Creating new catalog offerings for Amazon EC2VMs . . . . . . . . . . . . . . . . . 27Troubleshooting failed VM deployments. . . . . 29Managing deployed VMs as configuration items . . 29

Appendix. Additional referenceinformation . . . . . . . . . . . . . 31SmartCloud Control Desk objects used in theintegration. . . . . . . . . . . . . . . 31SmartCloud Control Desk domains . . . . . . 31Configuration items for deployed Amazon EC2instances . . . . . . . . . . . . . . . 33Deployment scripts . . . . . . . . . . . . 34SmartCloud Control Desk end points . . . . . . 34

Notices . . . . . . . . . . . . . . 37Trademarks . . . . . . . . . . . . . . 38

© Copyright IBM Corp. 2013 iii

iv SmartCloud Control Desk 7.5.1.1: Content Package: Amazon Elastic Compute Cloud (EC2) Integration

Chapter 1. Amazon Elastic Compute Cloud integrationoverview

SmartCloud Control Desk Version 7.5.1.1 users can install an optional contentpackage that integrates the product with Amazon Elastic Compute Cloud.

Amazon Elastic Compute Cloud (EC2) is a public cloud where users can purchasecomputing services that are based on the amount of capacity that they need. Userscan create, stop, start, and delete the virtual machine (VM) instances as requiredand pay an hourly rate for services that they use.

The integration package lets administrators manage virtual machine deploymentsin Amazon EC2 through the SmartCloud Control Desk user interface.Administrators can configure SmartCloud Control Desk to provide catalogofferings for virtual machine deployment in Amazon EC2. Users can then requestdeployment of a virtual machine instance in the cloud and use the VM to runsoftware applications.

When the requests are routed through SmartCloud Control Desk, you can applystandard business processes, such as approval requirements, to the deploymentwork flow.

The content package integrates change and configuration management with cloudmanagement. When an instance is successfully deployed to the cloud, aconfiguration item (CI) is created, and you can use SmartCloud Control Deskfunctions to manage problems, incidents, and changes.

After you install and configure the package, SmartCloud Control Desk providesthe following features:v Administrators can create offerings for VM deployments to Amazon EC2 and

make these offerings available to SmartCloud Control Desk users.v In the Activities and Tasks application, administrators can monitor deployments

and resolve incidents that are related to deployments.v In the Configuration Items application, administrators can view data about the

VMs that are deployed and use that information to manage computingresources.

v In the Self Service Center or Offering Catalog application, users can request VMdeployments to Amazon EC2.

v In the My Resources navigator in the Self Service Center, users can view thestatus of their requests for VM deployment. After VMs are deployed, users canalso use the My Resources navigator to start, stop, and delete the VMs asneeded.

The SmartCloud Control Desk Amazon EC2 integration is supported only onWebSphere® Application Server. The package content and documentation for thisintegration is provided in English only.

The SmartCloud Control Desk Amazon EC2 integration package contains code thatis required for the integration. This guide explains how to install and configure theintegration and how to use SmartCloud Control Desk to manage the virtualmachines that are deployed.

© Copyright IBM Corp. 2013 1

The integration package includes a sample offering for deployment of an instanceof Red Hat Enterprise Linux 64-bit to the cloud. This guide explains how toconfigure SmartCloud Control Desk for that catalog offering. The sample is used toillustrate how the self-service user in SmartCloud Control Desk submits a requestto deploy a virtual machine instance. The sample can also be used as a model ortemplate for creating more virtual machine deployments.

Introduction to Amazon EC2

To use virtual machines in the Amazon EC2 cloud, you create an Amazon WebServices account, define how to build the instance or instances that you want, andthen start instances.

Amazon Web Services hosts Amazon EC2 in multiple locations around the world.Locations are segmented into regions and Availability Zones. A region is a specificgeographic area, for example US East (Northern Virginia) Region. Each AmazonEC2 region is independent and separated from other regions. When you create anAmazon EC2 resource, that resource is tied to the region that you designate whenyou create it.

Within regions, separated isolated locations exist that are called Availability Zones.You can distribute your instances across multiple Availability Zones and designyour applications to allow instances in a different Availability Zone to handlerequests.

The two basic requirements for building VM instances are selecting the image(Amazon Machine Image) to deploy and selecting the type of instance that youwant.

For the Amazon Machine Image (AMI), you can select a pre-configured AMI or youcan create your own AMI that specifies what operating system and virtual softwareto use. Amazon Web Services offers many pre-configured AMIs with variouscombinations of operating systems and virtual application software.

To specify the hardware, including the amount of processor, memory, storage, andnetwork capacity that you want, you select an instance type. Amazon Web Servicesoffers various pre-configured instance types so that you can select resources thatare appropriate for your business needs. When you specify instance type, you canalso set instance sizes.

Amazon Web Services uses public-key cryptography to secure sites so a key pairmust be created for each instance that you deploy. A key pair includes a public keyand a secret key that together control access to virtual machines. A key pair is notrequired to deploy a VM instance to the cloud. However, a key pair is required tolog in to a deployed VM instance. A default VM is provided with the SmartCloudControl Desk integration package. The default key pair can be used to test whetheryour deployment of the sample offering provided with the package is successful.

To use the integration, create one or more key pairs that can be linked to instancesthat are deployed. The key pairs enable users to log in to the instances. Amazonrecommends that you give a key pair a name that is easy to remember and thatyou include in the name the region that the key pair is associated with, forexample your_user_name_key_pair_region_name. When you create the key pair, theprivate key is downloaded to your browser, and you can save it.

2 SmartCloud Control Desk 7.5.1.1: Content Package: Amazon Elastic Compute Cloud (EC2) Integration

Remember: Note the key pair name and the private key. In some cases, you needthe key pair name to start a virtual machine instance, and you need the privatekey to log in to the virtual machine.

For extra security, you can create security groups. Security groups serve as afirewall that controls access to connect to virtual machine instances using SSH.Amazon recommends that you give the security group a name such asyour_user_name_SG_region_name, which includes the region. After you create thesecurity group, you can create security group rules that specify one or more publicIP addresses or a range of addresses that are allowed to connect to virtualmachines on Amazon EC2.

For more information about Amazon Elastic Compute Cloud, see the product pagefor Amazon EC2.

How the integration works

When the Amazon EC2 integration is implemented, each catalog offeringcorresponds to an Amazon Machine Image. When users request an offering, theyselect an instance type that is based on the processor, memory, and other hardwarerequirements that they have. The request for the offering triggers creation of aservice request. In the default work flow for the SmartCloud Control Deskintegration, the request is automatically approved; however, you can customize thework flow to meet your business needs.

A change work order is created, and a response plan (AWSDEPLOY) and a jobplan (AWSDEPLOY) are applied. The change work order is fully automated. Thejob plan contains one job plan task that invokes the AWSDEPLOY work flow.

The SmartCloud Control Desk work flow sends a request to Amazon EC2 todeploy an instance with the AMI specified by the catalog offering and the instancetype that is requested by the user. An escalation is launched that checks the statusof the deployment. Results of the status check are reported in the log file of thework order.

After the virtual machine instance is successfully deployed, the status is reportedin the My Resources navigator in the Self Service Center.

After an instance is deployed, a configuration item (CI) is created for the instance.CIs created for Amazon EC2 virtual machine instances belong to the childclassification CI.AmasonComputerSystem under the CI.COMPUTERSYSTEMclassification. Details about the deployed VM are available in the Long Descriptionfield on the CI Details tab in the Configuration Items application.

In the Self Service Center, users can start, stop, or delete the deployed VM instanceas needed.

Implementation process

To use this integration, complete the following tasks:v Ensure that you installed SmartCloud Control Desk Version 7.5.1.1.v Create an Amazon Web Services account for VM deployments.v Download the Jython programming packages that are required for the

implementation and copy them to the appropriate location in your environment.v Download the Amazon EC2 PSI package from the IBM® ISM Library.

Chapter 1. Amazon Elastic Compute Cloud integration overview 3

http://aws.amazon.com/ec2/

http://www-304.ibm.com/software/brandcatalog/ismlibrary/search#rc=SmartCloudControlDesk:IBM%20SmartCloud%20Control%20Desk

v Install the Amazon EC2 content package using the Content Installer applicationv Install the Amazon EC2 PSI package.v Configure the integration between SmartCloud Control Desk and Amazon EC2.


Chapter 2. Prerequisites

Several prerequisites must be met before you can implement the SmartCloudControl Desk integration with Amazon EC2.

The integration with Amazon EC2 requires that you install SmartCloud ControlDesk 7.5.1 and apply fix pack 7.5.1.1, create an Amazon Web Services account, andobtain several additional programming components. Before you attempt toimplement the integration, make sure that you satisfy the following requirements:v Install SmartCloud Control Desk Version 7.5.1.1v Create an Amazon Web Services accountv Download the following Jython programming packages, which are required for

the integration:– simplejson– boto

v Download the Amazon EC2 PSI package (amazonec2_pmp.zip) from the IBM ISMLibrary.


http://pypi.python.org/pypi/simplejson/1.3

http://pypi.python.org/pypi/boto



Chapter 3. Preparing Amazon EC2 for the integration

Before you can integrate with Amazon EC2, you have to create an Amazon WebServices account and enable the account to create virtual machine instances onAmazon EC2.

When you create an Amazon Web Services account, set up account accesscredentials to provide security for the account. You can also create one or more keypair names that enable users to access virtual machine instances.

To launch instances on Amazon EC2, you must also specify a region, an AmazonMachine Image (AMI), and an instance type. The sample offering included in thepackage provides the region and the AMI, and you can select default instancetypes.

When you implement the integration, you can also create customized AMIs andselect other regions or instance types. For those tasks, see the Amazon ElasticCompute Cloud (EC2) Documentation.

Creating an Amazon Web Services accountTo implement the Amazon EC2 integration, you need an Amazon Web Servicesaccount.

About this task

When you initially create an Amazon Web Services account, the email address andpassword that you provide allow full access to all resources in your accountincluding any financial information that is associated with the account. Amazonprovides an additional web service to manage user access and permissions, AWSIdentity and Access Management (IAM). To limit access to the primary accountinformation, create additional security credentials for yourself and other users whorequire access. For more information about IAM, see the Using IAM guide.

The following steps describe how to create an Amazon Web Services account. Notethat the Amazon EC2 images used in this guide are examples only and might bedifferent if the user interface is changed.

Procedure1. Open the web page for the AWS Management Console (http://

aws.amazon.com/console/).2. Click Sign in to the AWS Console.3. Select I am a new user and create a user account.4. From the drop-down list in the upper right corner of the screen next to your

log-in name, select Security Credentials and specify user credentials foraccount access.


http://aws.amazon.com/documentation/ec2/

http://aws.amazon.com/documentation/ec2/

http://docs.aws.amazon.com/IAM/latest/UserGuide/IAM_Introduction.html

http://aws.amazon.com/console/

http://aws.amazon.com/console/

5. On the window that is displayed offering you information about securitycredentials, click Continue to Security Credentials.

6. On the Your Security Credentials page, expand the Access Key section and clickCreate New Access Key.

7. To return to the Amazon EC2 dashboard, select Services in the upper leftcorner of the screen and select EC2. On the dashboard you can manage virtualmachine instances, image, security groups, and key pairs.


Chapter 4. Installing integration components

To implement the Amazon EC2 integration, install the content and PSI packages inyour SmartCloud Control Desk environment.

Installing the content packageInstall the SmartCloud Control Desk Amazon EC2 content using the ISM ContentInstaller application.

About this task

The following instructions explain how to install the integration using the ISMContent Installer application. The navcode for the content package is 1TW10CO0I.

Procedure1. In SmartCloud Control Desk, go to System Configuration > ISM Content

Installer.2. Select the IBM SmartCloud Control Desk link.3. On the Content Items page of the ISM Content Installer, locate content

package titled IBM SmartCloud Control Desk 7.5.1.1 (Catalog Offerings forAmazon Web Services EC2).

4. Click the Download link in the rightmost column to start the installation.5. Select Yes in the Install Warning dialog.6. Click the I Agree check box and click Download.7. You must accept the license to continue installing the content package.8. Switch to the Replacements tab in the Install Content dialog.

Important: All of the components that are listed on the Package Content tabmust be populated.

9. In the Replacements column, replace the Organization id and the Item SetIDs if they are different from the defaults. The field contains a list of theelements that are currently in the environment.

Note: Make note of the Item Set value. You must specify this value when youinstall the PSI package.

10. Click Install.

Installing the content package behind a firewallIf you do not have Internet access from your SmartCloud Control Desk installation,you can still install content packs using the ISM Content Installer.

Before you begin

If your installation is behind a firewall, you must first download the content packremotely and then copy it to your SmartCloud Control Desk server.


About this task

The following instructions explain how to install content packs from behind afirewall.

Procedure1. In a temporary location on your SmartCloud Control Desk server, create an

XML file called ContentSource.xml that contains the following text:<?xml version="1.0" encoding="UTF-8"?><catalog infourl="" lastModified="" owner=""

xmlns:tns="http://www.ibm.com/tivoli/tpae/ContentCatalog"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="ContentCatalog.xsd"><catalogItem>

<version>Enter the version number of the Content Installer pack,for example 7.5.1</version>

<type>mriu</type><name>Enter the name of package</name><description>Enter a description of the package here</description><homepage/><licenseurl/><category>Describe the category of the content</category><url>file:////C:\temp\TestPackage.zip</url>

</catalogItem></catalog>

2. Edit the name and description and the category according to the content thatyou are installing.

3. Change the file name in the URL to the name of the content pack zip file.4. Save the file.5. Copy the content pack zip file to the temporary directory on the server.6. Go to the ISM Content Installer application: System Configuration > IBM

Content Installer.

7. Click New .8. In the URL field, specify the location of the ContentSource.xml file that you

created in step 1 and a description, for example C:\temp\ContentSource.xml.9. Click Save.

10. On the Content Sources page, select the newly created content source.

11. Click the download link to install the content.

Installing the PSI packageAfter you install the Amazon EC2 content package, install the Amazon EC2 PSIpackage.

Before you begin

Before you can install the Amazon EC2 PSI package (amazonec2_pmp.zip) , youmust download the package from the IBM ISM Library.

To install the Amazon EC2 PSI package, you must use the command interfaceinstead of the graphical user interface. Before installation, review the followingcommand syntax and parameter definitions and ensure that you have the requiredvalues for the installation command.



Note: If you provide an incorrect value for the -XITEMSETID parameter, you are notnotified at installation time. If you provide an invalid value for any of the databaseor application server connection parameters, a notice is written in the logs. Formore information, see “Error detection and recovery” on page 12.

The -loadlanguages option is not available for this integration package, which issupported in English only.

SyntaxsolutionInstaller.bat -action install -pkgpath $PKGPATH -XITEMSETID $ITEMSET-dbuser $DBUSER -dbpwd $DBPASSWD -wasuser $WASUSER -waspwd $WASPWD-wasrxauser $WASRXUSER -wasrxapwd $WASRXPWD -license accept

where the string with the dollar symbol ($) specifies a variable that is appropriatefor your environment.

For example, specify -wasuser wasadmin to indicate that wasadmin is the user namefor the parameter -wasuser.

Parameters

-dbpwdPassword of the database user ID that is used to access the Maximo®

database.

-dbuserDatabase user ID that is used to access the Maximo database.

-licenseSpecifies whether you want to automatically accept the license agreementor if you want to be prompted to accept or reject it. Valid values are acceptor prompt.

-pkgpathFile path of a process solution package. Paths that contain embeddedspaces must be enclosed in quotations. This path corresponds to where youdownloaded the amazonec2_pmp.zip package (see step 2 on page 12).

-waspwdPassword for the WebSphere Application Server administrator password(was_admin_password).

-wasuserUser ID for the WebSphere Application Server administrator.

-wasrxapwdPassword for the user ID that has remote access to the WebSphereDeployment Manager system.

-wasrxauserUser ID for the user that has remote access to the WebSphere DeploymentManager system.

-XITEMSETIDThis value is the ITEMSET for the offering.

Important: You must provide the -XITEMSETID parameter, and it mustmatch the Item Set value that you specified on the Replacements tab instep 9 on page 9. Failure to do so results in an inoperable referenceoffering.

Chapter 4. Installing integration components 11

Procedure1. On the Content Items page of the ISM Content Installer, click the AWS EC2

link in the Category field, or click the PSI Package link in the Descriptionfield.

2. Download the AWS EC2 PSI package (amazonec2_pmp.zip). Note the pathwhere you save the file. You must specify this path for the $PKGPATH parameterwhen you install the PSI package in step 3.

3. On the SmartCloud Control Desk administrative workstation, start the ProcessSolution Installer (PSI). Open a command prompt and specify the appropriatecommand and parameters for your environment:v Microsoft Windows: c:\ibm\smp\bin\solutionInstaller.batv Linux/AIX®: /opt/ibm/smp/bin/solutionInstaller.sh

For example,solutionInstaller.bat -action install -pkgpath C:\temp\amazonec2_pmp.zip-XITEMSETID PMSCS1 -dbuser dbadmin -dbpwd dbadminpw-wasuser wasadmin -waspwd wasadminpw -wasrxauser Administrator-wasrxapwd wasrxadminpw -license accept

Error detection and recoveryIf you encounter problems installing the PSI package for Amazon EC2, you canview log files to determine the cause of the errors. You can also uninstall thepackage and attempt to reinstall it.

Detection

If you provide an incorrect value for the -XITEMSETID parameter, you are notnotified at installation time. If you provide an invalid value for any of the databaseor appserver connection parameters, a notice is written in the logs.

The log files are in the following default locations:v For Microsoft Windows: c:\IBM\SMP\install_dir\logsv For Linux/AIX: /opt/IBM/SMPinstall_dir/logs

The log files have the CTG prefix. You can find package-specific logs ininstall_dir\solutions\logs\amazonec2_pmp.

Recovery

If you provide invalid values for any of the PSI installer parameters, uninstall thepackage as follows.1. Locate the UUID of the package to uninstall. For this package, the UUID is

E0C9E86E1DAA4C6298767DA4CB0CF780. Or run the following command, and thenscan the output for the package.solutionInstaller.bat -action showinstalled -type processmodule

2. Run the PSI uninstall command:solutionInstaller.bat -action uninstall -pkguuid $UUID -dbuser $DBUSER-dbpwd $DBPASSWD -wasuser $WASUSER -waspwd $WASPWD -wasrxauser$WASRXUSER -wasrxapwd $WASRXPWD

where $UUID is the UUID of the package to remove.3. After the uninstall completes, you can reinstall if you want to use the feature.


Chapter 5. Configuring SmartCloud Control Desk for theAmazon EC2 integration

After you install the Amazon EC2 content and PSI packages, configure SmartCloudControl Desk to implement the integration.

To configure SmartCloud Control Desk for the integration, complete the followingtasks:v Install or deploy the Python packages that are required for the implementation,

including Jython, simplejson, and boto.v Import the SSL certificate for Amazon EC2 into WebSphere Application Server.v Enable the My Resources navigator in SmartCloud Control Desk.v Activate the escalation that polls for the status of virtual machine deployments.v Configure the end points for the Amazon EC2 integration.v Configure the domains for the Amazon EC2 integration.v Configure the service catalog offering.

Configuring required Jython packagesBefore you configure the Amazon EC2 integration, configure the required Jythonpackages.

Downloading required Jython library packagesThe Amazon EC2 integration requires Jython library packages that must bedownloaded from the Internet.

About this task

At publication, two versions of boto are provided by Amazon: boto 2.9.6, which isavailable from the download button on the Amazon download site, and 2.13.3. Ifyou select the option get the suorce on gitHub on the download site, you getversion 2.13.3.

Note: New versions of boto are posted frequently. You can use the most recent onethat is available.

For more information about boto, see http://boto.readthedocs.org/en/latest/.k

At publication, the current version of simplejson that is offered by python.org isversion 3.3.0.

Procedurev To download boto, complete the following steps:

1. Go to the AWS SDK for Python (Boto) site: http://aws.amazon.com/sdkforpython/.

2. Click the download button.3. Save the file to a temporary location on the server where you have installed

SmartCloud Control Desk.v To download simplejson, complete the following steps:


http://boto.readthedocs.org/en/latest/

http://aws.amazon.com/sdkforpython/

http://aws.amazon.com/sdkforpython/

1. Go to the simplejson site on python.org: https://pypi.python.org/pypi/simplejson/.

2. Click the download button.3. Save the file to a temporary location on the server where you have installed

SmartCloud Control Desk.

Copying Jython packagesExtract the Jython jar file that is provided with SmartCloud Control Desk to theappropriate location on your application server. Then copy boto and simplejsoninto the Jython library.

Procedure1. To set up your Jython library, complete the following steps:

a. Locate the jython.jar file in your SmartCloud Control Desk installationdirectory:C:\ibm\SMP\maximo\applications\maximo\lib\jython.jar

b. Extract the jython.jar file to the following location on the application serverfor SmartCloud Control Desk: C:\jython.

Note: If you have your Jython library in a different location or if you areusing Linux, complete the following steps to change the path to the Jythonlibrary in the AWSEC2 script:a. Go to System Configuration > Platform Configuration > Automation

scripts.b. Locate the script AWSEC2.c. Change the path to the location where you installed the Jython library and

save the script. For instance, if the Jython library is installed under/opt/jython/Lib, change the following lines:for path in sys.path:

if (path.find("jython\Lib") != -1) :foundJython = True

if (foundJython==False):sys.path.append(r’C:\jython\Lib’)

Change the C:\jython\Lib references as follows.for path in sys.path:

if (path.find("jython/Lib") != -1) :foundJython = True

if (foundJython==False):sys.path.append(r’/opt/jython/Lib’)

2. To add boto to the Jython library, complete the following steps:a. In the temporary location where you downloaded the compressed boto file,

extract the boto directory.b. Copy the boto directory to the following location in your Jython library:

c:\jython\Lib.3. To add simplejson to the Jython library, complete the following steps:

a. In the temporary location where you stored the downloaded simplejson file,extract the file.

b. Copy the simplejson folder to the following location in your Jython library:c:\jython\Lib.


https://pypi.python.org/pypi/simplejson/

https://pypi.python.org/pypi/simplejson/

Results

After you complete this task, you have boto and simplejson directories inC:\jython\Lib on the SmartCloud Control Desk application server, as shown in thefollowing example.

Importing the SSL certificateTo enable SmartCloud Control Desk to communicate with Amazon EC2, obtain theSSL certificate from the Amazon server and import it into your application server.

Obtaining the Amazon certificateAbout this task

An Amazon endpoint is a URL that identifies the host and port that are the entrypoint for a web service. Amazon provides regional endpoints to enable fasterconnectivity.

Complete the following steps to obtain the SSL certificate from the Amazon server.

Procedure

To find the Amazon server host name that corresponds to the region that you wantto connect to, select one of the following options:v Go to http://docs.aws.amazon.com/general/latest/gr/rande.html, select EC2,

and choose an endpoint.v Go to http://aws.amazon.com/developertools/Amazon-EC2/351, download the

Amazon EC2 API Tools file, extract the tools files, and run theec2-describe-regions command.

Chapter 5. Configuring SmartCloud Control Desk for the Amazon EC2 integration 15

http://docs.aws.amazon.com/general/latest/gr/rande.html

http://aws.amazon.com/developertools/Amazon-EC2/351

Importing the SSL certificate into WebSphere ApplicationServer

Procedure1. Log in to the WebSphere Application Server administrative console as

wasadmin.2. Click Security > SSL certificate and key management.

3. In the SSL certificate and key management window, select Key stores andcertificates.

4. Select the truststore, usually CellDefaultTrustStore.


5. Select Signer certificates.

6. Click Retrieve from port.


7. In the Host field, specify the host name for the region and Amazon server thatyou want to connect to, for example ec2-us-west-2.amazonaws.com. You canadd as many regions as you want.

8. In the Port field, specify the SSL port for the Amazon server. The default portis 443.

9. In the Alias field, specify an alias for the server.10. Select Retrieve signer information. If the certificate information is retrieved

successfully, it is displayed.11. Click Apply and OK.12. Save the changes to the master configuration.

Enabling the My Resources navigatorThe My Resources navigator added in the Self Service Center with SmartCloudControl Desk 7.5.1.1 is disabled by default. Because the integration with AmazonEC2 uses the navigator, enable this feature.


About this task

User access to the My Resources navigator in the Self Service Center is controlledbased on security groups. You can grant access to the navigator in the SecurityGroups application.

Because the My Resources navigator is a superset of the My Assets pod, youmight want to disable the My Assets pod. This step is also described in thefollowing procedure.

Procedure1. Go to Security > Security Groups.2. Locate the group that you want to allow access to My Resources.3. Go to the Applications tab.4. In the Applications section, expand Filter and search for Self Service Center

in the Description field.5. In the Options for Self Service Center section, expand Filter in the second

table, and search for Show Self Service Center in the Description field.6. Locate Show Self Service Center My Resources link and select the Grant

Access check box next to it.7. To disable the My Assets pod, locate Show Self Service Center My Assets

pod and clear the Grant Access check box next to it.8. Save the record.9. Log out, and then log back in for the My Resources navigator to display in

the user interface.

Note: You might be required to also clear your browser history or cache.10. Go to Self Service > Self Service Center. The My Resources navigator should

appear on the home page.

Activating the escalation to poll statusTo enable SmartCloud Control Desk to poll the status of VM deployments onAmazon EC2, activate the escalation that checks to determine whether or not adeployment is complete.

About this task

The escalation that is provided in the Amazon EC2 integration package is set topoll for status every minute. The status is reported SmartCloud Control Desk inthe Self Service Center. When you configure the integration, you must activate thatescalation. If necessary, you can also change the schedule to a frequency that meetsyour business needs.

Important: If you do not activate the escalation, the offering does not workproperly. The instance is still created. However, the job is not completed and theservice request is not resolved. No CI is created, and you cannot use the MyResources navigator to manage the instance.

The following instructions explain how to activate the escalation.


Procedure1. Log in to SmartCloud Control Desk and go to System Configuration >

Platform Configuration > Escalations.2. Click Filter and search for AWSPOLLSTATUS.3. Open the escalation AWSPOLLSTATUS.4. Optional: If you want to change the frequency, change the Schedule from 1

minute to the frequency that you want.5. From the Select Action menu, select Activate/Deactivate Escalation to activate

the escalation.

Configuring end points for the Amazon EC2 integrationBefore you deploy VM instances, configure the end points that specify the accountcredentials for connecting to Amazon EC2.

Before you begin

To implement the integration, you must create one or more end points that specifysecurity credentials. The security credentials control access to the Amazon EC2account using both an Access Key ID and a Secret Access Key. Before you attemptto configure the end points for the integration, log in to your in your Amazon EC2account and create the security credentials that are required for your environment.For more information about security credentials, see Amazon EC2 Security Groups.

About this task

The steps in this procedure explain how to create end points by duplicating theSCCDAWS end point that is provided with the SmartCloud Control Desk AmazonEC2 integration package.

Procedure1. Go to Integration > End Points.2. Search for and select the SCCDAWS end point.3. From the More Actions menu, select Duplicate End Point.4. In the End Point field, enter a name for the end point.5. Enter a description.6. Expand the Password row.7. In the Encrypted Value field for the password property, specify the secret

access key for your Amazon EC2 security group.8. Expand the User Name row.9. In the Value field for the user name property, specify the access key for your

Amazon EC2 security group.10. Repeat steps 3 through 9 for each end point that you want to enter.11. Save the changes.

Configuring domains for the Amazon EC2 integrationBefore you can deploy VMs to Amazon EC2, configure the domain that specifiesvalues for key pairs.


http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html

Before you begin

To implement the integration, you must create one or more key pairs that can belinked to VM instances that are deployed. The key pairs enable users to log in tothe instances. Before you attempt to configure the domain for the integration,create the key pairs that are required for your environment in your Amazon EC2account. When you create the key pair, the private key is downloaded to yourbrowser, and you can save it.

Remember: Note the key pair name and the private key. Users must specify aprivate key to log in to the virtual machine instances. Administrators mustdistribute the keys to users to enable them to log in to the VMs.

For more information about creating key pairs, see Amazon EC2 Key Pairs.

About this task

In the Domains application, complete the following steps to specify the key pairsthat are available for your VM instances.

Procedure1. Go to System Configuration > Platform Configuration > Domains.2. Search for domains that begin with aws.3. Open the AWS_KEY_PAIR.4. Click New Row.5. In the Value field, specify the key pair name that you created in Amazon EC2.6. Enter a description.7. Repeat steps 4 through 6 for each key pair that you want to enter.8. Save the changes.

Configuring the sample Red Hat Enterprise Linux catalog offeringConfigure the sample Red Hat Enterprise Linux 64-bit catalog offering to work inyour business environment.

Before you begin

Each offering in SmartCloud Control Desk provides a VM deployment to AmazonEC2. To set up the offering in SmartCloud Control Desk , you must specify valuesfor some parameters that you defined for your Amazon EC2 account. Before youattempt to configure the sample offering, make sure that you have the key pairname for each VM instance that you want to deploy.

Also, verify that the image ID provided with the sample offering is valid. If not,use one of the Amazon EC2 public images or create your own image and specifythat image ID in the offering. For information about Amazon EC2 images, seeAmazon Machine Images (AMI).

About this task

This task describes how to configure the sample offering that is provided with theAmazon EC2 integration package so that it works in your environment. By defaultthe offering is active, and you must change its status to planning or pendingbefore you can configure it for your environment.


http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html

As you complete the steps, verify that the offering parameters of the sampleconform to the requirements of your environment and specify the appropriatevalues for implementing the offering in your business.

You can use this sample offering as a model for configuring other Amazon EC2catalog offerings that fit your business needs.

Procedure1. Log in to SmartCloud Control Desk as the Service Catalog administrator.2. Go to Service Request Catalog > Offerings.3. Click Filter and search for AWS_DEPLOY_RH64.4. Open the record.5. To change the status of the record from Active to Planning, complete the

following steps:a. From the Common Actions menu, select Change Status.b. In the New Status field on the Change Status window, specify Planning.c. Click OK.

6. Select the Specifications and Presentation tab.7. In the Specifications section, expand the AWS_KEY_PAIR attribute.8. In the Default Value field, specify a value for the key pair.9. Optional: If needed, specify default values for other specification attributes,

such as the image ID or region.10. Optional: In the Presentations section, you can change the default to show the

key pair or the instance count.11. From the Common Actions menu, select Change Status and change the status

to ACTIVE as described in step 5.

Results

The sample offering is now ready. Users can request deployment of a VM instanceof Red Hat Enterprise Linux 64-bit to Amazon EC2.


Chapter 6. Using the integration

After the SmartCloud Control Desk Amazon EC2 integration is configured, userscan request VM deployments and check on the status of their requests. After theVMs are deployed, users can start, stop, and delete VM instances as needed.

Requesting a virtual machine instance on Amazon EC2In the Self Service Center or in the Offerings application, SmartCloud Control Deskusers can request deployment of an Amazon EC2 VM.

Procedure1. Log in to SmartCloud Control Desk and go to Self Service > Self Service

Center.2. Select Request a new Service.3. In the Services list, select Amazon Web Services.

4. Specify the catalog offering that you want to request, in this case Deploy RedHat Enterprise 64-bit on Amazon EC2.

5. In the Instance Type field of the offering window, specify the type of instance.


6. In the Instance Name field, specify the name of the instance. The instancename that you specify is used for the CI name when the CI is created for thedeployed instance.

7. Add the request to your cart or click Order Now.8. In the Request Submitted window, click OK.

Viewing the status of a deployment requestUsers can view the status of requests to deploy a VM on Amazon EC2 in the SelfService Center.

Procedure1. In SmartCloud Control Desk, go to Self Service > Self Service Center.2. In the My Requests list, select the request that you want to view.

3. In the View Service Request window, review the status of the service request.The Status field displays the current status, and the progress bar tracks theprogress of the request. You can also view additional details on the Log tab.

4. Click OK to close the window.

Starting, stopping, or deleting VM instancesIn the Self Service Center users can stop, start, or delete VMs that are deployedtoAmazon EC2.


About this task

When a VM instance is deployed to Amazon EC2, a configuration item (CI) iscreated for the VM. By default, the status of the CI is Not Ready.

When you delete a VM, the following rules govern how the deletion is completed:v If the CI has a status of Not Ready, deleting the VM instance terminates the VM

on Amazon EC2 but does not change the status of the CI that was created forthat instance to Decommissioned. Administrators can go to the ConfigurationItems application and change the status manually.

v If the CI has a status of Operating or any other status for which it is valid tochange the status to Decommissioned, the status of the CI is changed toDecommissioned.

A CI for a VM instance will be displayed in the My Resources navigator until theCI is decommissioned even if the VM instance is terminated on Amazon EC2.When you delete a VM, ensure that the status of the CI is Operating or anotherstatus that can be automatically decommissioned so that the CI for your VMinstance will be decommissioned.

The following instructions explain how to start, stop, or delete a VM instance inthe My Resources navigator in the Self Service Center.

Procedure1. In the Self Service Center, select My Resources.2. In the Resources panel, select Virtual Machines.

3. In the Virtual Machines panel, select the virtual machine that you want tomanage.

4. In the Actions menu, select the action that you want to perform. For example,Start Virtual Machine.

Chapter 6. Using the integration 25

5. Click Refresh to see the status of the action.


Chapter 7. Administering virtual machine deployments

Administrators can create new catalog offerings based on the sample that isprovided with the Amazon EC2 integration. Administrators can also troubleshootfailed deployments, and they can manage VM instances on Amazon EC2 just asthey manage other CIs.

Creating new catalog offerings for Amazon EC2 VMsAt installation, this content package provides a sample catalog offering that candeploy an instance of Red Hat Enterprise Linux on Amazon EC2. You can createnew offerings in your enterprise using the sample as a template.

Before you begin

Before you set up the offering, make sure that you have an Amazon MachineImage (AMI) created for it and the security credentials and key pairs that arerequired for your implementation.

Procedure1. Log in to SmartCloud Control Desk as the Service Catalog administrator.2. Go to Service Request Catalog > Offerings.3. Click Filter and search for aws.4. Open AWS_DEPLOY_RH64, the Deploy Red Hat Enterprise 64-bit on

Amazon EC2 offering.5. From the More Actions menu, select Duplicate an Offering.6. On the Offerings tab, enter a name, a description, and a long description for

your offering.7. Optional: In the Fulfillment Time field, enter the estimated deployment time.

This value has no effect on the real deployment. It is an indicator to tell theuser how long the deployment takes to complete. The default is 10 minutes.

8. To create a new classification for the offering, complete the following steps:a. In the Classification field, click the Detail Menu and select Go to

Classifications.b. In the Classifications application, from the More Actions menu, select

Duplicate Classification.c. In the Classifications field, enter a name for the new classification, for

example SCCD_AWS_WIN, a description, and a long description.d. In the Description field, replace Deploy Red Hat Enterprise 64-bit on

Amazon EC2 with the appropriate description and long description foryour classification.

e. Click Yes if you receive a message indicating that the classification is notvalid and asking whether you want to create a new classification.

f. Save the record.g. Click Return with Value to return to the Offerings application.

9. In the Specifications and Presentation sections of the Specifications andPresentation tab, specify attributes for your environment, as shown in thefollowing example.


The following table describes the attributes of the sample offering that isprovided for the SmartCloud Control Desk Amazon EC2 integration.

Table 1. Attributes defined for the integration

Attribute Description

AWS_IMAGE_ID Amazon Machine Image specified for theoffering.

AWS_REGION Amazon EC2 region for the offering. Eightregions are predefined for the integration.us-west-2 is the default for the offering.

AWS_SECURITY_GROUP Amazon EC2 security group that isassociated with the offering. Two securitygroups are predefined for the integration:default and quick-start-1. default is thedefault for the offering.

AWS_INSTANCE_TYPE Amazon EC2 instance type for the offering.Five types are predefined. The types arevisible to the end user.

AWS_NAME Amazon EC2 name that is associated withthe offering.

AWS_KEY-PAIR Amazon EC2 key pair for the offering. Nokey pairs are predefined for the integrationoffering. Deployment is still successful if nokey pair is added here.

AWS_INSTANCE_COUNT Specifies the number of instances to deploy.1, 2 and 3 are valid selections. The defaultfor the offering is 1.

AWS_ENDPOINT Specifies the SmartCloud Control Desk endpoint to use for the offering.

10. To add the offering to the Offerings Catalog, complete the following steps:a. From the More Actions menu, select Add Offering to Catalog.


b. In the Add to Catalogs window, select Add to Catalog.11. From the Common Actions menu, select Change Status and change the status

of the offering to Active.12. Go the Response Plans application, modify the AWSDEPLOY response plan to

specify the classification that you created for the new offering.13. Optional: If the existing job plan does not meet your requirements, modify the

AWSDEPLOY job plan. For more information about modifying job plans, seethe Job Plans application documentation in the SmartCloud Control DeskInformation Center.

Troubleshooting failed VM deploymentsIn the Activities and Tasks application, administrators can view information thathelps troubleshoot failed VM deployments.

Procedure1. In SmartCloud Control Desk, go to Work Orders > Activities and Tasks. If you

are the task owner, you can select the assignment in the Inbox/Assignmentssection of the Start Center to go directly to activity records.

2. In the Activities list, locate and select the activity for the failed deployment.3. Select the Log tab for the activity.4. On the Work Log tab, expand the activity record to view detailed information

about the deployment.

Managing deployed VMs as configuration itemsAdministrators can manage VMs that are deployed in Amazon EC2 just as theymanage other CIs in SmartCloud Control Desk.

About this task

When a VM is successfully deployed to Amazon EC2, a CI is automatically createdfor the VM. The configuration item name (CINAME) is the name that the userspecified when requesting an Amazon EC2 instance. The configuration itemnumber is created as shown in the following example:

Name +AMI launch

index + Instance ID + autonumTSY_AMAZON2 0 I-1FB35028 1009

Note: IBM SmartCloud® Orchestrator users: For the Amazon EC2 integration, oneCI (CI.AMAZONCOMPUTERSYSTEM) is created for each VM instance that isdeployed. No CI is created for the Amazon Reservation. For the IBM SmartCloudOrchestrator integration, one CI (CI.VIRTUALSYSTEM) and one asset(IT/VIRTUAL RESOURCE) are created for a deployment, and one CI(CI.COMPUTERSYSTEM) is created for a VM. One deployment can create morethan one VM.

Chapter 7. Administering virtual machine deployments 29

http://pic.dhe.ibm.com/infocenter/tivihelp/v50r1/topic/com.ibm.mbs.doc/jobplan/c_job_plans_application.html

Procedure1. In SmartCloud Control Desk, go to IT Infrastructure > Configuration Items.2. On the List tab, select the configuration item that you want to work with.3. To view detailed information about the virtual machine, click Long Description

in the Configuration Item Name field.

The following table describes the configuration item details that are provided inthe long description field.

Table 2. Configuration item details

Configuration item detail Description

NAME: myinstance, Name that the user specified whenrequesting a virtual machine deployment.

INSTANCE: i-b64cf281 Amazon ID for the deployed VM instance.

AMI ID: ami-b8a63b88 Amazon machine image on the deployedinstance.

ZONE: us-west-2c Amazon region for the deployed instance.

TYPE: t1.micro Instance type for the deployed instance.

RESERVATION: r-b489e480 Amazon reservation ID for the deployedinstance. Amazon assigns a reservation IDwhen the request to launch an instance issubmitted. All instances that are created bythe same request are associated with thisreservation ID and can be retrieved by usingthe reservation ID.

SECURITY GROUPS: [{GroupName:default,GroupId: sg-89c12ae6}]

Amazon security group that is associatedwith the deployed instance.

KEY PAIR NAME: null Key pair for the deployed instance.

PUBLIC DNS: ec2-54-200-126-217.us-west-2.compute.amazonaws.com

Public DNS that Amazon allocated to thedeployed instance.

PRIVATE DNS: ip-172-31-3-123.us-west-2.compute.internal

Private DNS that Amazon allocated to thedeployed instance.

PRIVATE IP ADDRESS: 172.31.3.123 Private IP address of the deployed instance.

4. To view the public DNS of the VM, select the CI Details tab and then select theCOMPUTERSYSTEM_FQDN attribute on the Specifications tab.


Appendix. Additional reference information

This SmartCloud Control Desk offering can be customized to meet your businessrequirements. Review the information about the objects that are configured for theintegration to prepare for implementation.

“SmartCloud Control Desk objects used in the integration”

SmartCloud Control Desk objects used in the integrationThe following SmartCloud Control Desk objects are used by Amazon EC2 samplecatalog offering:

To create new catalog offerings, create new objects or modify existing objects asrequired.

Table 3. SmartCloud Control Desk objects used in the integration

SmartCloud Control Desk Function SmartCloud Control Desk Object

Offering Classification SCCD_AWS\SCCD_AWS_RH64\

Change workflow pmchgmain1

Response plan AWSDEPLOY, owner MAXADMIN

Job plan AWSDEPLOY, owner MAXADMIN. Use theclassification, SCCD_AWS_RH64_JP.

Deployment workflow AWSDEPLOY

CI classification CI.AMAZONCOMPUTERSYSTEM

Escalation AWSPOLLSTATUS

SmartCloud Control Desk domainsIn the Domains application, administrators define the domains for the SmartCloudControl Desk Amazon EC2 integration.

The following table describes the domains that are predefined for the integration.Administrators can customize them to meet their business needs.


Table 4. Domains defined for the integration

Domain Description

AWS_REGION Amazon EC2 region. The following eightregions are predefined for the integration:

v ap-northeast-1, Asia Pacific (Tokyo)Region

v ap-southeast-1, Asia Pacific (Singapore)Region

v ap-southeast-2, Asia Pacific (Sydney)Region

v eu-west-1, EU (Ireland) Region

v sa-east-1, South America (Sao Paulo)Region

v us-east-1, US East (Northern Virginia)Region

v us-west-1, US West (Northern California)Region

v us-west-2, US West (Oregon) Region

us-west-2 is the default.

For more information about regions, seeRegions and Availability Zones.

AWS_SECURITY_GROUP Amazon EC2 security groups. The followingtwo security groups are predefined for theintegration:

v default

v quick-start-1

default is the default.

Security groups control access to one ormore instances. Amazon EC2 users cancreate Security Groups that specify multipleaccess credentials. Security groups can alsoinclude rules that control account access. Formore information about security groups, seeAmazon EC2 Security Groups.

AWS_INSTANCE_TYPE Amazon EC2 instance types. The followingfive types are predefined:

v m1.large

v m1.medium

v m1.small

v m1.xlarge

v t1.micro

The types are visible to the end user.

For more information about instance types,see Instance Types.


http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html

Table 4. Domains defined for the integration (continued)

Domain Description

AWS_KEY-PAIR Amazon EC2 key pairs. No key pairs arepredefined for the integration offering.Deployment is still successful if no key pairis added here.

For more information about key pairs, seeAmazon EC2 Key Pairs.

AWS_INSTANCE_COUNT Specifies the number of instances to deploy.1, 2 and 3 are valid selections. The defaultfor the offering is 1.

Configuration items for deployed Amazon EC2 instancesAfter an instance is deployed to Amazon EC2, a configuration item (CI) is createdfor the instance.

By default, when you install the integration package, the system property forcreating CIs for the Amazon EC2 machine instances, pmsc.aws.createci.enabled, isset to 1. If you disable this property, (set it to 0), CIs are not created. If CIs are notcreated, users cannot view CI information in the My Resources navigator.

CIs created for Amazon EC2 virtual machine instances belong to the classificationCI.AmazonComputerSystem, which is a child to the CI.COMPUTERSYSTEMclassification. CI.AmazonComputerSystem has all the attributes ofCI.COMPUTERSYSTEM plus two additional attributes specific to the Amazon EC2instances: AMAZONCOMPUTERSYSTEM_REGION andAMAZONCOMPUTERSYSTEM_ENDPOINT. The CI is a virtual machine.

The following table describes the attributes of the CIs created for Amazon EC2instances.

Table 5. Configuration Item attributes for Amazon EC2 instances

Attribute Description

COMPUTERSYSTEM_FQDN Public DNS for the computer system.

COMPUTERSYSTEM_VMID Instance id for the computer system.

COMPUTERSYSTEM_VIRTUAL The value is 1 to specify that the computersystem is a virtual computer system.

AMAZONCOMPUTERSYSTEM_REGION Amazon EC2 region for the offering.

AMAZONCOMPUTERSYSTEM_ENDPOINT End point for the offering.

SmartCloud Control Desk uses the COMPUTERSYSTEM_VIRTUAL,AMAZONCOMPUTERSYSTEM_REGION, andAMAZONCOMPUTERSYSTEM_ENDPOINT attributes to locate and connect to theAmazon EC2 instance.

When a deployment is complete, the public DNS is shown in the work log, alongwith the instance ID.

When the integration is installed, the Amazon EC2 product is added to the OMPtable. The name AWS EC2 is stored in the system properties filepmsc.aws.omp.name. When a CI is created, the name in system properties file isused to retrieve the ompguid (AWSEC2OMP) in the OMP table. The cinum and

Appendix. Additional reference information 33

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html

ompguid are saved in the OMPAUTHCIRLN table. The My Resources navigatoruses the cinum/ompguid string in the table as well as the attributes in the CI todetermine which AMAZON EC2 workflow or action to call for a CI.

Deployment scriptsThe following automation scripts are used for deploying virtual machine instancesto Amazon EC2:

Table 6. Amazon EC2 deployment scripts

Script Description

awsdeploy This script sends a deployment request andsaves the reservation ID in the Activities andTasks application.

awsgetstatus This script retrieves the status. It is called bythe work flow when the escalation timerexpires.

awsec2 (common) This script appends the jython path tosys.path, retrieves the credentials from theendpoint, and sends the connection requestto Amazon EC2. (If the default jython pathis not in c:\jython\lib, customers can changethe path in the awsec2 automation script).

awsofferinghelp (common) This script is called by awsdeploy andawsgetstatus. It provides a number offunctions, including retrieving attributesfrom the offering or activity and logging anentry to SR/Activity work log.

awsrelatedrecord This script is called by awsgetstatus to createthe CI and OMPAUTHCIRLN record.

To troubleshoot the automation scripts, set the autoscript logger level DEBUG. Toset the logger level, complete the following steps:1. Go to System Configuration > Platform Configuration > Logging.2. Search for the logger autoscript and expand the row for that logger.3. In the Logger Level field, specify DEBUG.4. From the More Actions menu, select Apply Settings.

SmartCloud Control Desk end pointsIn the End Points application, specify the account credentials for connecting toAmazon EC2.

Security credentials that you specify for your Amazon EC2 account control accessto the account, providing both an Access Key ID and a Secret Access Key.

SmartCloud Control Desk maintains the access credentials for the Access Key IDand Secret Access Key in the End Points application. The end points control accessto the Amazon API. By default, the end points are not visible to end users.

Administrators can specify multiple end points with different security credentialsand assign them to different offerings.


You can add end points in the Specifications section on the Specifications andPresentation tab in the Offerings application.

Note that the Select Value option in the drop-down menu for the Default Valuefield does not work. Please use Go to End Points instead.

Appendix. Additional reference information 35

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONALBUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Amazon Web Services, the “Powered by Amazon Web Services” logo, AmazonEC2, Amazon Elastic Compute Cloud, and AWS are trademarks of Amazon.com,Inc. or its affiliates in the United States and/or other countries.

Java™ and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other product and service names might be trademarks of IBM or other companies.

Notices 39

��

Printed in USA

Content Package:Amazon Elastic Compute Cloud (EC2) Integration · in Amazon EC2 through the...

Documents

Transcript of Content Package:Amazon Elastic Compute Cloud (EC2) Integration · in Amazon EC2 through the...