6.2
Table Of Contents
- IaaS Configuration for Cloud Platforms
- Contents
- IaaS Configuration for Cloud Platforms
- Configuring IaaS
- Configuring IaaS for Cloud Checklist
- Custom Properties in Machine Provisioning, Blueprints, and Build Profiles
- Bringing Resources Under vRealize Automation Management
- Configure Machine Prefixes
- Create a Business Group
- Managing Key Pairs
- Cloud Reservations
- Optional Configurations
- Preparing for Provisioning
- Choosing a Cloud Provisioning Scenario
- Preparing for Amazon Provisioning
- Preparing for OpenStack Provisioning
- Preparing for Virtual Machine Image Provisioning
- Preparing for Linux Kickstart Provisioning
- Preparing for WIM Provisioning
- Creating a Cloud Blueprint
- Configuring Advanced Blueprint Settings
- Managing Cloud Infrastructure
- Monitoring Workflows and Viewing Logs
- Machine Life Cycle and Workflow States for Cloud Platforms
Using Optional Amazon Features
vRealize Automation supports several Amazon features, including Amazon Virtual Private Cloud, elastic
load balancers, elastic IP addresses, and elastic block storage.
Using Security Groups for Amazon Web Services
A security group acts as a firewall to control access to a cloud machine.
A fabric administrator specifies at least one security group when creating an Amazon EC2 reservation.
Each available region requires at least one specified security group. The reservation form displays the
security groups that are available to an Amazon Web Services account region. Every region includes at
least the default security group.
Administrators can use the Amazon Web Services Management Console to create additional security
groups, configure ports for Microsoft Remote Desktop Protocol or SSH, and set up a virtual private
network for an Amazon VPN.
For information about creating and using security groups in Amazon Web Services, see Amazon
documentation.
Understanding Amazon Web Service Regions
Each Amazon Web Services account is represented by a cloud endpoint. When you create an
Amazon Elastic Cloud Computing endpoint in vRealize Automation, regions are collected as compute
resources. After the IaaS administrator selects compute resources for a business group, inventory and
state data collections occur automatically.
Inventory data collection, which occurs automatically once a day, collects data about what is on a
compute resource, such as the following data:
n
Elastic IP addresses
n
Elastic load balancers
n
Elastic block storage volumes
State data collection occurs automatically every 15 minutes by default. It gathers information about the
state of managed instances, which are instances that vRealize Automation creates. The following are
examples of state data:
n
Windows passwords
n
State of machines in load balancers
n
Elastic IP addresses
A fabric administrator can initiate inventory and state data collection and disable or change the frequency
of inventory and state data collection.
IaaS Configuration for Cloud Platforms
VMware, Inc. 43