AWS Connections
A connection binds one AWS identity to a named scope inside the console. Ventra tests the connection when you save it, then reuses it across platform runs and Acquire kit builds.
| Field | Step | Purpose |
|---|---|---|
| Display name | Provider details | How the connection appears in dropdowns and run history |
| Alias | Provider details | Optional short tag such as Production or Forensics account |
| Account ID | Provider details | The twelve digit account identifier, used for labeling and validation |
| Access Key ID and Secret Access Key | Authenticate | Long lived or temporary STS credentials for the Credentials method |
| Session Token | Authenticate | Only for temporary credentials from an assumed role |
| Role ARN | Authenticate | The cross account role Ventra assumes for the IAM Role method |
Platform runs collect inside the Ventra backend using the saved connection. Workstation and client kit profiles export a kit zip, and credentials never travel inside the kit. The operator supplies keys through the environment or the command line on the collection host.
When you edit a connection, leave the Secret Access Key blank to keep the value already saved on the server.