Updated: March 2018<\/strong><\/p>\n \nVeeva delivered its first cloud applications to life sciences companies in 2007. At that time, public cloud infrastructure services such as Amazon Web Services (AWS) were just emerging and not ready for global enterprises or regulated applications. Therefore, Veeva built its operations infrastructure in a managed hosting model. In this model, Veeva leased specific hardware devices, network capabilities, and managed services from managed hosting providers.\n<\/p>\n \nToday, public cloud services from companies such as Amazon, Google, and Microsoft have achieved global enterprise scale and the ability to support complex regulatory and compliance requirements. Using public cloud services allows solutions providers like Veeva to leverage the most advanced infrastructure and provide a more innovative, scalable, global, predictable, and secure environment.\n<\/p>\n \nAfter a comprehensive evaluation of public cloud vendors, Veeva determined AWS is the right primary cloud infrastructure provider to meet Veeva customers\u2019 growing needs as we look to the future.\n<\/p>\n \nWhen will the move to AWS occur?<\/strong><\/p>\n Timing for the move of Veeva\u2019s application services to AWS is as follows:<\/p>\n \nVeeva CRM –<\/strong> Veeva CRM transactional data will remain on salesforce.com\u2019s infrastructure, and will therefore not be impacted by the AWS move. Only the Veeva CRM application server and supporting infrastructure is moving.\n<\/p>\n \nThe Veeva CRM 17R2 release in July 2017 was the final major release on managed hosting. All customer orgs have been moved and currently reside on the AWS infrastructure.\n<\/p>\n<\/li>\n \nVeeva Vault \u2013<\/strong> The Veeva Vault 17R2 release in August 2017 was the final major release on managed hosting. All customer Vaults have been successfully moved to AWS.\n<\/p>\n<\/li>\n \nVeeva Network \u2013<\/strong> The Veeva Network 17R3 release in December 2017 will be the final major release on managed hosting. The move to AWS will occur during a weekend in April 2018, prior to the 18R1 release of Veeva Network. Customers will be notified a minimum of 30 days prior to the actual move date. There will be a brief, scheduled downtime window during the move.\n<\/p>\n<\/li>\n<\/ul>\n \nTo ensure conformance with local regulations, application data will remain in the same geographic regions \u2014 U.S. (West and East Coast), Europe (Germany and Ireland), and Japan \u2014 and are subject to the same security controls as currently implemented in managed hosting. Data will be backed up within the same region as the primary processing region.\n<\/p>\n \nVeeva CRM transactional data will remain on salesforce.com\u2019s infrastructure with no change in geographic location of the primary processing location or the backup location.\n<\/p>\n \n \nVeeva\u2019s Quality and Compliance team has ensured that the new AWS infrastructure is qualified and that critical regulated functionality of the Veeva applications is validated on AWS infrastructure. Equivalent procedural controls, security frameworks, and monitoring infrastructure will be applied to the production environment to ensure the products are maintained in a validated state.\n<\/p>\n \nAWS is Privacy Shield certified and has entered into the EU Model Clauses and a Business Associate Agreement (HIPAA) with Veeva.\n<\/p>\n \nThe following compliance related documentation will be available to customers at least 30 days prior to initial moves:\n<\/p>\n\n
\nWhere will customer data reside?<\/strong>\n<\/p>\n
\nWhat about validation, compliance, and data privacy?<\/strong>\n<\/p>\n