Deploying automations
After you create and test your automations in Amazon Quick Automate, the next step is to deploy them so they can run regularly on a trigger. Deployment makes the automation operational and ready for execution. You can add a trigger to a deployed automation to run it at a predefined schedule. Deployment involves configuring runtime settings, assigning users for human-in-the-loop tasks, verifying credentials and integrations.
This section explains each step of the deployment process and how to configure your automation for reliability, security, and optimal performance.
Prerequisites
Before deploying your automation, ensure that the following steps are complete:
Automation is tested thoroughly - Validate your automation through end-to-end testing to confirm that all logic, actions, and agent interactions work as expected.
Version committed for deployment - Only committed automation versions can be deployed. Review your changes, finalize the version, and commit it before proceeding.
Integrations configured - If your automation interacts with external applications such as Salesforce or Jira via APIs, make sure all necessary integrations are configured.
Navigate to Connections → Integrations in the left panel to create new integrations.
Currently, only integrations available under the Actions tab are supported in Amazon Quick Automate.
Once an integration action is created, associate it with the Automation Group where it will be used.
The associated actions will then appear in the canvas. During deployment, you can select the appropriate connection to be used by the deployed automation.
Credentials configured - Verify that all credentials required by your automation are correctly set up.
Deploying an automation
You can deploy an automation directly from the Canvas by clicking Deploy, or by navigating to the Deployment tab on the automation's landing page. Once you initiate deployment, the system guides you through a series of steps to complete the configuration and release process.
Release details
On the Release Details page, select the version of the automation you want to deploy. Only committed versions are available for deployment and will appear in the dropdown list.
Additional settings
Additional settings include:
Runtime configuration
Tasks (for HITL assignments)
Access
Runtime configuration
Runtime configurations are parameters that may differ between environments such as development, testing, and production.
For example, an automation step that sends an email may use your personal email address during testing but should switch to a shared team address in production. Such environment-dependent values can be defined as runtime configurations when authoring the automation.
At deployment time, you can review and override these configurations to ensure the automation runs correctly in the intended environment. Runtime parameters can include:
Email addresses or notification recipients
File paths or URLs specific to the environment
This flexibility helps maintain a single automation definition across environments while adapting key parameters as needed.
Tasks
Select the resolver users or user groups for each of the tasks that require human-in-the-loop.
Access (Credentials and Connections)
Automations often need to connect to external systems, databases, or services. Amazon Quick Automate provides secure methods for managing credentials and connections without embedding sensitive information within your automation logic.
Connection and credential data are securely stored and encrypted, and made available to workflows at runtime without exposing them to authors or end users. This design ensures strong separation of secrets from automation definitions, improving both security and maintainability.
You can store and use two primary types of credentials:
Website credentials - Used for UI automation steps that require website logins (username and password).
Action credentials (Integrations) - Used for connecting AWS services (e.g. S3) or external systems through configured integrations (e.g., Salesforce, Jira).
At deployment, ensure that the correct credentials and connections are selected so the automation can access all required systems securely and successfully.
Setting up triggers
Triggers determine when and how your automations run. You can configure automations to start based on a predefined schedule. To setup a trigger:
On the Deployment page, click "Create Trigger" and configure the rules.
Select the frequency
Select the start date and time (Note that the actual execution will initiate within 15 minutes of the start time selected)
Select the end date and time
Select the timezone
Amazon Quick Automate provided built-in scalability. Select the number of parallel executions of the automation (you can select a maximum of 10 parallel executions per trigger and 50 across all automations within an account. Please reach out to AWS)
For complex scheduling needs, you can use cron expressions to define precise running patterns. For example, to run an automation at 2:30 AM every Monday, Wednesday, and Friday, you would use the cron expression:
30 2 * * 1,3,5.
