You can create an endpoint to connect to an Amazon instance. You can optionally associate proxy settings to the Amazon endpoint by associating to a Proxy endpoint.
About this task
vRealize Automation provides several Amazon 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.
For information about associating proxy settings to your endpoint, see Create a Proxy Endpoint and Associate to a Cloud Endpoint.
Log in to the vRealize Automation console as an IaaS administrator.
If you want to configure additional security and force connections to pass through a proxy server, create a Proxy endpoint. You can associate to the Proxy endpoint as you create the Amazon endpoint. See Create a Proxy Endpoint and Associate to a Cloud Endpoint.
- Select .
- Select .
- Enter a name and, optionally, a description.
Typically this name indicates the Amazon account that corresponds to this endpoint.
- Enter the administrative-level access key ID for the Amazon endpoint.
Only one endpoint can be associated with an Amazon access key ID.
To obtain the access key needed to create the Amazon endpoint, you must either request a key from a user who has AWS Full Access Administrator credentials or be additionally configured with the AWS Full Access Administrator policy. See Amazon documentation for details.
- Enter the secret access key for the Amazon endpoint.
- (Optional) Click Properties and add supplied custom properties, property groups, or your own property definitions for the endpoint.
- (Optional) To configure additional security and force connections to pass through a proxy server, click Associations and associate to an existing Proxy endpoint.
You must have at least one Proxy endpoint to create an association.
- Click OK.
After you create the endpoint, vRealize Automation begins collecting data from the Amazon Web Services regions.
What to do next
Add the compute resources from your endpoint to a fabric group. See Create a Fabric Group.