You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build capability to make calls to proxy functions instead of terrahub api endpoints
Expected Behavior
In private networks (to be read: VPC), there is no external connectivity to TerraHub API. So, instead of forcing customers to open those connectivities, let's build out the capability to make calls to proxy functions (AWS Lambda, Google Functions, Azure Functions) that are deployed in the same VPC and can communicate using cross account role with TerraHub API.
The text was updated successfully, but these errors were encountered:
avozicov
changed the title
build capability to make calls to proxy functions instead of terrahub api endpoints
Build capability to make calls to proxy functions instead of terrahub api endpoints
Mar 2, 2019
Describe the Feature
Build capability to make calls to proxy functions instead of terrahub api endpoints
Expected Behavior
In private networks (to be read: VPC), there is no external connectivity to TerraHub API. So, instead of forcing customers to open those connectivities, let's build out the capability to make calls to proxy functions (AWS Lambda, Google Functions, Azure Functions) that are deployed in the same VPC and can communicate using cross account role with TerraHub API.
The text was updated successfully, but these errors were encountered: