orchestrator
latest
false
- 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
- Solutions
- Audit
- Settings
- Cloud robots
- Automation Suite Robots
- Folders Context
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Indexes
- Queues
- Assets
- Connections
- Business Rules
- Storage Buckets
- MCP Servers
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting

Orchestrator user guide
Last updated Apr 17, 2026
Storing Assets in AWS Secrets Manager (read only)
Note:
Make sure you have configured the AWS Secrets Manager integration.
To store an asset of the type Credential or Secret in the read-only version of the AWS Secrets Manager, create a secret in AWS, using the Other type of secret option. The secret must include the following keys, with their corresponding values:
- For
Credential-type assets:- Username - the username of the credentials.
- Password - the password of the credentials.
In the AWS Secrets Manager console, you can also store these key/value pairs as a JSON string, in the following format: {"Username":"username","Password":"password"}
- For
Secret-type assets:- Username - the name of the asset.
- Password - the value of the secret.
In the AWS Secrets Manager console, you can also store these key/value pairs as a JSON string, in the following format: {"Username":"assetname","Password":"secretvalue"}