Object Storage (S3-Compatible)

Yes. Leafcloud object storage is fully compatible with Terraform's S3 backend:

terraform {
  backend "s3" {
    bucket                      = "tf-state"
    key                         = "my-project/terraform.tfstate"
    region                      = "europe-nl-ams1"
    access_key                  = "YOUR-ACCESS-KEY"
    secret_key                  = "YOUR-SECRET-KEY"
    skip_credentials_validation = true
    skip_requesting_account_id  = true
    skip_s3_checksum            = true
    skip_region_validation      = true
    use_path_style              = true
    endpoints = {
      s3  = "https://leafcloud.store"
      sts = "https://leafcloud.store"
    }
  }
}

See our full Terraform backend tutorial for complete setup instructions.

Yes. Velero works well with Leafcloud object storage. See our Velero backup tutorial or use this quick configuration:

Credentials file:

# velero-credentials
[default]
aws_access_key_id=YOUR-ACCESS-KEY
aws_secret_access_key=YOUR-SECRET-KEY

Installation command:

velero install \
  --provider aws \
  --plugins velero/velero-plugin-for-aws:v1.5.0 \
  --bucket velero-backups \
  --secret-file ./velero-credentials \
  --backup-location-config region=europe-nl-ams1,s3ForcePathStyle=true,s3Url=https://leafcloud.store

No, versioning is not currently enabled on our Ceph cluster.

If versioning is a critical requirement for your use case, contact support to discuss options. Enabling versioning requires infrastructure changes and typically takes 4-8 weeks.

Alternatives:

• Implement application-level versioning (store versions with different object keys)
• Use backup tools that handle versioning independently (e.g., Kopia, Restic)

You can access object storage through multiple methods:

1. OpenStack Dashboard: Navigate to Object Store > Containers at create.leaf.cloud
2. S3-compatible clients: Cyberduck, MinIO Client, AWS CLI, or any S3-compatible tool
3. Programmatic access: boto3 (Python), AWS SDK, or the OpenStack CLI

Important: To use S3-compatible access, you need to create EC2 credentials (separate from your dashboard login):

openstack ec2 credentials create

This returns an access key and secret key for S3 API access.

Connection details:

• Endpoint: leafcloud.store (or https://leafcloud.store)
• Region: europe-nl-ams1
• Path Style: Enable "Path Style" or "Use path style URLs"

Cyberduck example:

1. Connection type: Amazon S3
2. Server: leafcloud.store
3. Access Key ID: Your EC2 access key
4. Secret Access Key: Your EC2 secret key

MinIO Client (mc) example:

mc alias set leafcloud https://leafcloud.store YOUR-ACCESS-KEY YOUR-SECRET-KEY
mc ls leafcloud

boto3 (Python) example:

import boto3

s3 = boto3.client(
    's3',
    endpoint_url='https://leafcloud.store',
    aws_access_key_id='YOUR-ACCESS-KEY',
    aws_secret_access_key='YOUR-SECRET-KEY',
    region_name='europe-nl-ams1'
)

Additional features:

• S3-compatible API for broad tool support
• Public/private containers
• Bucket policies & ACLs
• Multipart uploads for large files
• Presigned URLs for temporary access

This is the most common issue. There are two separate credential types:

Your dashboard password will NOT work for S3 access. You must generate EC2 credentials.

Quick fix:

# Generate new EC2 credentials
openstack ec2 credentials create

# Output example:
# access | 67fd5d4526114c97b87ace3981bd75cb
# secret | 9da048142f604573bef0fa97sfb3509d

Use the access value as your Access Key ID and secret as your Secret Access Key.