7.0

Table Of Contents
Procedure
1 Select Infrastructure > Endpoints > Endpoints.
2 Select New Endpoint > Cloud > Amazon EC2.
3 Enter a name and, optionally, a description.
Typically this name indicates the Amazon Web Services account that corresponds to this endpoint.
4 Select the Credentials for the endpoint.
Only one endpoint can be associated with an Amazon access key ID.
5 (Optional) Click the Use proxy server checkbox to configure additional security and force
connections to Amazon Web Services to pass through a proxy server.
a Enter the host name of your proxy server in the Hostname text box.
b Enter the port number to use for connecting to the proxy server in the Port text box.
c (Optional) Click the Browse icon next to the Credentials text box.
Select or create credentials that represent the user name and password for the proxy server, if
required by the proxy configuration.
6 (Optional) Add custom properties.
7 Click OK.
After the endpoint is created, vRealize Automation begins collecting data from the Amazon Web Services
regions.
What to do next
vRealize Automation provides several Amazon Web Services instance types for you to use when creating
blueprints, but if you want to import your own instance types see Add an Amazon Instance Type.
Add the compute resources from your endpoint to a fabric group. See Create a Fabric Group.
Add an Amazon Instance Type
Several instance types are supplied with vRealize Automation for use with Amazon blueprints. An
administrator can add and remove instance types.
The machine instance types managed by IaaS administrators are available to blueprint architects when
they create or edit an Amazon blueprint. Amazon machine images and instance types are made available
through the Amazon Web Services product.
Prerequisites
Log in to the vRealize Automation console as an IaaS administrator.
Procedure
1 Click Infrastructure > Administration > Instance Types.
2 Click New Instance Type.
Configuring vRealize Automation
VMware, Inc. 175