Symantec is committed to providing a highly-scalable and reliable, cloud-based, strong authentication service. Due to incredible growth and adoption of VIP, we have made changes to the VIP infrastructure to continue delivering quality service by migrating VIP to Amazon Web Services (AWS). Many months of extensive planning and preparation went into this next-generation VIP service. VIP services are no longer served from the former statically-provisioned data centers and now reside in AWS -- an elastic, highly-scalable and resilient public cloud infrastructure.
Symantec’s goal was to transparently and seamlessly migrate our customers through both phases of this migration. To that end, it is our hope that we accomplished this.
> 24 OCT 2018: The VIP AWS MIGRATION IS 100% COMPLETE. All VIP traffic is flowing to end-points in AWS.
> 11 Jun 2018: Phase 1 complete. Phase 2 is underway
> 29 May 2018: Migration times added under What Is Happening
> 05 MAY 2018: Migration progress will be posted to our VIP Status Page. Visit and subscribe to receive updates.
> 04 APR 2018: Phase 1 date change. Phase 1 will begin on June 4, 2018. Phase 2 is planned for mid-summer 2018. Phase 2 Details and dates will be updated.
> 04 APR 2018: Additional IP address-based connectivity options added to the Prepare your environment for the Migration of VIP Services Platform to AWS and Test your VIP environment for the Migration of VIP Services Platform to AWS.
The following information was published pre-migration.
The VIP AWS migration will occur in two phases. This approach is designed to reduce overhead and operational risks. We do not anticipate any service changes throughout this migration
PHASE 1 Complete
Completed. June 4, 2018 - Beginning at 2 PM PDT (9 PM UTC), all services-auth.vip.symantec.com traffic will be routed through the AWS cloud, then pass through back to the current Symantec VIP data centers (see graphic below). No transactions are occurring on AWS servers during this phase. All VIP Services will continue to be served from the existing VIP data centers.
Completed. June 5, 2018 - Beginning at 2 PM PDT (9 PM UTC), all services.vip.symantec.com traffic will be routed through the AWS cloud, then pass through back to the current Symantec VIP data centers (see graphic below). No transactions are occurring on AWS servers during this phase. All VIP Services will continue to be served from the existing VIP data centers.
Completed - At 2 PM PDT (9 PM UTC), all userservices-auth.vip.symantec.com traffic will be routed through the AWS cloud, then pass through back to the current Symantec VIP data centers (see graphic below). No transactions are occurring on AWS servers during this phase. All VIP Services will continue to be served from the existing VIP data centers.
PHASE 2 Completed
All VIP customers and VIP services are being migrated to the VIP AWS platform. The anticipated completion is mid-October 2018.
To receive real-time notifications, subscribe to our VIP Status Page.
VIP traffic will be seamlessly directed and balanced during both phases of the migration. We do not anticipate any disruption or change in your service before, during or after these changes.
If connectivity to VIP is lost (see figure 2 above), VIP traffic can temporarily be forced back to the legacy VIP datacenter (see figure 1 above) by bypassing AWS. Contact VIP Technical Support for assistance with these changes. This method involves the PDF attached to this KB article. This document contains the locations of Symantec URLs within your particular VIP integration(s). After connectivity issues are resolved, revert back to the original Symantec URLs. (note: do not use verisign.com URLs)
Yes. Testing must be performed on your VIP Enterprise Gateway(s), custom server application(s), and any other component(s) where VIP Service traffic is served involved can communicate with the VIP Service. See Testing your VIP environment for the Migration of VIP Services Platform to Amazon Web Services for testing procedures.
When your organization has completed pre-phase 1 testing, let us know the outcome (successful or unsuccessful) at https://migration.vip.symc.io/connect_feedback. If you have any issues and need assistance, we will use this information to contact you.
Symantec is committed to helping our customers achieve success during this transition. If you have further questions or need technical support:
Where will the service be hosted?
After the migration is complete, the service will be hosted in the United States, in the AWS Oregon [us-west-2] and the Virginia [us-east-1] regions.
What can I do if I cannot whitelist domains?
See AWS Configuration Requirements for the Migration of VIP Services Platform to Amazon Web Services for IP netblocks that you must add to your firewall to allow outbound connectivity to the AWS-hosted platform. Do not remove existing netblocks for legacy VIP data centers.
Will the service capabilities change as a result of this migration?
There will be no functional changes in VIP. All services will continue to function seamlessly throughout this migration.
Are there changes to my Service Level Agreement?
No. Your existing Service Level Agreement applies to the new environment.
How will I know when my service was migrated?
This migration will be transparent to you. We will alert you when your service has moved.
Can I opt out of the migration?
No. Symantec will completely exit its legacy data centers and terminate those operations by calendar Q4 of 2018.
Will the routed traffic through the AWS-hosted platform increase latency?
There will be no observable change in speed. Symantec testing has shown an average increase in latency after Phase 1 with the new route to be ~20ms.
I use VIP Pilot or Partner Lab environments. Will these be migrated to AWS as well?
Both VIP Pilot and VIP Partner Lab environments will function until October 2018.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.