7.4

You can use an existing security group component to add an NSX security group to the design canvas
and configure its settings for use with vSphere machine components and Software or XaaS components
that pertain to vSphere.
By default, security groups that are applicable to the current tenant are exposed when authoring a
blueprint. Specifically, security groups are made available if the associated endpoint has a reservation in
the current tenant. For additional information about controlling tenancy access, see Controlling Tenant
Access for Security Objects.
Prerequisites
n
Create and configure a security group in NSX. See Configuring vRealize Automation and NSX
Administration Guide.
n
Verify that the NSX inventory has executed successfully for your cluster.
To use NSX configurations in vRealize Automation, you must run data collection.
n
Review security component concepts. See Using Security Components in the Design Canvas.
n
Log in to vRealize Automation as an infrastructure architect.
n
Open a new or existing blueprint in the design canvas by using the Design tab.
Procedure
1 Click Network & Security in the Categories section to display the list of available network and
security components.
2 Drag an Existing Security Group component onto the design canvas.
3 Select an existing security group from the Security Group drop-down menu.
4 Click OK.
5 Click Finish to save the blueprint as draft or continue configuring the blueprint.
You can continue configuring security settings by adding additional security components and by selecting
settings in the Security tab of a vSphere machine component in the design canvas.
Add an On-Demand Security Group Component
You can add an on-demand NSX security group component to the design canvas in preparation for
associating its settings to one or more vSphere machine components or other available component types
in the blueprint.
When you create an on-demand security group you add security policies to create the group. The security
policies can be globally exposed or hidden by default. Policies are only exposed in tenants for which the
associated NSX endpoint has a reservation in that tenant.
By default, security groups that are applicable to the current tenant are exposed when authoring a
blueprint. Specifically, security groups are made available if the associated endpoint has a reservation in
the current tenant. For additional information about controlling tenancy access, see Controlling Tenant
Access for Security Objects.
Configuring vRealize Automation
VMware, Inc. 405