Hi Gokul,
Thanks for the reply. Yes as far as I understand it AWS should be pushing 0.0.0.0/0 through the VPN. We have enabled route propagation for the two route tables that go with our VPC. Just in case, we've added a route from our 192.168.53.0/24 to the virtual private gateway (vgw-07dd....) which is attached to the VPN. This can be seen on the screenshot below.
Applying this small change to the route table in AWS didn't solve the issue.
When running your suggested 'get route' it returns the following information:
Any ideas what I'm missing or what I've miss configured wrong?
Best wishes,
Christopher