After you create a serverless runtime environment, you can perform management tasks such as editing, redeploying, or cloning the serverless runtime environment.
Except where noted, management actions described in this section apply to both AWS and Azure serverless runtime environments.
Editing a serverless runtime environment
The properties that you can edit in a serverless runtime environment vary, depending on the environment's status.
You can edit the following properties, based on the status of the serverless runtime environment:
•Up and Running. You can only update the following fields: Max Compute Units Per Task and Task Timeout. The updated values take effect for subsequent task runs.
•Failed. You can update all the properties. The updated properties take effect once you use the Redeploy (AWS) or Start environment action (Azure).
If the serverless runtime environment shows any other status, you must delete the serverless runtime environment and create a new one.
To edit a serverless runtime environment, expand the Actions menu for the serverless runtime environment and select Edit. This works for both Azure and AWS serverless runtime environments.
For serverless runtime environments created in Azure Native ISV Services, you can also use the Azure portal to edit the properties.
Redeploying a serverless runtime environment (AWS)
The redeploy action restarts the serverless runtime environment, either after a change in the environment or if the environment shuts down for a specific reason.
You might redeploy the serverless runtime environment in the following situations:
•You change your organization's licenses.
•The serverless runtime environment shuts down because the organization ran out of serverless compute units. You can add more compute units to your organization and redeploy the serverless runtime environment.
•You update the configuration in your cloud environment. For example, you update files in the supplementary file location, or you update the policy that is attached to the IAM role.
Before you redeploy a serverless runtime environment, in Monitor, be sure that no jobs are running in the runtime environment. Then, in Administrator, expand the Actions menu for the serverless runtime environment and click Redeploy.
Note: Wait until the redeployment completes before you run a mapping. Any jobs running during redeployment will fail.
Cloning a serverless runtime environment
You might clone a serverless runtime environment to create another environment that has a similar configuration. For example, you want to create a similar serverless runtime environment that connects to a different subnet in your cloud environment or uses a different security group.
Note: To clone serverless runtime environments created in Azure Native ISV Services, use the Azure portal.
To clone a serverless runtime environment, expand the Actions menu for the serverless runtime environment and select Clone.
Deleting a serverless runtime environment
Delete a serverless runtime environment when it's no longer required.
Note: To delete serverless runtime environments created in Azure Native ISV Services, use the Azure portal.
Before you delete a serverless runtime environment, perform the following tasks:
•Use Monitor to make sure that the environment is not running any jobs.
•Use the Show Dependencies action to see if the environment is being used by any tasks, mappings, or connections. If dependencies exist, remove them before deleting the environment.
To delete a serverless runtime environment, expand the Actions menu for the serverless runtime environment and select Delete.