There are several ways to implement this Endpoint, as described in this article.
1. Bumblebee Node on-prem
If your application runs on servers or containers in the on-prem data center and this application needs to connect to another private application (for example, make API calls) that is published on Bumblebee platform as App Service, you deploy Endpoint on your side to build the network connectivity.
You can deploy a Bumblebee Node as a virtual or hardware appliance in your data center, as seen in the diagram below.
Follow this article for configuration steps.
2. Native Cloud Endpoint
Use this option for the following situations:
Your application that needs to connect to another application resides in the cloud environment such as AWS VPC and Azure VNet
Your application resides in the data center but you cannot deploy Bumblebee Node on-prem. However, your data center has a Direct Connect or VPN to a cloud provider (AWS or Azure) and your on-prem application has reachability to the cloud environment,
In the above scenarios, you use native cloud provider endpoint, as shown below. In this case, the AWS or Azure private endpoint connects to Bumblebee and then to the application no matter where it is.
The diagram below illustrates using your own AWS VPC reachable from on-prem and creating a native endpoint to access applications. The configuration steps is described in this article for AWS endpoint.
3. Hosted Bumblebee Node
If your application is on-prem and it does not have reachability to your own cloud environment or you do not have cloud environment, you can let Bumblebee platform host your Bumblebee Node, as shown below.
Comments