Site-to-Site Connectivity with ngrok

Chapter 2. Site-to-Site Connectivity: APIs and Databases

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 3rd chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

Modern software solutions distribute workloads across regions and cloud providers and often offload tasks to third-party services, creating an additional challenge for SaaS vendors who must span these resources. Site-to-site connectivity with ngrok helps SaaS companies securely access these workloads and services—wherever they reside!

Why Connect to APIs and Databases?

Consider a company that performs compliance penetration testing across an organization’s cloud, devices, and network. The data and applications they need to scan reside in their customers’ environments, while the software and tools required to perform the scan reside in their local network.

SaaS companies that provide compliance testing use ngrok to gain access to their customers’ internal systems, such as Jira and GitHub, using APIs. Access to these internal systems allows compliance testing organizations to automate the entire testing workflow, including scanning GitHub ...