Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Timestream InfluxDB Within VPC

0

I have created a Timestream InfluxDB server using a VPC. I can connect to the server outside the VPC using the url provided. I created an endpoint within the VPC which provides access to timestream-influxdb. I can trace the endpoint within the VPC and it resolves to the correct local ip address. When I add the server prefix to the internal endpoint url it no longer resolves to an ip address. The endpoint is not created with a wildcard prefix. What is the correct mechanism for connecting to the InfluxDB server through the endpoint within the VPC?

The Endpoint is within an accessible security group and subnet.

Topics
DatabaseNetworking & Content Delivery
Tags
Amazon VPCAmazon Timestream
Language
English
asked 2 years ago921 views
2 Answers
0
Accepted Answer

Hi Josh,

I created an endpoint within the VPC which provides access to timestream-influxdb. I can trace the endpoint within the VPC and it resolves to the correct local ip address

I assume you are referring to PrivateLink endpoints here. Timestream for InfluxDB does not yet support PrivateLink endpoints for accessing InfluxDB endpoint. The private link support is only for the CRUD APIs (CreateDbInstance, GetDBInstance ...).

I recommend continuing to use the URL provided by GetDBInstance within your VPC. If you do not want to resolve to a publicIP address, please configure publiclyAccessible to false when creating the db instance.

AWS
answered 2 years ago
EXPERT
reviewed a year ago
  • Josh
    2 years ago

    Thank you for the reply. I would be interested to see where you found this in the documentation. I was on the lookout for wording implying this to be the case, but I never saw it.
    This is the configuration I am using until the endpoint is changed to include a wildcard prefix.

    Thank you.

0

Hello,

Follow this blog post to create VPC endpoints with Amazon Timestream https://aws.amazon.com/blogs/database/use-vpc-endpoints-with-amazon-timestream/

EXPERT
answered 2 years ago
  • Josh
    2 years ago

    Hello,

    I appreciate your reply, however, that blog post does not directly apply. I am trying to create a VPC endpoint to access a Timestream InfluxDB instance. That blog post applies to Timestream (not InfluxDB).

    The error I get when I follow the steps of the blog post is that the service name is not valid. The blog post uses com.amazonaws.<region>.timestream.ingest-cell1 which is not valid. (com.amazonaws.<region>.timestream.ingest-cell2 is valid. ) The service for Timestream InfluxDB is com.amazonaws.us-east-1.timestream-influxdb, which is valid, but it is also what I already have. Adding the server id to that service name causes the invalid service name error.

    The creation of the endpoint itself does not seem to be an issue, but using the endpoint to connect to an InfluxDB instance is not working.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content