Your connector must have the ability to egress its network and reach the Border0 API and proxies through the Internet.
Depending on your preferred installation method, you will be required to create a connector token for the connector to authenticate. Failure to provide this token when required will result in the connector being unable to authenticate itself against your Border0 Organization and it will not come online. Any sockets associated only with this connector will not be available to your Border0 users.
Your connector must be able to reach the target services (at the hostname and port configured in the upstream configuration) through the network, with the exception of AWS SSM targets. For example, if you have a connector running in a private network with no way of connecting to a target service in a different private network, this connector will not be able to establish a connection to the upstream service.
Depending on the upstream configuration of your connector's sockets you may need additional credentials or configuration to authenticate against third-party services. Specifically, if any of the sockets are connected-to using the AWS EC2 Instance Connect or AWS SSM options, you will need to ensure your connector's runtime has access to the appropriate AWS credentials that allow connecting with those methods.
- For help with AWS credentials for connecting to AWS EC2 Instance Connect targets, click here.
- For help with AWS credentials for connecting to AWS SSM targets, click here.
- For help with AWS credentials for using the EC2 Discovery Plugin, click here. // TODO
- For help with AWS credentials for using the ECS Discovery Plugin, click here. // TODO
- For help with AWS credentials for using the RDS Discovery Plugin, click here. // TODO
- For help with AWS credentials for fetching variables from AWS SSM Parameter Store, click here. // TODO
- For help with AWS credentials for fetching variables from AWS Secrets Manager, click here. // TODO
Updated 14 days ago