Bucket management

Each bucket has four independent configurations:

Configuration	Effect
Policy	Define who can do what with the bucket/object (JSON, fine-grained)
CORS	Allow browsers on another domain to access the bucket (web upload, CDN)
Lifecycle	Automatically delete or transition objects by age (cost optimisation)
Versioning	Keep older versions on overwrite/delete (data protection)

Bucket Policy

S3-compatible JSON policy — fine-grained control over Action, Resource and Principal.

Bucket CORS

Cross-Origin Resource Sharing so web apps on other domains can talk to the bucket.

Bucket Lifecycle

Expire objects by age, clean up failed multipart uploads and manage old versions.

Bucket Versioning

Keep multiple versions of the same object — guard against accidental deletes and overwrites.

Pair Versioning with Lifecycle

Enable Versioning for important data and add a Lifecycle Rule that removes old versions after N days — both data protection and cost control.