How to upload to ScorePlay via S3 Client (Remote Upload v2)?

💻 Environment/Context

• Upload
• Storage

❓ Issue/Question

• How can I upload to ScorePlay via S3 Client (Remote Upload v2)?

👌 Resolution/Answer

Remote Upload v2 creates a bidirectional sync between your S3 bucket and ScorePlay's collection structure. Collections you create in ScorePlay appear as folders in S3; folders you create in S3 become collections in ScorePlay. Files uploaded to an S3 folder inherit all tags and settings configured on the corresponding ScorePlay collection

• Prepare your collections in ScorePlay (recommended)
• Before uploading, set up your destination collections in ScorePlay:
  • Log in to your ScorePlay workspace
  • Create the collections and sub-collections you need
  • Assign the appropriate tags and teams to each collection

💡 Tip: Configuring collections before uploading ensures media is tagged and enriched correctly from the start. Tags, roster, and AI enrichment settings are inherited by uploaded content

⚠️ Note: If you skip this step and upload into new S3 folders, those folders will still become collections — but their tag and roster settings will be empty and will require manual configuration afterwards. Tags from parent collections will still be applied

• Install an S3 client
  • Install any S3-compatible file transfer client:
    • Cyberduck (recommended) | cyberduck.io
      • ⚠️ Note: For Cyberduck, use version 9.1.1 for best compatibility. Newer versions may cause permission issues. Older versions are available at cyberduck.io/changelog
    • FileZilla Pro | filezilla-project.org
    • WinSCP | winscp.net
    • AWS CLI | aws.amazon.com/cli

• Connect to your S3 bucket
  • Using Cyberduck as an example:
  • Open Cyberduck and click + (bottom-left) to create a new bookmark
  • Fill in the connection details using the credentials from your CSM:
    • Protocol = Amazon S3
    • Nickname = A recognizable name (e.g., "ScorePlay S3")
    • Server = Provided by your CSM
    • Access Key ID = Provided by your CSM
    • Secret Access Key = Provided by your CSM
    • Path = Provided by your CSM
  • Close the bookmark window
  • Double-click your new bookmark to connect
  • You should see a folder structure matching your ScorePlay collections. If you see an error, check credentials for typos or trailing spaces — or try downgrading to Cyberduck v9.1.1
•  Upload your files
  • Navigate to the target collection folder and drag and drop files into the client window (or right-click → Upload). Wait for the transfer to complete
  • You can also drop an entire folder structure with content — each folder becomes a collection in ScorePlay, and sub-folders become sub-collections. This is especially useful for migrations where your media is already organised in a folder tree

⚠️ Note:  For very large bulk imports (100 GB+), coordinate with your CSM to optimise sync settings before uploading

• Confirm media has landed
  • ScorePlay detects new files automatically. Media appears in your Media Library in the corresponding collection. If AI tags were configured on the collection, they are applied at import time

🔖 Notes 

• Browser-based uploads degrade at large file sizes and don't support automated pipelines. S3 Remote Upload uses Amazon S3's transfer infrastructure, which is faster and more reliable for multi-GB media. Because collection paths in S3 mirror ScorePlay collection names, upload destinations are predictable — enabling automation via scripts, Make.com, n8n, or video encoding tool outputs
  • Example path structure: https://remote-upload-v2.s3.amazonaws.com/{org-id}/Season%202025-26/London%20vs%20Paris
  • Your {org-id} is provided by your CSM. Always URL-encode the folder path
• Never share your S3 credentials — they are unique to your organisation. Treat them like a password
• Tags configured on a collection are applied at upload time — content uploaded before a collection is configured will not be retroactively enriched
• For recurring event workflows (e.g., match day uploads), collection paths follow your naming convention and are predictable — pre-configure your upload pipeline to target them directly
• The bidirectional sync works in both directions: create collections in ScorePlay, and they appear as S3 folders, or create folders in S3, and they appear as collections in ScorePlay — use whichever direction fits your workflow