7.1

Table Of Contents
6 Invoke the SSH Tunnel from the local network machine to the Amazon AWS tunnel machine.
ssh -N -v -o "ServerAliveInterval 30" -o "ServerAliveCountMax 40" -o "TCPKeepAlive yes” \
-R 1442:vRealize_automation_appliance_fqdn:5480 \
-R 1443:vRealize_automation_appliance_fqdn:443 \
-R 1444:manager_service_fqdn:443 \
User of Amazon tunnel machine@Public IP Address of Amazon tunnel machine
You congured port forwarding to allow your Amazon AWS tunnel machine to access
vRealize Automation resources, but your SSH tunnel does not function until you congure an Amazon
reservation to route through the tunnel.
What to do next
1 Install the software bootstrap agent and the guest agent on a Windows or Linux reference machine to
create an Amazon Machine Image that your IaaS architects can use to create blueprints. See “Preparing
for Software Provisioning,” on page 62.
2 Congure your Amazon reservation in vRealize Automation to route through your SSH tunnel. See
“Scenario: Create an Amazon Reservation for a Proof of Concept Environment,” on page 209.
Preparing Red Hat OpenStack Network and Security Features
vRealize Automation supports several features in OpenStack including security groups and oating IP
addresses. Understand how these features work with vRealize Automation and congure them in your
environment.
Using OpenStack Security Groups
Security groups allow you to specify rules to control network trac over specic ports.
You can specify security groups when creating a reservation and also in the blueprint canvas. You can also
specify security groups when requesting a machine.
Security groups are imported during data collection.
Each available region requires at least one specied security group. When you create a reservation, the
available security groups that are available to you in that region are displayed. Every region includes at least
the default security group.
Additional security groups must be managed in the source resource. For more information about managing
security groups for the various machines, see the OpenStack documentation.
Using Floating IP Addresses with OpenStack
You can assign oating IP addresses to a running virtual instance in OpenStack.
To enable assignment of oating IP addresses, you must congure IP forwarding and create a oating IP
pool in Red Hat OpenStack. For more information, see the Red Hat OpenStack documentation.
You must entitle the Associate Floating IP and Disassociate Floating IP actions to machine owners. The
entitled users can then associate a oating IP address to a provisioned machine from the external networks
aached to the machine by selecting an available address from the oating IP address pool. After a oating
IP address has been associated with a machine, a vRealize Automation user can select a Disassociate
Floating IP option to view the currently assigned oating IP addresses and disassociate an address from a
machine.
Configuring vRealize Automation
22 VMware, Inc.