Tetra Agent Allow List Endpoints
Tetra Agents must have access to at least one of the following endpoints:
- Your Tetra Data Platform (TDP) API (for example,
platform.tetrascience.com
) - A Tetra Hub with Agent access configured on forward and reverse proxy ports
- A Tetra Data Hub with Agent access configured on a Generic Data Connector (GDC) and Tetra L7 Proxy Connector
If you select the recommended Enable S3 Direct Upload or Receive Commands options during Agent deployment, then the Agent must have access to the following endpoints, either directly or through a proxy:
NOTE
If you're using a Tetra Hub to proxy the Agent's connections, only the Hub must have access to the following endpoints. The Agent only needs access to the Hub.
AWS Endpoint | Description | When Required |
---|---|---|
https://[infrastructure name]-[environment]-datalake.s3.[region].amazonaws.com https://[infrastructure name]-[environment]-backup.s3.[region].amazonaws.com https://[infrastructure name]-[environment]-events.s3.[region].amazonaws.com Note: If you have a customer hosted deployment, you can find these Amazon Simple Storage Service (Amazon S3) bucket names in the Amazon S3 console. If you have a Tetra hosted deployment, you will get these URLs from TetraScience. | Uploads files | When the Enable S3 Direct Upload option is selected |
https://sqs.[region].amazonaws.com | Fetches the command message and then returns the command processing status | When the Receive Commands option is selected |
https://logs.[region].amazonaws.com | Posts agent heart beats and logs | When the Enable S3 Direct Upload option is selected |
https://monitoring.[region].amazonaws.com | Sends Metrics Data (such as CPU, memory, and disk usage) | When the Enable S3 Direct Upload option is selected |
Updated 5 months ago