Manage Connections#

Connections are the authenticated links between Reply CMP and your cloud provider accounts. All discovery, cost ingestion, provisioning, monitoring, and automation operations run through connections. Keeping credentials valid is critical for uninterrupted platform operation.

Navigate: left navigation → Tenant → Connections.

Note

For creating a new connection from scratch, see Connect a Provider.

The Connections list#

Connections are displayed as a card grid. Each card shows:

  • Provider logo (Azure / AWS / GCP)

  • Connection name and alias (e.g. default, prod, dev)

  • Status indicator: Active / Expiring (amber) / Expired (red)

  • Expiry date chip

Search: filter connections by name or alias.

Load More: the first 12 connections are shown; click Load More to load 12 more per click.

Connection health#

New in version 1.0.0.

Each connection card now shows when data was last updated, so teams can immediately spot stale connections at a glance:

Field

What it shows

Last discovery

When the most recent resource discovery scan completed for this connection

Last cost refresh

When cost data was last successfully ingested from the provider

Latest reservation data

The date through which reservation costs have been processed (only shown for connections with Reserved Instances, Savings Plans, or CUDs)

If a connection shows a Last discovery or Last cost refresh date older than 48 hours, check the connection credentials and trigger a manual sync from the connection’s action menu.

Connection actions#

Each connection card has an action menu:

Action

Description

Launch Discovery

Triggers an on-demand resource discovery sync for this connection

Refresh Cost Data

Triggers an on-demand cost data ingestion

Open Details

Opens the Connection Details modal

Delete

Removes the connection (with confirmation)

Updating connection credentials#

Credentials expire. When expiry is approaching (amber chip) or has passed (red chip), update the secret:

  1. Click Open Details → the Connection Details Modal opens

  2. Scroll to Credentials → click Update Secret

  3. Fill in the provider-specific credential form:

Azure: Client ID, new Client Secret value, (read-only) Tenant ID and Subscription ID

AWS: Access Key ID, new Secret Access Key

GCP: Upload a new Service Account JSON key file

  1. Click Validate — Reply CMP tests the new credentials against the provider API before saving

  2. If validation passes: click Save — the credential is stored in Azure Key Vault

  3. If validation fails: fix the error shown and retry before saving

Important

Always validate before saving. Saving invalid credentials immediately breaks all platform operations for this connection.

Connection aliases#

The alias identifies the connection in Provisioning templates (default, prod, dev, etc.). To update:

  1. Open Details → click the alias field → edit → Save

Note

If you change an alias that is referenced in existing deployment configurations, those deployments may need to be updated to use the new alias name.

Deleting a connection#

  1. Click Delete on the connection card → a confirmation dialog appears

  2. Confirm

Post-delete effects:

  • No new discovery, cost, provisioning, or monitoring operations run for this connection

  • Existing cost and discovery data from before deletion is retained in the platform for historical reporting

Reading the connection status#

Status

Chip colour

Action needed

Active

Green

None

Expires soon

Amber

Rotate credentials before expiry

Expired

Red

Update credentials immediately