DocumentaciónHelp

Connect AWS, Google Cloud, Azure, Cloudflare or Coolify

Create the read-only AWS, Google Cloud or Azure connection once; costs and the SIEM then pick it when they are enabled.

On this page

The connection is the read-only identity ARGUNIS uses to access your cloud. You create it once in Settings → Monitoring → Cloud services and the key is stored in your company's vault. Afterward, each section that uses it picks it when it is enabled, and you add the permission it needs to that identity.

Before you begin

  • Administer permission in Settings.

  • Access to your cloud console to create a user, a service account or an app registration.

Steps

  1. Go to Settings → Monitoring → Cloud services and choose the AWS, Google Cloud or Azure tab.

  2. Click Connect AWS, Connect Google Cloud or Connect Azure.

  3. Follow the steps on the screen. Each one comes with ready-to-copy commands:

    • AWS: choose how ARGUNIS signs in (IAM user with an access key, or role with an external ID) and create the argunis user with its access key. In role mode, also create the role with the trust relationship shown on the screen.

    • Google Cloud: create the argunis service account and its JSON key.

    • Azure: register the argunis application (service principal) and create a client secret; copy the value.

  4. Paste the key and, if you want, enter the Connection name.

  5. Click Save and test. The test only authenticates against the cloud, at no cost.

The identity is created without permissions. Each section tells you which permission to add when you enable it: the What this connection enables table summarizes them.

What the connection enables

Section

Where to enable it

Connection

Permission you add

Monitoring

On this same tab, in AWS resources, Azure resources or Google Cloud resources

The connection whose resources you see and edit below

Google Cloud: roles/compute.viewer, roles/cloudsql.viewer, roles/run.viewer, roles/cloudfunctions.viewer and roles/monitoring.viewer on each project (Copy commands button). See Choose which Google Cloud resources are monitored. Azure: "Reader" and "Monitoring Reader" roles on each subscription (Copy commands button). See Choose which Azure resources are monitored. AWS: ec2:Describe*, rds:Describe*, lambda:List*, elasticloadbalancing:Describe*, cloudwatch:GetMetricData, lightsail:GetInstances and lightsail:GetInstanceMetricData (Copy policy button). See Choose which AWS resources are monitored

Costs

FinOps integrations → AWS, GCP or Azure

The one used by the cost reading, or Enable in FinOps integrations

AWS: Cost Explorer policy. Google Cloud: read access to the billing dataset. Azure: "Cost Management Reader" role

SIEM

SIEM integrations → AWS, Google Cloud, Microsoft 365, Cloudflare or Coolify

The one used by each SIEM integration, or Enable in SIEM integrations

AWS: cloudtrail:LookupEvents. Google Cloud: "Logs Viewer". Azure: AuditLog.Read.All and SecurityAlert.Read.All, and "Reader" on each subscription for the Activity Log

Choose each section's connection

With more than one connection for the same cloud, the Connection column of the What this connection enables table lets you choose which one each section uses without leaving the page:

  • Monitoring: choose which connection you see and edit in … resources, further down. It is the same selector as in that section: changing one changes the other. It doesn't turn anything off: several connections can monitor at the same time. If you have unsaved changes in the resources, it first asks whether to discard them.

  • Costs: if the cost reading for that cloud is enabled, it shows its connection. When you choose another, confirm the notice ("AWS costs will use …") and the reading continues with the same options. If it isn't enabled, Enable in FinOps integrations appears and takes you to that page.

  • SIEM: the same, with that cloud's SIEM integration. If there are several, a selector appears for each integration, with its name above it. If there are none, Enable in SIEM integrations appears.

Only administrators can change the Costs or SIEM connection. Everyone else sees the name of the connection each section uses. Before changing it, add that section's permission (last column) to the new connection's identity: if it doesn't have it, the next reading fails.

Manage a connection

In each tab's connection table, the Used by column shows which sections use it.

  • Test: authenticates again.

  • Change key: saves a new key. The previous one keeps working for 24 more hours.

  • Remove (trash can): deletes the stored key. You can't do it while a section uses it; turn it off there first. In the cloud, the identity still exists: delete it there if you no longer use it.

Related

Cloudflare

  1. In dash.cloudflare.com → My Profile → API Tokens → Create Token, choose Create Custom Token.

  2. Permissions, all read-only: at account level Account Analytics, Account Settings, Cloudflare Pages and Workers Scripts; at zone level Zone, DNS, Analytics and SSL and Certificates. Zone resources: all zones in the account.

  3. Copy the token (Cloudflare won't show it again) and paste it in the Cloudflare tab with Connect Cloudflare. The Account ID is optional: without it, ARGUNIS uses the accounts the token can see.

Coolify

  1. In your Coolify dashboard, go to Keys & Tokens → API tokens and create a token just for ARGUNIS with read permission only: no write, no deploy and no root.

  2. Copy the token (it looks like 1|xxxxxxxx…; Coolify won't show it again).

  3. In the Coolify tab, click Connect Coolify, enter the Coolify address (the dashboard's address, for example https://coolify.tu-empresa.cl, without a path) and paste the token. Save and test queries the Coolify version with the token, without changing anything.

ARGUNIS reaches the Coolify API through that public address. We recommend publishing it behind Cloudflare with a WAF rule that only lets in the platform's IP.

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

↑↓ to navigate · Enter to open · Esc to close