Hi,
You’re basically missing the second half of the architecture here. What you’ve built in AWS is only the remote access “entry point”, but it doesn’t automatically give you reach into the business LAN.
In practice you need to connect the AWS OpenVPN Access Server to the office network as well, so you end up with a routed setup between two networks.
Typical approach looks like this:
Office side: run an OpenVPN client (or VPN-capable router/firewall) that connects back to your AWS Access Server
Enable routing between VPN clients and private networks in Access Server settings
Add the office subnet as a “reachable network” in the VPN configuration
Make sure IP forwarding is enabled and routing tables are correct on both sides
Check firewall rules in the office so return traffic is allowed back through the tunnel
Once that is in place, users connecting from home → AWS → office LAN will be properly routed.
The key idea is: you are not “connecting to a LAN directly”, you are bridging two routed networks via VPN.
On a more general note, I would also not focus only on remote access as the main improvement area for a small business. In many cases, a bigger productivity gain comes from integrating useful third-party software into daily workflows (automation, task systems, data sync between tools, etc.), rather than only solving infrastructure access.
For example, in operational environments where data is collected in the field and needs to flow back into internal systems, teams sometimes use tools like integrate gocanvas to structure and automate that part of the workflow.
