Unit 2.3: Activity Logs and the Audit Trail
Introduction
An auditor rarely asks what happened in the last month. They ask what happened on a specific day a year ago, who did it, and how you know the record has not been altered. The platform's activity log answers the first two questions only for a limited window, and it answers them per contract. The rest of the audit trail is an architecture you build.
This unit explains the activity log's fixed properties and then designs the pattern around them: pull, export, aggregate and lock. It is a design unit; Unit 5.2 builds the bucket and Unit 7.2 the wider observability planes.
1. What the Activity Log Gives You
1.1 Scope and Access
The activity log records the actions performed in a contract: user logins, resource provisioning, configuration changes, data access and more. For each entry you can also track the source of an action, the resources affected by the activity and the timeline of the events. The trace records are limited to IaaS products, so the audit evidence for managed PaaS services must come from elsewhere.
Four properties are fixed:
- Per contract. The activity log is grouped by contract and can be refined using date ranges. You retrieve it per contract number.
- Read-only. All calls to the activity log are
GETrequests, so no API call changes an entry. - API only. The activity log is available through its RESTful API only, at
https://api.ionos.com/activitylog/v1, with Basic authentication or a Bearer token. - 35-day retention. The data retention period is 35 days. After it expires, data older than the retention period is purged.
Contract Owners and Administrators can access the activity log API by default and can grant access to User accounts through the Access Activity Log privilege. Treat that privilege as sensitive: the platform classes access to the activity log, with its usage profiles of the organization, as access to sensitive data.
1.2 What It Does Not Do
The activity log does not push anything. Its interface consists of read calls only, so every consumer pulls. It also does not aggregate. A credential can list the contracts it is authorized to access through the /contracts endpoint, but each contract's entries are retrieved separately. A group of contracts therefore needs an aggregation point that you operate.
2. The Export Pattern
2.1 The 35-Day Window Is a Deadline
Because entries are purged after 35 days, the retention period is not your archive; it is the time you have to copy each entry somewhere durable. IONOS CLOUD itself recommends downloading the data and storing it in a different storage such as IONOS Cloud Object Storage for longer persistence. Design the export so that a failure is noticed and repaired well inside the window:
- Run a scheduled exporter under a dedicated automation user (Unit 2.2) that holds only the Access Activity Log privilege, with a Bearer token.
- Enumerate contracts with
GET /contracts, then pull each one withGET /contracts/{contractNumber}, using thedateStartanddateEndfilters and paging withlimitandoffset. The maximum page size is 10000. - Overlap the windows. Pull a range that overlaps the previous run, and de-duplicate on the entry's
@uuidfield, so that a missed run loses nothing. - Alert on gaps. Monitor the newest exported timestamp per contract. An exporter that has been silent for days is an incident, because every day of silence spends part of the 35-day budget.
curl -s -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
"https://api.ionos.com/activitylog/v1/contracts/$CONTRACT?dateStart=$START&dateEnd=$END&limit=10000&offset=0"
The snippet's point is architectural: the time range is yours to manage, and the exporter, not the platform, owns completeness.
2.2 Making the Archive Tamper-Evident
The archive target is IONOS Cloud Object Storage with Object Lock. Object Lock applies write once, read many (WORM) protection to objects, so they cannot be deleted or modified for a specified duration. It has two modes. Governance mode allows specific users with special permissions to override the lock. Compliance mode enforces a strict lock without any possibility of an override: an object is immutable until its retention date has passed, and the retention period cannot be shortened by the bucket owner or by IONOS CLOUD.
Four constraints shape the bucket design:
- Object Lock can only be enabled when you create the bucket; it cannot be added to an existing bucket. Enabling it also enables versioning, and neither can be disabled afterwards.
- The DCD sets a retention period of up to 365 days. For longer periods, use the API, which allows up to 100 years.
- A bucket with Object Lock enabled cannot be a source for replication or tiering, though it can be a destination.
- Lifecycle rules handle expiry after the retention period; a lifecycle configuration holds up to 1000 rules.
Storage cost is modest at this volume: Object Storage is priced at 0,007 € per GB per 30 days in the EUR price list, with no charge for API calls.
2.3 Search and Aggregation
The archive proves integrity; it is not where analysts search. For search, forward the exported entries to a log platform. One documented pattern runs a script that pulls activity log events for every contract and forwards them through Fluent Bit to the IONOS CLOUD Logging Service, where Grafana queries them. Keep the roles separate: Grafana queries a window of up to 30 days, so the Logging Service is the search plane and the locked bucket is the evidence plane. Enterprises with a central Security Information and Event Management (SIEM) system send the same stream there instead; Unit 7.2 designs that fan-in.
FinCorp combines these parts. Its exporter runs every six hours under svc-fc-audit-export, pulls both contracts from Unit 2.1, and writes daily files to a contract-owned bucket in Frankfurt (eu-central-4), created with Object Lock in Compliance mode and a multi-year retention period set through the API. The Berlin contract-owned region (eu-central-3) is not used for this archive because its BSI IT-Grundschutz certification is currently pending. The same events feed FinCorp's SIEM for correlation. Because the trace records cover IaaS products only, FinCorp's audit mapping lists the evidence source for each managed service separately.
Decision Summary
| Requirement | Platform property | Design decision |
|---|---|---|
| Audit history beyond five weeks | 35-day retention, then purge | Scheduled export, overlapping windows, gap alerting |
| Tamper-evident evidence | Activity log is read-only, but expires | Object Storage bucket with Object Lock in Compliance mode, created with the lock enabled |
| Retention longer than 365 days | DCD limit of 365 days | Set the retention period through the API |
| One view across contracts | Grouped and retrieved per contract; no push | Exporter enumerates /contracts and aggregates outside the platform |
| Least-privilege access to audit data | Access Activity Log privilege; owners and administrators by default | Dedicated export user with only that privilege and a Bearer token |
| Evidence for managed services | Trace records limited to IaaS products | Map each PaaS service to its own evidence source |
Summary
The activity log is a read-only, per-contract, API-only record of IaaS activity that keeps entries for 35 days. Treat that window as an export deadline: pull every contract on a schedule, overlap the ranges, and write the results to an Object Storage bucket locked in Compliance mode. Search and correlation belong in a log platform or SIEM, fed from the same export.
Key Points:
- The activity log is grouped by contract, read-only (
GETonly) and available through the API only. - Entries are purged after 35 days; IONOS CLOUD recommends storing them elsewhere, such as Object Storage.
- Nothing is pushed and nothing is aggregated across contracts; your exporter does both.
- Object Lock must be enabled at bucket creation; Compliance mode cannot be shortened by the owner or by IONOS CLOUD.
- The trace records cover IaaS products only; plan separate evidence for managed services.