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.

Post

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:

Externalise task state. The instance runs the work; it does not hold the truth.
Emit an audit event per verified state transition, off the instance, as it happens.
Cap session lifetime by policy. 14 days is a capability, not a default.
Treat a shared session ID as a blast radius — two runtimes on one session share a filesystem.
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.

First comment

Sources for this edition — primaries only.

AWS News Blog, 6 August 2026 — runtime instances announced https://aws.amazon.com/blogs/aws/runtime-instances-persistent-compute-for-production-ai-agents-on-amazon-bedrock-agentcore/

AWS What's New — general availability, the nine regions, session limits https://aws.amazon.com/about-aws/whats-new/2026/08/aws-bedrock-agentcore-runtime-instances-generally-available/

AgentCore developer guide — capacity providers, shared filesystem, the 14-day cap and what teardown deletes https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances-how-it-works.html

LongHorizon-Harness — DreamX Team, Alibaba Group, arXiv 2608.01964, submitted 3 August 2026 https://arxiv.org/abs/2608.01964

GDPR Article 5 — storage limitation and accountability https://gdpr-info.eu/art-5-gdpr/

Cut for length: the AI Act clause you would reach for here is Article 12, automatic logging over the lifetime of the system — but that sits in Chapter III and binds high-risk systems, and the Digital Omnibus deferred those obligations by 17 to 24 months. Which is precisely why the constraint that binds a Berlin team this morning is GDPR, not the AI Act.

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.

Claims

Sources

Corrections

None.

AI disclosure

The video for this edition contains AI-generated media: the narration is a synthetic voice and the cover art is generated. The script, the claims and the source verification are human-authored and human-checked. Assets carry IPTC DigitalSourceType and C2PA Content Credentials.

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.

Post

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.

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.

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.

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

What I would do on Monday:

Externalise task state. The instance runs the work; it does not hold the truth.

Emit an audit event per verified state transition, off the instance, as it happens.

Cap session lifetime by policy. 14 days is a capability, not a default.

Treat a shared session ID as a blast radius — two runtimes on one session share a filesystem.

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.