Customers sending SFTP files to the server in the United States need to transition to the new SFTP server located at Azure South Central US. By storing your SFTP files at Azure, iOFFICE can provide you with the same level of protection and security we introduced with the recent Azure migration, including data-at-rest encryption for all files stored on the Azure SFTP server.
Refer to the following sections for more detailed information on completing this process.
What do we need to do to prepare?
Alert the appropriate IT resources responsible for this managing this change and complete the following steps prior to scheduling the migration.
- Whitelist 184.108.40.206 to allow your company to send and retrieve files on the new SFTP server at Azure (using port 22), and continue sending your user file to the existing SFTP at Rackspace for now.
- Coordinate with your Account Manager to schedule a date and time for your migration. This process will involve an Integration Manager who will complete the setup required on our end and confirm the process is working as intended.
- On the scheduled date, you will switch your SFTP server address to sftp3.iofficeconnect.com, which is the new address for the Azure SFTP server. The update path for the sftp3 server must point to an IN folder (we recommend that you work with your Account Manager to complete this process). Once the change is made, let your Account Manager know (or call 713-526-1029) so we can confirm that you have made the change.
Note: The IN folder path requirement includes customers who currently direct their file process path to drop to the 'root' folder of the existing sftp2 instance. Please refer to the Root to IN Folder Path Update section and work with your Account Manager to complete this process.
All migrations must be finalized by April 1st, 2019. If you have any questions or would like additional information, contact your Account Manager.
Frequently Asked Questions
- Are there any other IP's we should be whitelisting outside of the 220.127.116.11 listed in the notice?
A: This is the only IP needed for the SFTP migration. However if you have not already prepared for the Azure server migration please see this guide for additional IP addresses.
- How will the DNS be handled? We are currently using sftp2.iofficeconnect.com or sftp.iofficeconnect.com
A: sftp3.iofficeconnect.com will be used for the Azure SFTP server. After migration is complete sftp2 and sftp will be migrated to point to the new IP address. However we recommend all existing customers use sftp3 before the migration to ensure a smooth transition.
- Will our data be migrated to the new SFTP? Is there any data archival process we need to be aware of prior to the migration?
A: All data is currently being replicated to both environments so there will be no data loss or downtime when transitioning.
- Will our credentials used to authenticate change?
A: All credentials (username, passwords and keys) are synced to the new environment so no changes will be required by the customer.
- How can we schedule this migration with iOFFICE? We need to make sure we know exactly when the migration will happen to avoid any downtime with our feeds.
A: Because all data is replicated the change can be made at any time without any downtime or data loss. However your account manager can work with you to help schedule a time for testing and verification if desired.
Root to IN Folder Path Update
For security reasons, files cannot be created in the `root` of a folder anymore. These files must be created in a subdirectory. For this reason, we are enforcing an `IN` folder of traffic to iOFFICE and an `OUT` folder for from iOFFICE. This is an impactful but simple change, that should be completed as follows.
- Schedule a date and time with your Account Manager.
- On the scheduled date, iOFFICE will update our directory before noon. iOFFICE will reply to the ticket with the path information and folders that moved.
- The client has from noon until the end of the business day to make the necessary changes to update their side (this may include updates to job launchers and watchers depending on the client setup).