Platform/OS
Cross-platform
Category
Media & Video Tools
Anchorpoint
Anchorpoint is a simple file organizer and version tracker designed for creative teams working with large video, design, and 3D projects. It works like a smart shared hard drive that automatically keeps every version of your files safe and makes it easy to find the exact one you need without digging through messy folders. It uses S3-compatible object storage behind the scenes to hold all your actual files in a cheap, reliable cloud space that can grow as big as you need. This storage approach means your team can access the same up-to-date files from anywhere without slowing down your computer or paying for expensive servers. The real-world value is that creatives spend less time hunting for files and worrying about losing work, while only paying for the storage they actually use.
Connection / Setup
- Create an account and log in to DiskSpace
- Click I'm ready to set up my storage
- Enter Bucket Name following the instructions
- Click Create Bucket and wait for it to be generated
- Find your Endpoint URL, Access Key, and Secret Key in the S3 Client Configuration section for use below
Connect Anchorpoint to DiskSpace.sh
Anchorpoint supports S3-compatible storage. Follow the steps below to connect your DiskSpace.sh bucket.
Connection Steps
- Open Anchorpoint and navigate to the Connections or Storage panel.
- Click Add Connection and select S3 Compatible Storage as the type.
- Fill in the credentials using the values provided by DiskSpace.sh.
- Ensure Path-style requests is enabled (required for DiskSpace.sh).
- Save the connection and test the bucket access.
Region: Leave empty or use
us-east-1
Important: Path-Style Requests
DiskSpace.sh requires path-style URLs. Anchorpoint must be configured to use this format:
https://s3.diskspace.sh/bucket-name/key
Troubleshooting
- Ensure you selected Path Style or Force Path Style in the connection settings.
- Verify your Access Key and Secret Key have the correct IAM permissions.
- Try region
us-east-1if leaving it blank doesn't work. - Confirm the Endpoint URL does not contain your bucket name.