VMware

VMware vCenter Orchestrator Plug-In for Amazon Web Services 1.0 Release Notes

VMware vCenter Orchestrator Plug-In for Amazon Web Services 1.0 | 22 April 2014 | Build 1729926

VMware vCenter Orchestrator 5.5.1 | 11 March 2014 | Build 1617131

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Introduction to the VMware vCenter Orchestrator Plug-In for Amazon Web Services

The Orchestrator Plug-In for Amazon Web Services (AWS) exposes the functionality of the Amazon Elastic Cloud. The plug-in's API exposes the AWS API and lets workflow developers create content similar to the content created through the AWS Java SDK. In addition to creating their own content for specific usecases, workflow developers can search the AWS documentation for exisiting solutions.

To use the Orchestrator Plug-In for AWS, you must be familiar with the AWS and the Amazon Elastic Compute Cloud web service. For information on AWS, see the Amazon Web Services General Reference.

Top of Page

Installing the VMware vCenter Orchestrator Plug-In for AWS

You must use the Orchestrator configuration interface to install the plug-in.

Functional Prerequisites

Version 1.0 of the plug-in works with vCenter Orchestrator 5.5.1 and Java AWS SDK 1.7.0.

 

Install the Orchestrator Plug-In for AWS

  1. Download the .vmoapp file from the Orchestrator Plug-In for AWS download page.
  2. Log in to the Orchestrator configuration interface at http://orchestrator_server:8282.
  3. On the General tab, click Install Application.
  4. Upload the Orchestrator Plug-In for Amazon Web Services.
    1. Click the magnifying glass icon.
    2. Select the .vmoapp file to install.
    3. Click Open.
    4. Click Install.
  5. On the Startup Options tab, click Restart service to complete the plug-in installation.

Top of Page

Configuring the VMware vCenter Orchestrator Plug-In for AWS

By using the Configuration workflows in the Orchestrator Plug-In for AWS, you can add, update, and remove AWS accounts. For the initial account configuration, you must use access keys (Access Key ID and Secret Access Key) as security credentials in order to sign AWS API requests.

A region is a named set of AWS resources in the same geographical area. Regions are exposed as objects in the root directory of the Orchestrator inventory. When an account is created, it has an associated client for each region.

Add an Amazon account

Prerequisites

  • You must have an active AWS account. An AWS account is an Amazon account, which is enabled to use AWS products.
  • You must have valid access and secret keys in order to sign programmatic requests that Orchestrator makes to AWS. You can create access keys by using the AWS Management console. It is recommended to use IAM access keys instead of AWS root account access keys. IAM lets you securely control access to AWS services and resources in your AWS account.
  • You must have permissions to add AWS accounts.
To add an AWS account
  1. Log in to the Orchestrator client as an administrator.
  2. Click the Workflows view in the Orchestrator client.
  3. In the hierarchical list of workflows, select Library > Amazon Web Services > Configuration and navigate to the Add Amazon account workflow.
  4. Right-click the Add Amazon account workflow and select Start workflow.
  5. Specify the properties of the account you want to add.
    Option Action
    Account name Type a unique name for the account you want to add.
    AWS access key Type the access key that you created with your Amazon account.
    AWS secret key Type the secret key that you created with your Amazon account.
    Connection timeout in seconds Type the connection timeout of the HTTP client in seconds. The default value is 50.
    Socket timeout in seconds Type the socket timeout. The default value is 50.
    Maximum number of open HTTP connections Type the maximum number of HTTP connections. The default value is 50.
    Maximum number of retry attempts for failed retryable requests Type the maximum number of retries for failed requests. The default value is -1 and it indicates that you want to use the default policy of the SDK.
    Proxy host to connect through Type the proxy host if you are using a proxy connection.
    Port on the proxy host to connect through Type the proxy port if you are using a proxy connection.
    User name to use when connecting through a proxy Type the proxy username if you are using a proxy connection.
    Password to use when connecting through a proxy Type the proxy password if you are using a proxy connection.
    Windows domain name for configuring NTLM proxy support Type the Windows domain name if you are using NTLM as an authentication mechanism.
    Windows workstation name for configuring NTLM proxy support Type the workstation name if you are using NTLM as an authentication mechanism.
  6. Click submit to run the workflow

Top of Page

Using the VMware vCenter Orchestrator Plug-In for AWS

You can use the workflows in the VMware vCenter Orchestrator Plug-In for AWS to expose the functionality of the Amazon Elastic Compute Cloud. To access these workflows, navigate to Library > Amazon Web Services > Elastic Cloud. The workflows of the plug-in are grouped in the following categories:

  • Addresses
  • Gateways
  • Images
  • Instances
  • Key Pairs
  • Network ACLs
  • Network Interfaces
  • Routes
  • Route Tables
  • Security Groups
  • Snapshots
  • Subnets
  • Volumes
  • VPCs
  • VPN Connections

Top of Page