- 新しい順
- 投票が多い順
- コメントが多い順
When using the AWS Timestream InfluxDB VPC Endpoint, the supported APIs are routed through the VPC and can access the Timestream resources within the VPC. However, other APIs that are not part of the InfluxDB-compatible API (such as GetBucketsApi and GetWriteApiAsync()) are not routed through the VPC Endpoint.
These additional APIs are part of the Timestream SDK and are used for managing Timestream resources, such as creating and managing databases, tables, and other administrative tasks. These APIs are not part of the InfluxDB-compatible API and are instead part of the AWS Timestream API.
To use these additional APIs, you need to ensure that your application or resources have the necessary permissions and network access to communicate with the AWS Timestream API directly, without going through the VPC Endpoint.
So for these additional APIs (such as GetBucketsApi and GetWriteApiAsync()) it is that they are communicating directly with InfluxDB, they are not leaving the VPC network (through public internet or VPC Endpoint). Endpoint is only used for Timestream Api calls (like: CreateDbInstance). For administrating Timestream only. If my understanding is right then thank you very much for your detailed explanation.