Skip to content

Cloud accounts

A cloud account lets Seylo see what runs in one Azure subscription, one AWS account or one Google Cloud project. It is read-only, and Seylo stores no key for it: you grant a read-only role that trusts Seylo’s own identity, and you revoke it by deleting that role.

Connecting a cluster never needs a cloud account. The agent connects a cluster with no cloud access at all. See connect a cluster. A cloud account is a separate, optional connection.

Cloud accounts live on Admin → Integrations → Cloud accounts, with one card per cloud.

See What runs in the account, counted by type: Kubernetes clusters, virtual machines, databases, serverless apps, storage, registries and load balancers. Every other resource is counted as other resources. The card shows the account’s own name
Read your bill Azure, AWS and Google Cloud. What your machines, and on Azure your managed disks, on AWS your EBS volumes, on Google Cloud your Persistent Disks, actually cost you. Google Cloud needs its billing export to BigQuery turned on. See prices from your cloud bill
Help Nightshift When a failing workload’s evidence names a cloud resource - a Key Vault, a database, a storage account - Nightshift reads that resource’s settings to find the cause. See Nightshift and your cloud
Change anything in your cloud No. Seylo refuses to connect a role that can write
Read your data, secrets or keys No. Metadata only. Seylo never reads a secret value, a stored object such as a blob, a key, a token or an app setting. See what Seylo reads in your cloud
Store a key No. There is no key, client secret, certificate or service account key file at any step. Seylo signs in as itself, and your cloud gives it short-lived access each time
Revoke You do, in your cloud: delete the role, the CloudFormation stack, or the service account and pool. Seylo cannot stop you, and does not need to be told first

What Seylo stores for a connection is the account’s ids, its name, who connected it and when, and the last test result. Connecting, testing and removing are recorded in your organisation’s audit log.

Action Role
See connected cloud accounts and their last test viewer
Connect, test and remove admin

An organisation can connect up to 50 cloud accounts.

Every Seylo organisation reaches your cloud as the same Seylo identity. If the grant only trusted that identity, someone in another Seylo organisation who learned your subscription ID, account ID or project ID could connect your account to their organisation.

So each grant names your Seylo organisation, in a place that only someone who administers your cloud can write and that Seylo’s read-only role can read:

Cloud Where your organisation is named
Azure The Seylo Reader role assignment’s description, seylo-org: followed by your organisation’s ID
AWS The tag seylo-org on the role, set to your organisation’s ID
Google Cloud The service account’s description, seylo-org: followed by your organisation’s ID

The commands the portal gives you set it for you. Test refuses a grant that names no organisation or a different one, and does not say which organisation it names.

Each Seylo region also has its own identity, so a grant made for one region cannot be used by another.

The portal generates the exact commands for you, with your ids, Seylo’s identity for your region and your organisation already filled in. The commands below show their shape, with placeholders such as <subscription ID> where the portal puts real values. Copy them from the portal, not from this page.

  1. Open Admin → Integrations → Cloud accounts and choose Connect Azure, Connect AWS or Connect Google Cloud on that cloud’s card.
  2. Enter the ids the form asks for, below for each cloud, and optionally a Name; the cloud’s own name for the account is used when it is empty. On AWS and Google Cloud, leave Let Nightshift investigate cloud dependencies ticked unless you do not want it (see the Nightshift tick box). The steps to run in your cloud appear under the form once the ids look right.
  3. Run those steps in your cloud, as someone who may grant roles there.
  4. Choose Test. The result says what Seylo could and could not do, step by step, what it can see, and what Nightshift can read.
  5. When Test says Connected, choose Save.

The form asks for your Tenant ID (Microsoft Entra ID → Overview → Tenant ID, or az account show --query tenantId -o tsv) and the Subscription ID, not its name.

What you grant: Seylo’s app in your directory, and one custom role, Seylo Reader <subscription ID>, on that one subscription. It is Azure’s Reader minus every read Microsoft documents as returning a key, a token, a credential or an app setting. One role serves everything: the inventory, your bill, and Nightshift. There is no tick box on Azure. What the role holds is on what Seylo reads in your cloud.

Who can run it: someone who is Owner or User Access Administrator on the subscription. Creating a custom role needs Microsoft.Authorization/roleDefinitions/write, which those two roles hold. A Role Based Access Control Administrator, enough for the built-in Reader before, cannot create it.

  1. Add Seylo’s app to your directory. An administrator of the directory opens the consent link the portal shows, or runs:

    Terminal window
    az ad sp create --id <Seylo app ID>

    Consent lets Seylo’s app sign in to your directory and nothing more. It gives no access to any subscription; the role assignment below does that.

  2. Save the role as seylo-reader.json in the folder you run az from. The portal shows the file, with Download. It is a file, not a JSON argument, because Windows PowerShell strips the double quotes inside an argument and az would then receive invalid JSON.

  3. Create the role, and give it to Seylo’s app on the subscription, with the description that names your organisation. Keep the description exactly as shown:

    Terminal window
    MSYS_NO_PATHCONV=1 az role definition create --role-definition @seylo-reader.json
    MSYS_NO_PATHCONV=1 az role assignment create --assignee <Seylo app ID> \
    --role "Seylo Reader <subscription ID>" \
    --scope /subscriptions/<subscription ID> \
    --description seylo-org:<your organisation ID>

    MSYS_NO_PATHCONV=1 stops Git Bash on Windows from turning /subscriptions/... into a file path, which Azure then rejects with MissingSubscription. Other bash shells and Azure Cloud Shell ignore it. The PowerShell form the portal offers leaves it out, and quotes the file as '@seylo-reader.json', because a bare @ means something else in PowerShell.

    The role is named after the subscription because a custom role’s name must be unique in your directory: connecting a second subscription creates a second role.

  4. Test, then Save. A new role assignment can take up to 5 minutes to apply. If Test says No role yet, wait and press Test again.

