orchestrator
2024.10
true
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Audit
- Resource Catalog Service
- Automation Suite robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Integrations
- Troubleshooting
Orchestrator User Guide
Last updated Nov 13, 2024
Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
Note: Make sure you have configured the AWS Secrets Manager integration.
To store an unattended robot password in the read-only version of AWS Secrets Manager, create a secret in AWS, using the Other type of secret option.
This needs to include a Value key, whose value represents the robot password.
In the AWS Secrets Manager console, these key/value pairs can also be stored as a JSON string:
