This is work originally slated for milestone 2 but requested to be pushed forward to milestone 1. To accomplish this, some instance must be created on AWS and it must be able to communicate with a local process.
Possible Plan
The mobile team from last semester was working to do the same thing, but ran into trouble creating the connection. The main issue was getting through their local sub-net (on campus or otherwise). Something on the cloud would attempt to establish a connection with a local process, but would fail because it would not know "how" to find the process in their router's sub net. This can be fixed by:
using a VPN
port forwarding
Obviously the 2 options listed above are not the only way to establish a connection. For the purpose of demonstrating functionality, the goal is to be able to call a backend endpoint from an AWS instance.
Overview
This is work originally slated for milestone 2 but requested to be pushed forward to milestone 1. To accomplish this, some instance must be created on AWS and it must be able to communicate with a local process.
Possible Plan
The mobile team from last semester was working to do the same thing, but ran into trouble creating the connection. The main issue was getting through their local sub-net (on campus or otherwise). Something on the cloud would attempt to establish a connection with a local process, but would fail because it would not know "how" to find the process in their router's sub net. This can be fixed by:
Obviously the 2 options listed above are not the only way to establish a connection. For the purpose of demonstrating functionality, the goal is to be able to call a backend endpoint from an AWS instance.