---
title: "2026-08-28 vxData SDK S3 module reference map"
description: "Mapped code, tests, and docs affected by moving vxData SDK storage code into an s3 package."
image: "https://docs.virdx.dev/img/virdx-social-card.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.virdx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-08-28 vxData SDK S3 module reference map

## Work Done

- Inspected the vxData SDK storage transport and transfer modules without editing the monorepo.
- Mapped tracked imports, tests, and documentation that must change when direct S3, storage transport, download, upload, and shared transfer code move under `vxdata.sdk.s3`.
- Reported exact files and hazards to the parent agent, including circular imports, the public `TransferConfig` export, shared wire policy placement, and stale accidental exports.

## Lessons Learned: Pitfalls

- The infrastructure SOP overview was broader than needed for this static import map, but it did identify the SDK SOP as relevant context.
- The generic `test_transfer.py` name hides that it tests only downloads, which makes the intended split less obvious.

## Lessons Learned: Improvements

- The SDK module-layout section should name public versus internal imports. This would make module moves safer and clarify that only top-level `TransferConfig` is a supported transfer import.
- A focused SDK architecture page that records package boundaries and import direction would help prevent circular imports during future refactors.

Source: https://docs.virdx.dev/knowledge/inbox/2026-08-28-infrastructure-vxdata-sdk-s3-module-reference-map/index.mdx