Read-only roles only. If Seylo’s app holds any other role on the subscription that can write, or any role with a data action, Test refuses the connection and names that role. Remove it. The built-in Reader is still accepted, but Test reports it as wider than metadata-only: see move an existing connection.

Cloud accounts work with the global Azure cloud. Azure Government and Azure operated by 21Vianet are not supported.

On AWS and Google Cloud the form has one tick box, Let Nightshift investigate cloud dependencies, ticked by default. It adds the few reads Nightshift needs that the viewer grant lacks, and nothing else:

Cloud What the box adds Already in the viewer grant
AWS The inline policy seylo-nightshift-investigate: logs:StartQuery, logs:GetQueryResults, logs:StopQuery (CloudWatch Logs Insights), secretsmanager:ListSecrets, secretsmanager:DescribeSecret, secretsmanager:ListSecretVersionIds (secret names, versions and dates, never GetSecretValue), and cloudwatch:DescribeAlarms Metrics and CloudTrail event history, through ViewOnlyAccess
Google Cloud The role roles/secretmanager.viewer: secret names and versions, never their payload Logs, metrics and Admin Activity audit logs, through Viewer

Everything it adds is a read, and the same Test checks it. Untick it if you do not want it: the connection, the inventory and the bill read work exactly the same without it.

Azure has no box. The Seylo Reader role already holds what Nightshift reads: resource settings, metrics, Log Analytics and Application Insights queries, the activity log, and Key Vault secret names and dates.

Some of these reads are billed in your own cloud account, for example CloudWatch GetMetricData and Logs Insights on AWS. Nightshift reads only while it investigates, never on a schedule. The prices, with their sources, are on what reads cost in your account.

Save stays disabled until Test says Connected, and Seylo runs the test again when you save. Nothing is stored until a test has passed. A connected test reads, for example:

Connected, read-only. Seylo can see 214 resources in Acme Production and can change nothing in it.

Under the sentence, Test lists each step it ran, in order, so you can see how far it got: Seylo’s identity accepted, the account read, the role checked as read-only and naming your organisation, and the resources counted. When a count stops at a page limit, the card says there are at least that many.

Three more steps tell you about the grant without ever failing the connection:

Step ok means Otherwise
metadata-only The grant cannot read a key, token, credential or app setting. On Azure, the Seylo Reader role; on AWS, the stack’s Deny is in place wider: the grant could read more than Seylo uses, for example the built-in Reader on Azure, or a stack without the Deny on AWS. Seylo never calls those reads; the card shows the commands that narrow the grant
nightshift Nightshift can read everything it uses in this account not yet: what it cannot read, and what to run
cost-read (AWS) Seylo can read your bill from Cost Explorer list prices: why not, and what to do. Prices use AWS’s public list meanwhile
cost-read (Google Cloud) Seylo can read your billing export, from a free dry run that says what the daily read scans and costs Why not: no export yet (with the steps to create one), a table to name, or the command to run. Prices use Google’s public list meanwhile

Below them, what Nightshift can read lists the same six lines on every cloud, each yes, no or never, with an (i) that says where it is read from or what to run:

Line Azure AWS Google Cloud
Resources and their settings Azure Resource Manager ViewOnlyAccess Viewer, Cloud Asset Viewer
Metrics Azure Monitor CloudWatch Cloud Monitoring
Logs Log Analytics and Application Insights CloudWatch Logs Insights Cloud Logging
Activity (who changed what, when) The activity log, 90 days CloudTrail event history, 90 days Admin Activity audit logs
Secret metadata (names, versions, dates) Key Vault Secrets Manager Secret Manager
Secret values never never never

Secret values always reads never: it is not something Seylo can be granted. If it reads allowed instead, the grant could read keys or settings Seylo never asks for, and the metadata-only step says how to take that away.

Each line is judged from the roles Seylo read back from your cloud, not from what the steps asked for. A no never fails the connection: an account Nightshift cannot investigate is still connected, read-only and correct.

Press Test on a saved connection at any time, for example after you change the role in your cloud. Seylo does not notice such a change until a test runs.

Move an existing connection to the new grant

Section titled “Move an existing connection to the new grant”

