Skip to content
    Onboarding

    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

    ProviderWhat you createRead-only access granted
    AWSA read-only IAM role for SeqOpsSecurityAudit + ViewOnlyAccess (or ReadOnlyAccess) on the role
    AzureAn app registration with a client secretReader on the target subscription
    GCPA service account with a JSON keyViewer, 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.

    permissionsiamawsazuregcpleast privilegecloud connect

    We use cookies

    We use essential cookies to run this site. With your permission, we'd also like to use analytics cookies to see how the site is used, and functional cookies for chat and videos. Change your choice any time under Cookie settings. Read our Cookies Policy