influxdata / influxdata/influxdb
Access to InfluxDB Cloud instance via custom URL and certificate
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Proposal:__
Allow access to our InfluxDB Cloud instance via CNAME and ability to upload Server Certificate.
__Current behavior:__
Only access is via AWS EC2 instance URL (somewhat cryptic).
__Desired behavior:__
Use a URL like https://influxdb.groov.com (CNAME in place now) to access my InfluxDB Cloud instance. Also, would like to upload our wildcard server certificate to ensure encrypted connection.
__Alternatives considered:__
None at this time.
__Use case:__
We are manufacturer and developer of industrial automation and IIoT products for manufacturing, OEM machine builders, building management, and SCADA applications (www.opto22.com). We'd like to demonstrate the capabilities of InfluxDB Cloud to our customers, so they can begin leveraging the power of your solution. There is significant demand for this solution, particularly for IIoT and digital transformation projects.
Contributor guide
Research direction
The issue names no repository files, tests, or entry points. First determine whether custom URLs and certificate uploads are implemented in this repository or managed in InfluxDB Cloud infrastructure. Done means a Cloud instance can use the requested CNAME and uploaded wildcard certificate for an encrypted connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100