Windows Server 2012 RDS//SQL Role Distribution

configuration:

amazon web services vpc, 10.11.0.0/16.  public subnet (dmz) 10.11.1.0/24.  private subnet 10.11.2.0/24

deployed in public subnet single windows 2012r2 server -- "pg1" -- rd web, rd gateway, rd connection broker (non-ha), , rd licensing. 

deployed in  private subnet dc, sql server (running construction software called viewpoint vista), , rd session host -- "sh1."  the session host has vista client installed.  that's it.  i able publish client without issue -- i.e it's working. 

sidebar -- eventually, aws vpc have vpn connection on-premise network, , file server role dfs namesapce , replication.

the aws-living windows rds serve 12 users.

issue:

in effort economize installation serves 12 users, want minimize "server sprawl."  i opinions if:

1. adding session host role "pg1" server (resides in dmz), installing vista client, , publishing client there idea or not.

2. or, keeping current rd session host "sh1" in place , adding file server role acceptable.

option 1 seems expedient; however, concerned having session host in dmz.  furthermore, need add files services aws network sooner or later -- so, there not seem savings.  i need argument convince colleagues bad idea (if it's not bad idea, ears).  

i concerned option 2 "over-role'ing" session host.

i quite new of this; so, please bear me.

opinions?

thanks in advance,

ed.

Windows Server  >  Remote Desktop Services (Terminal Services)