🏠 Overview › 🧩 Components ›🧩 Object Storage

Object Storage

Component Detail

Infrastructure medium complexity backend
0
Dependencies
0
Dependents
0
Entities
0
Integrations

Description

External object storage system (e.g. S3-compatible bucket) that holds the binary file content for attachments. Accessed via signed URLs so clients can upload and download directly without proxying through the backend. Provides durable storage and lifecycle policies for retention.

Feature: Document Attachments

object-storage

Sources & reasoning

Matrix row 107 places Dokumentvedlegg at Fase 2 (mapped to Core Product). NHF unique-needs entry explains the Bufdir-evidence motivation and justifies it as a toggleable area-level capability rather than a quick-log addon.

  • Dokumentvedlegg til aktiviteter: Invitasjoner, Facebook-skjermbilder m.m. - viktig for Bufdir-etterprøving.
  • Dokumentvedlegg til aktiviteter | - | âś“ | - | - | âś“ | NICE TO HAVE | 2

Responsibilities

  • Store binary file content for uploaded attachments
  • Serve files via signed download URLs with limited TTL
  • Accept direct uploads via signed PUT URLs from clients
  • Apply lifecycle and retention policies for audit compliance
  • Provide durability and redundancy for stored objects

Interfaces

putObject(key: string, body: Binary, contentType: string): void
getSignedPutUrl(key: string, mimeType: string, ttlSeconds: number): string
getSignedGetUrl(key: string, ttlSeconds: number): string
deleteObject(key: string): void