This page covers the technical steps for ending your 2i2c service and ensuring a smooth transition.
Timeline and communication¶
We recommend giving at least 30 days notice before ending service to ensure proper transition:
Contact 2i2c support: Contact support with your planned end date
Notify hub users: Inform users about the timeline and their responsibilities for data export
Coordinate with 2i2c: Work with the 2i2c team to schedule final steps
Exporting data¶
User directories and files¶
Each hub user must download their own files:
Direct users to download their home directory
Set a clear deadline for data export (at least 1 week before service end)
Remind users that data will be permanently deleted after service ends
S3 bucket archives (if applicable)¶
If 2i2c has archived home directories to an S3 bucket:
Request access credentials from 2i2c support
Follow the S3 archive download instructions
Download archives before the final service date
Replicating your infrastructure (optional)¶
2i2c’s infrastructure is fully open-source as part of our Right to Replicate commitment.
If you want to continue running a JupyterHub independently:
See Replicate your own JupyterHub for step-by-step replication instructions
Review the infrastructure repository for your hub’s configuration
Final steps¶
Once data is exported and any replication is complete:
Confirm with 2i2c support that all data export is complete
Review final billing for any outstanding cloud costs
Infrastructure cleanup: Cloud resources will be deprovisioned
Questions?¶
Contact 2i2c support for assistance with any aspect of ending service.