A connection made before this release keeps working as it is. When its last Test says a Nightshift read is missing, or that the grant is wider than metadata-only, or the Test predates these checks, an admin sees a one-line note on its card with Show the command. Run what it shows (save the file first, where there is one), then press Test.

Moves the subscription from the built-in Reader to Seylo Reader. Save seylo-reader.json from the note, then run, in this order:

Terminal window
MSYS_NO_PATHCONV=1 az role definition create --role-definition @seylo-reader.json
MSYS_NO_PATHCONV=1 az role assignment create --assignee <Seylo app ID> \
--role "Seylo Reader <subscription ID>" \
--scope /subscriptions/<subscription ID> \
--description seylo-org:<your organisation ID>
MSYS_NO_PATHCONV=1 az role assignment delete --assignee <Seylo app ID> --role Reader \
--scope /subscriptions/<subscription ID>

The new role is assigned before Reader is removed, so the subscription is never without a read role. This needs Owner or User Access Administrator.

Remove on a connection’s row stops Seylo using it at once. It cannot revoke the grant in your cloud: only you can. After removing, the page shows the commands to run on your side, from what the last Test saw.

Terminal window
MSYS_NO_PATHCONV=1 az role assignment delete --assignee <Seylo app ID> \
--role "Seylo Reader <subscription ID>" --scope /subscriptions/<subscription ID>
MSYS_NO_PATHCONV=1 az role definition delete --name "Seylo Reader <subscription ID>" \
--scope /subscriptions/<subscription ID>
az ad sp delete --id <Seylo app ID>

The role definition can be deleted only once nothing is assigned it, so the assignment goes first. A subscription still on the built-in Reader is removed with MSYS_NO_PATHCONV=1 az role assignment delete --assignee <Seylo app ID> --role Reader --scope /subscriptions/<subscription ID> instead; the page shows whichever the last Test saw. The last command removes Seylo’s app from your directory. Skip it if another subscription in the same directory is still connected. Once the connection is removed, Seylo stops reading that subscription’s bill, and your nodes go back to your uploaded rates or the public list price.

Deleting the grant in your cloud ends Seylo’s access whether or not you removed the connection in Seylo first. A connection whose grant is gone stays on the page and fails its next test.

The badge says what kind of problem it is; the sentence beside it says what to do. The common ones:

Badge You see What to do
Consent needed Seylo's app is not in directory … yet. An administrator of that directory opens the consent link, or runs az ad sp create, then presses Test again
App disabled Seylo's app is in your directory but disabled … Enable it under Enterprise applications → Seylo → Properties, or remove the connection
Wrong directory No Microsoft Entra directory has the ID … Copy the Tenant ID from Microsoft Entra ID → Overview
Blocked by policy A Conditional Access policy in your directory blocked Seylo's app from signing in. Exclude Seylo’s service principal from that workload identity policy, or connect another directory
Wrong subscription Subscription … was not found. or … belongs to a different Microsoft Entra directory than the one entered. Use the subscription’s ID, and the Tenant ID of the directory that owns it
No role yet Seylo's app signed in but has no role on subscription … Run the Seylo Reader commands. A new assignment can take up to 5 minutes to apply
Trust not set up Account … has no IAM OIDC identity provider for Seylo … or Seylo may not assume arn:aws:iam::…:role/SeyloReadOnly … Deploy the CloudFormation stack the portal shows, then press Test again
No role yet Seylo assumed the role but could not read it … or The role SeyloReadOnly has no policy … Deploy the stack the portal shows rather than a role you made by hand
Trust not set up Project … has no workload identity pool "seylo" with provider "seylo-entra" … Run the commands the portal shows, and check the project number
No role yet The service account seylo-reader@… does not exist. or Seylo may not act as seylo-reader@… Run the commands the portal shows; the last one lets Seylo act as the service account. It can take a minute to apply
Wrong account Project … has number …, not …. Correct the project number
API not enabled A Google API Seylo needs is not enabled in project … Run the gcloud services enable command in the message, wait a minute, then press Test again
Can write - refused A read connection must not be able to change anything … Remove the role or policy the message names, and keep only Seylo Reader, ViewOnlyAccess, or the viewer roles. See your cloud’s tab above
Not this organisation’s … does not name this organisation. Create the grant again with the command the portal shows, which names your organisation. See why the grant names your organisation
Seylo-side problem … This is on Seylo's side … Nothing in your cloud. Press Test again later; if it persists, write to support@seylo.in
Unreachable Seylo could not reach … A network problem between Seylo and your cloud’s API. Press Test again in a minute

Messages that are not a test result:

You see What it means
Cloud accounts are not switched on in this Seylo region yet. Nothing about your clusters depends on them. Your organisation’s Seylo region does not offer cloud accounts yet
AWS and Google Cloud accounts are not switched on in this Seylo region yet; Azure is. Only Azure can be connected in your region
… is already connected as "…". Test or remove that connection instead. The account is connected already. Test the existing connection, or remove it first
An organisation can connect at most 50 cloud accounts. Remove one you no longer use first. Remove a connection you no longer use