Documentation Index
Fetch the complete documentation index at: https://docs.stigg.io/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Use this guide to request short‑lived AWS credentials for a customer’s event queue via the Stigg Edge API. These credentials can be used to access the queue (e.g., read messages) without sharing long‑lived AWS keys.Use cases
- Poll or consume the customer’s provisioned SQS queue from a backend worker.
- Rotate access automatically by renewing short‑lived credentials.
Endpoint
Required header
X-API-KEY— A full access key or a scoped key with the Event Queue: Read permission.
Query parameters
queueUrl(required): The SQS queue URL that was provisioned for the customer.durationSeconds(optional): Lifespan of the temporary credentials.- Range: 900-3600 seconds (15 minutes-1 hour)
- Default: 3600 seconds (1 hour)
queueUrl + account + environment. The request must be made with a key that belongs to the same account/environment where the queue was provisioned.
Example request (cURL)
STIGG_API_KEY can be either a full access key or a scoped key with the Event Queue: Read permission. Using a scoped key is recommended for environments with strict security requirements, as it limits the key’s access to only what is needed.Example response
accessKeyId,secretAccessKey, andsessionTokenare AWS STS session credentials.expirationis an ISO timestamp when the credentials become invalid. Renew before this time.
