7.1

Table Of Contents
3 Select Orchestrator > Library > Amazon Web Services > Elastic Cloud > Instances and select the Start
Instances workow in the workows folder.
4 Click Next.
5 Select EC2 Instance from the Resource type drop-down menu.
This is the name of the resource mapping you previously created.
6 Select instance from the Input parameter drop-down menu.
This is the input parameter of the resource action workow to match the resource mapping.
7 Click Next.
8 Leave the name and the description as they are.
The default name of the resource action is Start Instances.
9 Click Next.
10 Leave the elds as they are on the Form tab.
11 Click Add.
You created a resource action for starting Amazon virtual machines and you can see it on the Resource
Actions page.
What to do next
“Publish the Action for Starting Amazon Instances,” on page 347.
Publish the Action for Starting Amazon Instances
To use the newly created Start Instances resource action for post-provisioning operations on Amazon virtual
machines, you must publish it.
Prerequisites
Log in to the vRealize Automation console as an XaaS architect.
Procedure
1 Select Design > XaaS > Resource Actions.
2 Select the row of the Start Instances resource action, and click Publish.
The status of the Start Instances resource action changes to Published.
What to do next
Add the start instances action to the entitlement that includes the Amazon catalog item. See “Entitle Users to
Services, Catalog Items, and Actions,” on page 366.
Troubleshooting Incorrect Accents and Special Characters in XaaS Blueprints
When you create XaaS blueprints for languages that use non-ASCII strings, the accents and special
characters are displayed as unusable strings.
Cause
A vRealize Orchestrator conguration property that is not set by default, might be enabled.
Solution
1 On the Orchestrator server system, navigate to /etc/vco/app-server/.
Chapter 4 Providing On-Demand Services to Users
VMware, Inc. 347