Portal Community

Resource / Operation Model

Every S3 node config selects one of 13 operations via a resource + operation pair — not a single flat operation string. There is no generic "S3 node" config; each combination has its own dedicated form with its own field set, documented on its own page:

ResourceOperations
bucketcreate, delete, list-all, search
objectupload, download, copy, delete, get-many, exists
foldercreate, delete, get-many

Connection: Vault + Satellite

No operation form has credential or region fields. Connection settings — the vault credential, AWS region, and an optional S3-compatible endpoint override — live on a separate S3 Server satellite node, wired into each operation node's input. The satellite's values are merged onto every connected operation at execution time.
ModeWhenWhat you provide
Vault credential (default)Normal use, any environmentAn ApiKey-type vault record on the satellite — Username = access key ID, Password = secret key
IAM roleHost runs on EC2/ECS/Lambda with a role attachedNothing — set useIamRole=true on the satellite

Full field reference, the 15-value region list, credential-format rules, and how to point this node at Backblaze B2/MinIO/Cloudflare R2/DigitalOcean Spaces: see S3 Server (satellite).

Validation Rules

FieldRule
Bucket name3–63 chars; lowercase letters, digits, hyphens, and dots only; must start/end with a letter or digit; no consecutive dots; must not start with xn--; must not end with -s3alias; must not look like an IPv4 address.
Object key / folder path / prefix≤ 1024 UTF-8 bytes; no NUL or control characters (tab excepted); no .. path-traversal segments.
RegionMust be one of the 15 fixed AWS region codes — see S3 Server (satellite).
KMS Key IDRequired, 8–2048 chars, whenever Server-Side Encryption is aws:kms.
Max Keys1–1000 (AWS's own hard ceiling on a single list/search page).

Each rule maps to a specific error code — see Input & Output for the full error model.

Tenant Isolation

Every object key, folder path, and search prefix is automatically rewritten under tenants/{tenantId}/ before being sent to S3 — on 10 of the 13 operations (everything except bucket/create, bucket/delete, and bucket/list-all, which act on the bucket itself). See Input & Output for the full effectiveKey model.

Storage Classes

Available on object/upload via the storageClass field. Choose the right class to balance cost, availability, and retrieval speed.

Storage ClassBest ForRetrievalCost Profile
STANDARDFrequently accessed data, active workloadsMillisecondsHighest storage; no retrieval fee
INTELLIGENT_TIERINGUnknown or changing access patternsMillisecondsAuto-tiers; small monitoring fee per object
STANDARD_IAInfrequently accessed, rapid retrieval neededMillisecondsLower storage; per-GB retrieval fee
ONE_ZONE_IAReproducible infrequent data, single-AZ OKMilliseconds~20% less than STANDARD_IA; single AZ only
GLACIERLong-term archive, retrieval in minutes to hours1 min – 12 hrsVery low storage; retrieval fees apply
DEEP_ARCHIVECompliance archives, accessed <1x/year12 – 48 hrsLowest storage; highest retrieval fee
Non-AWS backends: storage classes and canned ACLs are AWS-specific concepts passed through verbatim to whatever Service URL the connected satellite points at. Non-AWS backends (Backblaze B2, MinIO, R2) may ignore or reject some of these — see S3 Server (satellite).

MIME Type Reference

Use with object/upload's contentType field.

File TypeExtensionContent-Type
PDF Document.pdfapplication/pdf
JSON Data.jsonapplication/json
CSV Spreadsheet.csvtext/csv
Plain Text.txttext/plain
Markdown.mdtext/markdown
JPEG Image.jpg / .jpegimage/jpeg
PNG Image.pngimage/png
ZIP Archive.zipapplication/zip
Excel Workbook.xlsxapplication/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Word Document.docxapplication/vnd.openxmlformats-officedocument.wordprocessingml.document
HTML File.htmltext/html
Binary / Unknownvariousapplication/octet-stream
Key naming conventions: Use structured objectKey paths with meaningful segments to keep buckets organized at scale — e.g. {document_type}/{year}/{month}/{entity_id}/{filename}. Remember the tenant prefix is added automatically on top of whatever you type — see Input & Output.