Connectivity
Cloud deployment
You may deploy your web application in your own cloud environment. Console does not impose any restrictions on how or where your application is deployed.
For example, you can deploy on:
- CStack
- Amazon EKS
- AWS Lambda with API Gateway
- Any other preferred setup
Establishing network connectivity
Since your product’s web application is integrated into the Console portal and uses Console’s web domain, you must set up network connectivity to Console’s AWS account. This allows requests to your webpages to be routed from the portal to your backend servers.
Traffic is routed as follows:
- A user accesses your application via Console’s domain.
- The request reaches Console’s Amazon EKS cluster.
- An NGINX pod within the cluster handles and routes the request.
- The NGINX pod then forwards traffic to your backend, based on your configuration.
For Console’s NGINX pod to reach your servers, you must ensure that network connectivity is established between Console’s EKS cluster and your backend infrastructure.
There are no fixed requirements on how to connect your application to Console’s AWS environment. Existing products use options such as:
- AWS VPC Endpoints (preferred)
- AWS VPC Lattice
Because implementation may vary across products, please contact the Console team to discuss your preferred setup and obtain assistance.
