Files
cp1-agents/docs/customer-cloud-access.md
Jonathan Boniface c14a94f33b
Some checks failed
check agents / check (push) Failing after 12s
Add hyperscaler discovery MCP servers and Well-Architected guidance
azure-discovery, aws-discovery and gcp-discovery collect read-only metadata
on servers, workloads, Kubernetes clusters, networks, data stores, policies
and provider recommendations. Credentials arrive per call from the vault.
Replies are paged, scrubbed of secrets and anonymised, and throttled calls
back off. cloud-knowledge searches each provider's Well-Architected guidance
from fixed lists only, so no customer detail can leave the platform.

Adds shared skills, the render and test tooling, a public Python Dockerfile
until the hardened base image is reachable, the customer access guide, the
implementation plan and the Vault Service platform issue.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-30 20:11:57 +00:00

53 lines
2.9 KiB
Markdown

# Giving KAB read-only access to a cloud estate
For a customer's cloud administrator, and the Kyndryl engineer working with them. These steps give the discovery servers read-only access to one estate. **The role lists below are starting points: they haven't yet been tested against a real estate.**
Discovery reads metadata only. It doesn't read files, database rows, documents or secret values, and it can't change anything. People's names and email addresses are removed from what it collects.
Enter the values under **Credentials** in KAB, for the engagement's project and the matching server. Then use the page's test to confirm the connection.
## Azure
1. Create an app registration and a client secret in Microsoft Entra ID.
2. Assign it **Reader** at the management group or subscription to be discovered.
| Field | Value |
|---|---|
| `tenant_id` | The Entra tenant id |
| `client_id` | The app registration's id |
| `client_secret` | The client secret |
| `scope_root` | `managementGroups/<id>` or `subscriptions/<id>` |
| `cloud` | Optional: `public`, `usgov` or `china` |
**For a short trial on your own estate only:** leave those three fields blank and put a token in `access_token`, from `az account get-access-token --resource https://management.azure.com --query accessToken -o tsv`. It expires within about an hour, after which calls fail until you store a new one. It carries your own permissions, not Reader, so never use this for a customer.
## AWS
1. Create a read-only IAM role, with the AWS managed policies **SecurityAudit** and **ViewOnlyAccess**, plus the `wellarchitected` read actions if you use the Well-Architected Tool.
2. Set its trust policy to allow Kyndryl's broker identity, and require an external id.
3. To collect organisation policies, create the role in the management account or a delegated administrator account.
4. For more accounts, create a role with the same name in each, trusting the first role.
| Field | Value |
|---|---|
| `access_key_id`, `secret_access_key` | The broker identity that assumes the role |
| `role_arn`, `external_id` | The role and its external id |
| `regions` | Comma-separated regions; the first is the default |
| `account_ids`, `member_role_name` | Optional: member accounts, and the role's name in them |
| `aggregator_name` | Optional: an AWS Config aggregator |
## Google Cloud
1. Create a service account and a JSON key.
2. Grant it, at the organisation, folder or project: **Cloud Asset Viewer**, **Browser**, **Compute Network Viewer** and **Organization Policy Viewer**, plus the Recommender viewer roles.
3. Enable the Cloud Asset, Organization Policy and Recommender APIs.
| Field | Value |
|---|---|
| `scope_root` | `organizations/<id>`, `folders/<id>` or `projects/<id>` |
| `service_account_json` | The JSON key |
## Removing access
Delete the credential in KAB, then delete the app registration, role or service account in the customer's cloud. Removing it from the cloud takes effect at once.