Skip to main content
Create dedicated provider credentials for Merops and grant only the access needed for your workflow. In broad terms, browsing requires bucket/object listing; migration requires source reads and destination writes, and may require destination bucket creation. Strict synchronization additionally requires deleting destination-only objects. Credential uploads are encrypted with a per-user key before being stored in the configured Google Cloud Storage bucket. During use, the backend decrypts the file in memory and gives credential content to the corresponding provider adapter. The implementation retains provider connection state in runtime memory and a cached provider key in application storage. Revoke or rotate credentials using the provider’s console. Deleting the Merops provider record is not a substitute for revoking a provider key. The repository does not define an exact least-privilege IAM policy for each workflow; validate permissions with your cloud administrator.