# Perspective Loadbalancing on AWS

**URL:** <https://forum.inductiveautomation.com/t/perspective-loadbalancing-on-aws/95810>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [September 10, 2024, 4:00pm UTC](https://forum.inductiveautomation.com/t/perspective-loadbalancing-on-aws/95810 "2024-09-10T16:00:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![david\_ludwig1](https://avatars.discourse-cdn.com/v4/letter/d/c57346/32.png) [@david\_ludwig1](https://forum.inductiveautomation.com/u/david_ludwig1)\
**Post date:** [September 10, 2024, 4:00pm UTC](https://forum.inductiveautomation.com/t/perspective-loadbalancing-on-aws/95810/1 "2024-09-10T16:00:59Z")

</div>

We currently use an EC2 instance to host an Ignition license. This instance is only used to provide Perspective webpages to users and we call this our FE server. We have several backend EC2/Ignition instances that collect and historize data from of remote plants.

Our user based is growing and so I need to scale out the FE perspective component of the system. Are there any special considerations I need to concern myself with if I create a new EC2 instance with Perspective loaded on it, and connect it to a load balancer? How will the session data be handled? Do I still need to configure the two instances as a primary and backup? Any other information will be appreciated.

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [September 10, 2024, 6:21pm UTC](https://forum.inductiveautomation.com/t/perspective-loadbalancing-on-aws/95810/2 "2024-09-10T18:21:22Z")

</div>

While I've never set up load balancing with Perspective, I can tell you that you will not be using primary and backup, and if you're trying to scale out, you won't need redundancy on them and will need to use full licenses on these instances.

Typically, the load balancer will try to use "sticky sessions" to make sure once a session is started on one server/FE that the load balancer will keep that client connected to the same FE server throughout the session lifetime.

---

<div class="post-metadata">

**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\
**Post date:** [September 12, 2024, 3:00pm UTC](https://forum.inductiveautomation.com/t/perspective-loadbalancing-on-aws/95810/3 "2024-09-12T15:00:04Z")

</div>

Yeah. The built-in Ignition redundancy feature is NOT what you want for load balancing Perspective. I went down that path briefly and tried to explain some of my pain over in this thread:

> [@Load Balancer Suggestions](https://forum.inductiveautomation.com/t/load-balancer-suggestions/83318):
>
> Has anyone done any implementations using load balancers? Any particular software that you would recommend? We were looking into Nginx, but would preferably like to use a windows based application rather than Linux. Would like to hear about some of your experiences.

Your multiple FE servers should have nearly identical configs, not be aware of each other, but all talk to the backend Ignition servers via the gateway network.

You will want the AWS load balancer to be sticky in some form. You can use a simple one based on just source IP, but you can get fancier and look for the JSESSIONID cookie if you want.