Uploading to DO Spaces via Boto3 prepends the bucket name to file keys

Hey!

I’ve just tested this with the following simple script and it seems to have worked as expected:

import os
import boto3
from dotenv import load_dotenv

# Load environment variables from .env file
load_dotenv()

# Set your credentials and region
spaces_key = os.getenv('DO_SPACES_KEY')
spaces_secret = os.getenv('DO_SPACES_SECRET')
spaces_region = os.getenv('DO_SPACES_REGION')
spaces_name = os.getenv('DO_SPACES_NAME')

# Create a session and client
session = boto3.session.Session()
client = session.client('s3',
                        region_name=spaces_region,
                        endpoint_url=f'https://{spaces_region}.digitaloceanspaces.com',
                        aws_access_key_id=spaces_key,
                        aws_secret_access_key=spaces_secret)

def upload_file(file_name, bucket, object_name=None):
    """Upload a file to an S3 bucket

    :param file_name: File to upload
    :param bucket: Bucket to upload to
    :param object_name: S3 object name. If not specified then file_name is used
    :return: True if file was uploaded, else False
    """
    if object_name is None:
        object_name = file_name

    # Upload the file
    try:
        client.upload_file(file_name, bucket, object_name)
    except Exception as e:
        print(f"Error uploading file: {e}")
        return False
    return True

# Example usage
file_name = 'test.txt'
bucket_name = spaces_name
object_name = 'destination/file.txt'

# Upload the file
if upload_file(file_name, bucket_name, object_name):
    print(f"File {file_name} uploaded successfully to {bucket_name}/{object_name}")
else:
    print(f"Failed to upload file {file_name}")

The file was uploaded to the destination directory without having the bucket name prepended two times:

Would you mind sharing an example code snippet that you are using so I could further look into this?

- Bobby

This is likely a result of using the bucket URL instead of the region URL as the endpoint_url. I faced the same issue and it was resolved by using the region URL. The reasoning behind using the bucket URL was due to the access key being scoped to a specific bucket. I assumed using the region URL might cause an AccessDenied error.