Minimum Permissions Required for Cloud Connect
The read-only access SeqOps needs on AWS, Azure and Google Cloud, for security reviewers.
SeqOps needs read-only access to each cloud environment. The table below summarises the access per provider for security reviewers. The step-by-step setup is shown in the SeqOps app when you connect an account.
Access by Provider
| Provider | What you create | Read-only access granted |
|---|---|---|
| AWS | A read-only IAM role for SeqOps | SecurityAudit + ViewOnlyAccess (or ReadOnlyAccess) on the role |
| Azure | An app registration with a client secret | Reader on the target subscription |
| GCP | A service account with a JSON key | Viewer, with the Cloud Resource Manager, Compute Engine and Service Usage APIs enabled |
Notes for Security Reviewers
- •Every connection is read-only. SeqOps can't change your cloud configuration.
- •The credentials you enter in SeqOps are encrypted before they're saved.
- •Azure: the connection stops working when the client secret expires, so note the expiry date and renew it in time.
- •GCP: the Cloud Resource Manager and Compute Engine APIs are off by default on new projects (Service Usage is on by default). If one of them is disabled, the connection test still succeeds but SeqOps can't see everything, so coverage is partial. Enable them before you connect.
After You Connect
Each AWS account, Azure subscription, or GCP project counts as one cloud environment on your plan — see What Counts as a Cloud Environment.
Need Help?
If the connection test fails, contact support@seqops.io or use the Contact Us page with the provider name and the exact validation error.