Name it clearly
Use a name that identifies the application or automation job using the key.
Scope it narrowly
Select only the services, resources, and actions that integration needs.
Protect the secret
Copy the key once, store it securely, and never share it publicly.
Create a key
- Sign in at cloudservices.ecowestern.net.
- Open the Dashboard.
- Open API Keys.
- Select Create New Key.
- Give the key a descriptive name.
- Select the services and resources it can access.
- Select the actions it can perform.
- Set an expiration date if needed.
- Create the key and copy the full secret.
Choose permissions
Use the smallest scope that fits the application. For example:- A deployment tool may need
canopy:writeandcanopy:read. - A monitoring tool may need
flow:readonly. - An application that sends requests to a function needs
flow:invoke. - A storage cleanup tool may need
clearlake:delete.
Manage existing keys
From Dashboard → API Keys, you can:- View key names, prefixes, status, expiration, and last-used time.
- Update a key’s name or expiration.
- Add or remove permission rules.
- Deactivate or reactivate a key.
- Permanently delete a key.
Permission planning
Start with the narrowest useful key and add access only when the integration needs it.
Avoid using
* for production integrations unless the integration genuinely manages every resource in the account.
Rotation workflow
- Create a replacement key with the same or narrower permissions.
- Deploy the replacement to the integration.
- Confirm that requests succeed with the replacement.
- Deactivate the old key.
- Delete the old key after the transition is complete.
