Sweet Security
Purpose
Synchronizes runtime vulnerabilities, attack chains, and AWS account and organization connections from Sweet Security so runtime detections appear alongside the rest of your environment.
tip
Secret fields below accept either an AWS Secrets Manager ARN or a value pasted directly into Subimage's managed vault. See Secrets for details.
Required Fields
| Field | Secret? | Description |
|---|---|---|
sweet_api_key |
Yes | Sweet Security API key: its AWS Secrets Manager ARN, or the value pasted into the vault |
sweet_api_secret |
Yes | Secret paired with the API key: its AWS Secrets Manager ARN, or the value pasted into the vault |
sweet_tenant_id |
No | Stable identifier for your Sweet Security tenant, such as its tenant name |
sweet_api_url |
No | Sweet Security API origin (default https://eapi.sweet.security) |
Setup Steps
- In the Sweet app, click your name, then click Settings.
- Click API Tokens and create a token with a read-only role and an expiration date.
- Copy the API key and its secret.
- In Subimage, set
sweet_api_key,sweet_api_secret, andsweet_tenant_id, then save the module.
Notes
- The sync is read-only. The token's role needs read access to AWS accounts (
GET /v1/aws/account), AWS organizations (GET /v1/aws/organization), vulnerabilities (GET /v1/vulnerability), and attacks (GET /v1/attack). sweet_tenant_ididentifies the tenant in the graph and scopes cleanup. Keep the same value for every sync.- Subimage exchanges the key and secret for a short-lived token on each sync.
Troubleshooting
Sync fails with 401. The API key or secret is wrong, or the token has expired. Create a new API token and update both fields in Subimage.
Sync fails with 403. Give the token's role read access to the endpoints listed in Notes.