Skip to content

Add alpha bucket commands for Object Storage data plane operations #1753

Open

Description

Problem description

The STACKIT CLI today only covers the Object Storage control plane (the object-storage commands for the service instance). Once a bucket exists, every data plane operation — listing, uploading, downloading, moving, or deleting objects — requires a third-party tool, pre-configured with the STACKIT storage endpoint and the access key credentials:

aws --endpoint-url https://object.storage.eu01.onstackit.cloud s3 ls s3://my-bucket

That means users have to manage Object Storage credentials, regions, and endpoints outside of the STACKIT CLI — configuration drift and an extra tool dependency for something that is core day-2 work after creating your first bucket.

Proposed solution

Add an Object Storage data plane command group to the STACKIT CLI:

stackit alpha bucket ls        # list buckets or bucket contents (--recursive for flat listing)
stackit alpha bucket cp        # copy objects/directories between local and Object Storage (--recursive)
stackit alpha bucket mv        # move objects, bucket-to-bucket via server-side copy (--recursive)
stackit alpha bucket mb        # create a bucket
stackit alpha bucket rb        # delete an empty bucket
stackit alpha bucket rm        # delete objects (--recursive --force for bulk delete)
stackit alpha bucket presign   # generate a time-limited read URL without exposing credentials

Buckets and objects are addressed directly with STACKIT Object Storage URLs, virtual hosted or path style:

https://my-bucket.object.storage.eu01.onstackit.cloud/dir/file.txt
https://object.storage.eu01.onstackit.cloud/my-bucket/dir/file.txt

Credentials are picked up from --access-key-id/--secret-access-key flags, STACKIT_OBJECT_STORAGE_ACCESS_KEY_ID / STACKIT_OBJECT_STORAGE_SECRET_ACCESS_KEY environment variables, or the config file (i.e. the same credentials created with stackit object-storage credentials create, with no extra setup). The region flag (--region) resolves the default endpoint, matching the rest of the CLI.

Implemented as an alpha command group.

Alternative solutions

  • Keep using the AWS CLI with --endpoint-url (current state): works, but duplicates credential/endpoint management outside the CLI.
  • Other third-party tools (e.g. rclone): same problem, plus another dependency to install and configure.

Additional information

Activity

  1. gfelbing commented on Nov 19, 2026

    @gfelbing
    Contributor

    I really like it!
    Typing stackit instead of aws is a way more sovereign user experience

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions