D4C registration
D4C registration is the Discover-for-Cloud AWS account collection for
this CID — GetD4CAwsAccount (PEP 8 get_aws_account) and
CreateD4CAwsAccount (PEP 8 create_aws_account). The path is
GET /cloud-connect-aws/entities/account/v2 and
POST /cloud-connect-aws/entities/account/v2.
The other 18 D4C ops and deprecated Cloud Connect AWS are not
implemented. No further roadmap row. Remaining operations stay under Not yet implemented.
This is not Cloud AWS Registration
(/cloud-security-registration-aws/…):
Cloud AWS Registration. This is not
Cloud security detections (/cloud-security-evaluations/…):
Cloud security detections. This is not
the HelloService template sample (GET /api/hello).
This collection is not CrowdStrike production. It does not call Falcon cloud. It is not CrowdStrike Falcon Cloud or Horizon.
RPC field notes: D4CRegistrationService. REST schemas:
API reference. Unused query keys ids, organization-ids,
status, limit, offset, migrated, scan-type, and parameters
are ignored. Extra unused parameters are ignored.
These curls use Host: crowdstrike-api.localhost against Compose
Traefik on :8088. If the hostname already resolves to Traefik, you can
omit the Host header and call http://crowdstrike-api.localhost instead.
Auth
Every call needs a console session or a Bearer token:
- Cookie
cs_consolefromCreateSession(POST /identity/entities/sessions/v1) Authorization: Bearerwithd4c-registration:read(GET) ord4c-registration:write(POST)
A session cookie bypasses OAuth scopes and can list and create. Seed
client cs-local-hosts (hosts:read only) cannot list or create
(403). Unit tests use a client named cs-local-d4cr with
d4c-registration:read; that client can list and cannot create
(403). Unit tests use a client named cs-local-d4cw with
d4c-registration:write; that client can create and cannot
list (403). Those clients are tests only; compose uses the session
cookie. GetD4CAwsAccount stays d4c-registration:read.
CreateD4CAwsAccount stays d4c-registration:write. There is no seeded
production client with d4c-registration:read or
d4c-registration:write — use the console cookie, or a client you
created with that scope. Missing or revoked token → 401.
HTTP paths
| Method | Path | Use |
|---|---|---|
GET | /cloud-connect-aws/entities/account/v2 | List D4C AWS accounts. RPC GetD4CAwsAccount. PEP 8 get_aws_account. d4c-registration:read. Extra unused query ids, organization-ids, status, limit, offset, migrated, scan-type, parameters ignored. Success 200 MSA resources (account_id, account_type, cloudtrail_region, iam_role_arn, is_master, organization_id, status). Order by account_id ascending. Distinct from Cloud AWS Registration and Cloud security detections. Other 18 D4C ops and deprecated Cloud Connect AWS are not implemented. |
POST | /cloud-connect-aws/entities/account/v2 | Create D4C AWS account. RPC CreateD4CAwsAccount. PEP 8 create_aws_account. d4c-registration:write. Body JSON resources[] with account_id, account_type, cloudtrail_region, iam_role_arn, is_master, organization_id. Success 201 MSA one resource with those keys and status registered. Missing resources → 400. Missing account_id → 400. Duplicate account_id → 409. Distinct from GET this path, Cloud AWS Registration POST, and Cloud security detections. |
Empty query params on GET return every account in this CID.
Default sort is account_id ascending. Empty store → empty resources,
still 200.
JSON is snake_case MSA. Clone GET success is 200. Clone POST success is 201.
The other 18 D4C ops and deprecated Cloud Connect AWS are not implemented. No further roadmap row. Remaining operations stay under Not yet implemented.
Seed accounts
account_id | account_type | cloudtrail_region | iam_role_arn | is_master | organization_id | status |
|---|---|---|---|---|---|---|
acct-d4c-1 | commercial | us-east-1 | arn:aws:iam::acct-d4c-1:role/lab | false | org-d4c-1 | registered |
acct-d4c-2 | commercial | us-west-2 | arn:aws:iam::acct-d4c-2:role/lab | true | org-d4c-1 | registered |
List returns acct-d4c-1 then acct-d4c-2 in account_id order.
Session cookie
curl -sS -c cookies.txt -H 'Host: crowdstrike-api.localhost' \
-H 'Content-Type: application/json' \
-d '{"email":"[email protected]","password":"FalconLocal!1","cloud":"us-1"}' \
'http://127.0.0.1:8088/identity/entities/sessions/v1'
GetD4CAwsAccount (cookie)
curl -sS -b cookies.txt -H 'Host: crowdstrike-api.localhost' \
'http://127.0.0.1:8088/cloud-connect-aws/entities/account/v2'
Success returns acct-d4c-1 then acct-d4c-2.
CreateD4CAwsAccount (cookie)
curl -sS -b cookies.txt -H 'Host: crowdstrike-api.localhost' \
-H 'Content-Type: application/json' \
-d '{"resources":[{"account_id":"acct-d4c-new","account_type":"commercial","cloudtrail_region":"eu-central-1","iam_role_arn":"arn:aws:iam::acct-d4c-new:role/lab","is_master":false,"organization_id":"org-d4c-1"}]}' \
'http://127.0.0.1:8088/cloud-connect-aws/entities/account/v2'
Success 201 returns acct-d4c-new with status registered.
Related
- Cloud AWS Registration — cloud AWS registration
- Cloud security detections — cloud security detections
- API reference
The other 18 D4C ops and deprecated Cloud Connect AWS are not implemented (not yet). No further roadmap row. Remaining operations stay under Not yet implemented. This is not Cloud AWS Registration or Cloud security detections.