Important Update:Vuforia Experience Service will no longer support HTTP protocol in a future release

[ytella]

Due to security concerns, support for HTTP protocol will be deprecated in a future release of the Experience Service. This means that all communications will use HTTPS when publishing experiences or consuming published experiences in Vuforia View. Authoring and experience management will not be affected by this change. If you have any questions or concerns, please contact your Customer Success representative or use the comment feature on this post.

[T.Nakamura]

Hi , @ytella 

This announcement is very heavy impact for us.

Will above update apply to not only PTC cloud but also on-premises environment ?

PTC message is must be change our environment for http to https , right ?

[CS_9856442]

We would also like to raise a concern regarding the decision to discontinue HTTP support for the Vuforia Experience Service, as it could have a significant impact on many of our customers who have implemented on-premises Vuforia Experience Service configurations on AWS.

In typical AWS configurations, even when HTTPS is utilized on the frontend via an Application Load Balancer (ALB) HTTPS listener, the backend communication between the ALB and EC2 instances placed in a private subnet often relies on HTTP. While it is technically possible to redesign the backend communication to use HTTPS, there are practical challenges that must be addressed.

One key issue is that AWS Certificate Manager (ACM) — which provides free SSL/TLS certificates — does not support issuing certificates for backend connections between ALB and EC2 instances. As a result, users would be forced to purchase additional certificates from external Certificate Authorities, incurring unexpected additional costs for them. This could be problematic for customers, especially considering that self-signed certificates are not viable in this case due to ALB health check failures when self-signed certificates are used.

[ytella · Accepted solution]

Thanks for all your great feedback. We heard you and decided to not stop the support of HTTP. You gave us enough good reasons to not do so. However, we would encourage you to use HTTPS wherever this is possible to make sure your communication between View and the Experience Service is safe