Automated Subscriber Uploads: S3 vs SFTP — How to Send Your SIS File to uConnect

Overview

uConnect’s Automated Subscriber Uploads (also called SIS) keep your subscriber list fresh by importing a CSV file from a secure, client-specific AWS S3 bucket on a daily or weekly schedule. Your IT team pushes one CSV file into your bucket; uConnect ingests it automatically and applies your mapping rules.

Our detailed instructions for set up are outlined in this article, but read below about how the set-up process works and what methods we use for file storage and syncing.

Short answer: We do not accept files via SFTP. Automated Subscriber Uploads (SIS) are delivered to a dedicated, private AWS S3 bucket using S3 credentials (Access Key ID and Secret Access Key).

Why we use S3 (not SFTP)

Security and simplicity: Each client receives a private S3 bucket and unique credentials with least-privilege access to that bucket only.
Automation-ready: S3 works seamlessly with the AWS CLI, SDKs, and server schedulers (cron, Task Scheduler) for reliable automation.
Operational resilience: A single, consistently named CSV ensures predictable processing and clear audit logs.

SFTP is not supported. We do not host an SFTP endpoint and cannot accept inbound SFTP file drops. Please plan to deliver your SIS CSV to the provided S3 bucket.

Important: SFTP is not supported. We do not host an SFTP endpoint and cannot accept inbound SFTP file drops. Please plan to deliver your SIS CSV to the provided S3 bucket.

How the setup works

An admin in your uConnect dashboard navigates to Engage → Subscribers → Automate Subscriber Uploads and clicks “Begin Automatic Subscriber Uploads Process.”
- This creates your institution’s private S3 bucket and sends setup instructions to the admin, including a secure link to retrieve the Access Key ID and Secret Access Key. If needed later, admins can use “Resend Instructions” or “Regenerate Credentials.”
Your IT team uploads a single CSV to the S3 bucket on a regular cadence (weekly or daily is common). Subsequent uploads should overwrite the same filename.
- AWS CLI (scriptable on Windows, macOS, Linux)
- AWS SDKs (e.g., Python Boto3), CI/CD jobs, or other automation tools
- Point-and-click tools that support Amazon S3 (e.g., FileZilla Pro, Cyberduck) for occasional/manual uploads
Once a file is detected in your bucket, the File Name appears in the dashboard.
Admins choose sync and email options, enable Auto Deprovision if desired, and map file columns to subscriber attributes and Community Groups.
uConnect processes the latest CSV on your selected schedule (weekly/daily). You can also run an on-demand import from the dashboard.

What your IT team needs

Bucket name: Provided via secure email link from your uConnect dashboard
Credentials: AWS Access Key ID and Secret Access Key (least-privilege to your bucket)
Region: us-east-1 (unless specified otherwise)
File: One CSV that follows standard CSV rules (RFC 4180), with a header row and one row per user. Use the same filename for each upload.

Accepted delivery methods

Windows: PowerShell + AWS CLI, scheduled with Task Scheduler
Linux/macOS: bash + AWS CLI, scheduled with cron
Any OS: AWS SDKs or automation tools that support S3
FileZilla Pro or Cyberduck using the provided S3 credentials

Best practice: Script the upload with the AWS CLI and schedule it. Overwrite the same CSV filename each run. Keep credentials secure and rotate if staff changes.

Security and compliance notes

Transport security: Uploads occur over HTTPS to Amazon S3.
Access control: Your keys grant access only to your institution’s bucket/object path per least-privilege policies.
Data handling: The platform reads only the CSV you upload. Admins can view import logs and optionally download the current file via the dashboard.
Key management: Retrieve credentials via a time-limited secure link from your dashboard. Admins can regenerate keys at any time.

Common questions

Can we send our file via SFTP?

No. We only accept SIS files via the dedicated AWS S3 bucket using S3 credentials. If you currently generate a file to SFTP, adapt your automation to copy that same file to S3 using the AWS CLI or an S3-capable tool.

Which tools can we use to upload?

Any tool that supports Amazon S3. Most clients use the AWS CLI on a server with a scheduled task. Others use AWS SDKs, CI jobs, or point-and-click tools (FileZilla Pro, Cyberduck) for testing or one-time drops.

Do you require deltas or a full file?

Provide a full file each time (no deltas). Always overwrite the same filename so the system consistently ingests the latest data.

What file format is required?

CSV with a header row following standard CSV rules (RFC 4180). If fields contain commas, wrap them in double quotes.

How will we know the file was received?

After upload, the file appears in the File Name dropdown in your dashboard. Admins can run an on-demand import or wait for the scheduled run and check the SIS Sync Log for results.

Step-by-step upload examples

Windows (PowerShell + AWS CLI)

Install AWS CLI v2, then run: aws configure and enter the provided keys and region. 2) Upload: aws s3 cp "C:\Data\student_feed.csv" "s3://YOUR_BUCKET_NAME/student_feed.csv" --region us-east-1 3) Verify: aws s3 ls "s3://YOUR_BUCKET_NAME/" --region us-east-1 4) Schedule weekly with Task Scheduler.

Linux/macOS (Terminal + AWS CLI)

Install AWS CLI (Homebrew, pip, or bundled installer). 2) Configure: aws configure. 3) Upload: aws s3 cp /path/to/student_feed.csv s3://YOUR_BUCKET_NAME/student_feed.csv --region us-east-1. 4) Verify: aws s3 ls s3://YOUR_BUCKET_NAME/ --region us-east-1. 5) Automate with cron (e.g., Saturdays 8:05 AM): 5 8 * * Sat aws s3 cp /path/to/student_feed.csv s3://YOUR_BUCKET_NAME/student_feed.csv --region us-east-1.

Manual (FileZilla Pro or Cyberduck)

Open a new S3 connection, enter Access Key ID, Secret Access Key, and region us-east-1. Connect, drag-and-drop your CSV into the bucket, and choose Overwrite when prompted. Refresh to confirm the timestamp updated.

Troubleshooting

Confirm exact bucket name and region, then refresh. Ensure you used the expected filename and overwrote any prior file.
Re-check the Access Key and Secret. If needed, ask your uConnect admin to “Resend Instructions” or “Regenerate Credentials.”
Validate CSV formatting (header row present, RFC-compliant quoting, no stray delimiters). Ensure you uploaded a complete file, not a placeholder.