Quirin Schlegel

Loading

Fourteen days, no record — AgentCore runtime instances meet GDPR accountability

AWS made a 14-day agent session generally available on 6 August 2026, and deleting that session deprovisions the persistent volumes with it — so the working state of a long-horizon agent is scratch space, not a record. GDPR Article 5(2) asks the controller to demonstrate compliance rather than merely be compliant, and the AI Act clause engineers reach for, Article 12 record-keeping, binds high-risk systems whose obligations the Digital Omnibus deferred. The reliability literature lands in the same place: LongHorizon-Harness holds task state outside the executor and updates it only from independently verified environment facts, which is also precisely what leaves an audit trail.

11 August 20269 verified claims6 sources

AWS gave your agent fourteen days to run. Delete the session and the only record of what it did for those fourteen days is deleted with it.

On 6 August, Amazon Bedrock AgentCore runtime instances went generally available. Agents now run on EC2 instances that AgentCore provisions and operates inside your own AWS account — sessions of up to 14 days, against 8 hours on the serverless microVM runtime. Frankfurt and Ireland are in the launch set, so this is live for EU workloads today.

The infrastructure story is good. AWS handles provisioning, patching, scaling and teardown. Your data stays in your account.

It is the teardown behaviour that should change your design.

When a session is deleted, AgentCore deprovisions everything, including the persistent volumes. A 14-day agent accumulates its entire working state on that disk — intermediate reasoning, tool calls, the files it touched. That disk is not a record. It is scratch space with a fortnight's lease.

Now put an EU regulator in the room. GDPR Article 5(2) does not ask you to be compliant. It asks you to be able to demonstrate it. A deprovisioned volume demonstrates nothing.

Three days before the launch, a paper from Alibaba's DreamX team argued the same thing from the reliability side: hold task state outside the executor, update it only from facts independently verified against the environment, audit it read-only. WeaveBench pass rate went from 51.8% to 80.7%.

The reliability fix and the evidence fix are the same fix.

What I would do on Monday:

1. Externalise task state. The instance runs the work; it does not hold the truth. 2. Emit an audit event per verified state transition, off the instance, as it happens. 3. Cap session lifetime by policy. 14 days is a capability, not a default. 4. Treat a shared session ID as a blast radius — two runtimes on one session share a filesystem. 5. Write down now what survives teardown. That list is your evidence boundary.

If your longest-running agent were deleted tonight, what could you still prove about what it did?

#AIAgents #EUAIAct #GDPR #AgenticAI #PlatformEngineering

AI disclosure: the narration voice, the cover art and the brand ident animation in this video are AI-generated. The script, the claims and the source checks are mine.

Evidence

What this rests on

Every factual claim in the edition above, stated on its own and checked before publication. If one of these is wrong, the argument is wrong — so they are listed where you can check them.

Amazon Bedrock AgentCore Runtime instances became generally available on 6 August 2026, running agents on EC2 instances that AgentCore provisions and operates inside the customer's own AWS account.
Why it mattersFixes the date and the ownership boundary. Any claim that the agent runtime moved into the customer's account rests on this.
amazonwebse2026runtime · amazonwebse2026agentcore · amazonwebse2026run
An AgentCore runtime-instance session runs for a maximum of 14 days and is stopped automatically at that limit, against up to 8 hours for the serverless microVM runtime.
Why it mattersThe 14-day vs 8-hour contrast is the whole reason the retention question is new rather than theoretical.
amazonwebse2026run · amazonwebse2026agentcore · amazonwebse2026runtime
When an AgentCore runtime-instance session is deleted, AgentCore deprovisions everything including the persistent volumes; EBS volumes retain data across session stops but are deleted with the session.
Why it mattersThe load-bearing fact of the edition: the working state of a long-horizon agent is destroyed with the session.
amazonwebse2026run
Two agent runtimes sharing a capacity provider and invoked with the same runtimeSessionId land on the same EC2 instance, where they share a filesystem.
Why it mattersTurns a shared session identifier into a blast-radius decision rather than a convenience.
amazonwebse2026run
AgentCore runtime instances launched in nine AWS Regions, including Europe (Frankfurt) and Europe (Ireland).
Why it mattersWithout an EU region this is a US-only curiosity. Frankfurt and Ireland make it a Berlin team's problem today.
amazonwebse2026agentcore
GDPR Article 5(2) provides that the controller shall be responsible for, and be able to demonstrate compliance with, the principles in Article 5(1), which include the storage-limitation principle in Article 5(1)(e).
Why it mattersDemonstrability, not retention, is the clause that bites. It is why deleting the volume is a compliance event.
intersoftco2026art
LongHorizon-Harness (arXiv 2608.01964, submitted 3 August 2026 by the DreamX Team, Alibaba Group) maintains task state outside the executor and updates it only with facts independently verified from the environment, via a Manage-Execute-Audit loop capped at 25 rounds.
Why it mattersThe engineering counterpart: externalised, environment-verified state is the reliability answer and the evidence answer at once.
arxiv2026longhoriz
On WeaveBench with Qwen 3.7-Plus using Claude Code, LongHorizon-Harness raised pass rate from a 51.8% baseline to 80.7%; on Terminal-Bench 2.1 with Qwen 3.7-Plus, success rate rose from 69.7% to 77.2%.
Why it mattersGives the argument a number. Attribution to benchmark and model matters — it is not a general result.
arxiv2026longhoriz
AI Act Article 12 requires high-risk AI systems to technically allow automatic recording of events over the system's lifetime; it sits in Chapter III, Section 2, so it binds high-risk systems only.
Why it mattersExplains why the AI Act clause engineers reach for is not the one binding them this morning.
euaiactexpl2026ai

Sources

Amazon Web Servicesprimary source
amazonwebse2026agentcore
Original Archived PDFretrieved 11 August 2026 · published 6 August 2026
Amazon Web Servicesprimary source
amazonwebse2026run
Original Archived PDFretrieved 11 August 2026 · published 6 August 2026
Amazon Web Servicesprimary source
amazonwebse2026runtime
Original Archived PDFretrieved 11 August 2026 · published 6 August 2026
arXivprimary source
arxiv2026longhoriz
Original Archived PDFretrieved 11 August 2026 · published 3 August 2026
EU AI Act Explorersecondary
euaiactexpl2026ai
Original Archived PDFretrieved 11 August 2026 · published 11 August 2026
Intersoft Consultingprimary source
Art. 5 GDPR — Principles relating to processing of personal data
Original Archived PDFretrieved 4 September 2026

Every source for this edition, as one PDF BibTeX — all editions

Corrections

What changed after publication

None.