Multi interfaces Additional Web Servers?

I don't believe so, at least not fully how you explained it. 

It is highly recommended not to have anyone connect to the primary poller instance, that is unless you lose your additional web servers and it's an absolute emergency.

What I would do is keep your PPE off limits to everyone except your SW support team.  I would host a SW instance for the admin team on AWS1 and then put a load balancer of some sort that supports AWS 2-6.  Your SW support team can then float between the PPE, their SW instance and the general population SW instance.  

You could then host 2 different SW instances on AWS 2-6 that utilize the load balancer.

But in all honestly, I don't really know what you would gain from all of this.  In the end all uses will, effectively hit the same DB, same PPE and the same environment.  There's little to no gain that i can see from doing this other than extra administrative work.

You're absolutely best option is 1 load balancer for all 6 AWS and then build manage everyone in teams with limited rights.... which you'll need to do no matter which direction you go.

Also your third concept is, as far as I know, not possible. All additional web service communication needs to be direct back to your PPE. 

I don't believe so, at least not fully how you explained it. 

It is highly recommended not to have anyone connect to the primary poller instance, that is unless you lose your additional web servers and it's an absolute emergency.

What I would do is keep your PPE off limits to everyone except your SW support team.  I would host a SW instance for the admin team on AWS1 and then put a load balancer of some sort that supports AWS 2-6.  Your SW support team can then float between the PPE, their SW instance and the general population SW instance.  

You could then host 2 different SW instances on AWS 2-6 that utilize the load balancer.

But in all honestly, I don't really know what you would gain from all of this.  In the end all uses will, effectively hit the same DB, same PPE and the same environment.  There's little to no gain that i can see from doing this other than extra administrative work.

You're absolutely best option is 1 load balancer for all 6 AWS and then build manage everyone in teams with limited rights.... which you'll need to do no matter which direction you go.

Also your third concept is, as far as I know, not possible. All additional web service communication needs to be direct back to your PPE.