I know Plex uses AWS for services. I was hoping to narrow down the scope of what they use so I don’t have open my firewall to the entire AWS IP EC2 range. (532 subnets or so)
Yes, to my knowledge, you should retain the full feature set. But full disclosure, I don’t use this list. And bear in mind that if you want to access the server remotely, you still need to poke holes in your firewall for all the remote clients which will be accessing your server.
However… keep in mind that’s only the Plex side of things.
If you have remote clients and lock down your firewall to only those IPs, you will at best get an indirect / relay connection when playing stuff from outside your home network (with a chance of not getting a connection at all).
Are remote users all relayed through AWS?
My goal is to permit as few as possible. I have geo location locked down for my country. So if I permit those Plex IPs, then anytime I’m traveling within my country, I should be fine. (geolocaton list obviously being current)
No. Plex establishes a direct connection between your server and the client.
Only if that fails it attempts an “indirect connection” (limited to 1 Mbit/s max; 2 Mbit/s for Plex Pass users). That indirect connection goes through a Plex server.