7.1

Table Of Contents
Scenario: Configure Network-to-Amazon VPC Connectivity for a Proof of Concept
Environment
As the IT professional seing up a proof of concept environment to evaluate vRealize Automation, you want
to temporarily congure network-to-Amazon VPC connectivity to support the vRealize Automation
Software feature.
Network-to-Amazon VPC connectivity is only required if you want to use the guest agent to customize
provisioned machines, or if you want to include Software components in your blueprints. For a production
environment, you would congure this connectivity ocially through Amazon Web Services, but because
you are working in a proof of concept environment, you want to create temporary network-to-Amazon VPC
connectivity. You establish the SSH tunnel and then congure an Amazon reservation in
vRealize Automation to route through your tunnel.
Prerequisites
n
Install and fully congure vRealize Automation. See Installing and Conguring vRealize Automation for the
Rainpole Scenario.
n
Create an Amazon AWS security group called TunnelGroup and congure it to allow access on port 22.
n
Create or identify a CentOS machine in your Amazon AWS TunnelGroup security group and note the
following congurations:
n
Administrative user credentials, for example root.
n
Public IP address.
n
Private IP address.
n
Create or identify a CentOS machine on the same local network as your vRealize Automation
installation.
n
Install OpenSSH SSHD Server on both tunnel machines.
Procedure
1 Log in to your Amazon AWS tunnel machine as the root user or similar.
2 Disable iptables.
# service iptables save
# service iptables stop
# chkconfig iptables off
3 Edit /etc/ssh/sshd_config to enable AllowTCPForwarding and GatewayPorts.
4 Restart the service.
/etc/init.d/sshd restart
5 Log in to the CentOS machine on the same local network as your vRealize Automation installation as
the root user.
Chapter 1 External Preparations for Provisioning
VMware, Inc. 21