With Automation Assembler, you can create extensibility actions for use in extensibility subscriptions.
Extensibility actions are highly customizable, lightweight, and flexible ways to extend application life cycles by using user-defined script code and action templates. Action templates contain predefined parameters that help set up the foundation of your extensibility action.
There are two methods of creating an extensibility action:
- Writing user-defined code for an extensibility action script.
Note: Writing user-defined code in the extensibility action editor might require an active Internet connection.
- Importing a deployment package as a ZIP package for an extensibility action. For information on creating a ZIP package for extensibility actions, see Create a ZIP package for Python runtime extensibility actions, Create a ZIP package for Node.js runtime extensibility actions, or Create a ZIP package for PowerShell runtime extensibility actions.
The following steps describe the procedure for creating an extensibility action that uses Amazon Web Services as a FaaS provider.
Prerequisites
- Membership in an active and valid project.
- Configured Amazon Web Services role for Lambda functions. For example, AWSLambdaBasicExecutionRole.
- Cloud administrator role or iam:PassRole permissions enabled.
Procedure
What to do next
After your extensibility action is created and verified, you can assign it to a subscription.
Note: Extensibility subscriptions use the latest released version of an extensibility action. After creating a new version of an action, click
Versions on the top-right of the editor window. To release the version of the action you want to use in your subscription, click
Release.