Configuring the Amazon EC2 provider with AWS accounts

The AWS accounts, represented by aliases in BMC Cloud Lifecycle Management, serve to perform specific functions in the Amazon cloud based on requests sent by BMC Cloud Lifecycle Management. The following sections provide account configuration instructions:

• • To add an account
  • To edit an account
  • To delete an account
  • Where to go from here

Amazon Elastic Compute Cloud (Amazon EC2) accounts are based on Amazon Web Services (AWS) accounts. You use AWS accounts to create and manage Amazon EC2 instances. More specifically, AWS accounts are used to retrieve the Virtual Private Cloud in an availability zone and to provision an Amazon Machine Image (AMI) as an EC2 instance in the Virtual Private Cloud (VPC).

Organizations may want to use multiple AWS account for different reasons. For example, IT departments may serve different corporate units, each with their own AWS account. Or, for cost accounting purposes, teams may want to be responsible for paying their own AWS bills.

All AWS accounts are associated with a single Amazon EC2 provider instance. AWS accounts are not specifically linked with BMC Cloud Lifecycle Management tenants. Instead, users associated with a tenant group can use multiple AWS accounts, and a single AWS account can be used by multiple tenant users. The actions you perform on AWS accounts do not affect tenants.

When setting up your Amazon EC2 account, you enter the security credentials associated with the AWS account, specifically the certificate and the private key files of the X.509 certificate. To generate and extract the certificate and private key files, see the Amazon Web Services documentation for the X.509 certificate. See Preparing-your-Amazon-EC2-account.

The certificate and private key files are maintained in encrypted format in the BMC Cloud Lifecyle Management environment. The underlying BMC Atrium Orchestrator workflow retrieves these files from the enterprise BMC Remedy AR System server and sends them to the BMC Atrium Orchestrator EC2 adapter, which uses them to connect to the AWS API.

A master account is used in the context of a pod search to reduce the number of AWS API calls to multiple user accounts. To improve search performance, specify one account as a master account.

To add an account

1. In the Providers workspace, select Compute. Then, select an Amazon EC2 provider in the list of providers.
    The Manage EC2 User Credentials icon appears.
2. Click Manage EC2 User Credentials .
    The Manage EC2 User Credentials dialog box is opened and ready for data input.
   
   
   

3. Complete the following fields:
   

   Field	Description
   User Name	User name assigned to this AWS account. The user name serves as an alias for a set of Amazon credentials.
   Private Key	Paste the contents of the private key file generated and extracted from your AWS account.
   Certificate	Paste the contents of the X.509 certificate file generated and extracted from your AWS account.
   Master Key	Indicates whether the account is a master account.

4. Click Save and close the dialog box.

To edit an account

1. Select the user account to be edited.
2. Click the Edit User Credentials icon to enable editing of the account credentials.
3. Make the changes to the credentials, and click Update.

To delete an account

1. Select the user account to be deleted, and click the Delete User Credentials icon.
2. At the prompt, click Yes.

Where to go from here

Next, go to Creating-product-catalog-entries to create catalog entries using your AMI ID as the basis for the entry.