Revert "Revert "GCP Beta""

pull/685/head
Scott Anderson 2019-12-30 13:04:39 -07:00 committed by GitHub
parent 949c3ee7ef
commit da215c9ed4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 95 additions and 41 deletions

View File

@ -3,7 +3,7 @@ title: Manage your InfluxDB Cloud 2.0 Account
description: >
View and manage information related to your InfluxDB Cloud 2.0 account such as
pricing plans, data usage, account cancelation, etc.
weight: 3
weight: 4
menu:
v2_0_cloud:
name: Account management

View File

@ -35,10 +35,13 @@ Limits are designed to let you monitor 5-10 sensors, stacks or servers comfortab
2. InfluxDB Cloud requires email verification to complete the sign up process.
Verify your email address by opening the email sent to the address you provided and clicking **Verify Your Email**.
3. (If you subscribed through InfluxData) Choose your cloud provider.
4. Select a region for your {{< cloud-name >}} instance. The following regions are available:
4. Select a provider and region for your {{< cloud-name >}} instance. The following are available:
- **US West (Oregon)**
- **EU Frankfurt**
- **Amazon Web Services (AWS)**
- **US West (Oregon)**
- **EU Frankfurt**
- **Google Cloud Platform (GCP)**
- **Iowa**
_To suggest regions to add, click **Let us know** under Regions._
5. (If you subscribed through InfluxData) Review the terms of the agreement, and then select **I have viewed and agree to InfluxDB Cloud 2.0 Services Subscription Agreement and InfluxData Global Data Processing Agreement**.
@ -81,22 +84,12 @@ For information about using the InfluxDB v2 API, `influx` CLI, and client librar
see [Write data to InfluxDB](/v2.0/write-data/).
{{% note %}}
#### InfluxDB Cloud instance endpoint
When using Telegraf, the InfluxDB v2 API, the `influx` CLI, or the client libraries to interact with your {{< cloud-name "short" >}}
instance, extract the "host" or "endpoint" of your instance from your {{< cloud-name "short" >}} UI URL.
For example:
```bash
# for US West (Oregon)
https://us-west-2-1.aws.cloud2.influxdata.com
# for EU Frankfurt
https://eu-central-1-1.aws.cloud2.influxdata.com
```
When using Telegraf, the InfluxDB v2 API, the `influx` CLI, or the client libraries
to interact with your {{< cloud-name "short" >}}, they each require the URL of your
InfluxDB Cloud instance.
See [InfluxDB Cloud URLs](/v2.0/cloud/urls/) for information about which URL to use
and where to find it in your InfluxDB Cloud UI.
{{% /note %}}
## Query and visualize data

View File

@ -0,0 +1,41 @@
---
title: InfluxDB Cloud 2.0 URLs
description: >
InfluxDB Cloud 2.0 is available on multiple cloud providers in multiple regions,
each with with a unique URL and API endpoint.
weight: 3
menu:
v2_0_cloud:
name: InfluxDB Cloud URLs
---
InfluxDB Cloud 2.0 is available on multiple cloud providers in multiple regions.
Each region has a unique InfluxDB Cloud URL and API endpoint.
Use the URLs below to interact with your InfluxDB Cloud instances with the
[InfluxDB API](/v2.0/reference/api/), [InfluxDB client libraries](/v2.0/reference/api/client-libraries/),
[`influx` CLI](/v2.0/reference/cli/influx/), or [Telegraf](/v2.0/write-data/use-telegraf/).
## Amazon Web Services (AWS)
| Region | URL |
|:------ |:--- |
| US West (Oregon) | https://us-west-2-1.aws.cloud2.influxdata.com |
| EU Frankfurt | https://eu-central-1-1.aws.cloud2.influxdata.com |
## Google Cloud Platform (GCP)
| Region | URL |
|:------ |:--- |
| Iowa | https://prod01-us-central-1.gcp.cloud2.influxdata.com |
---
### View your Cloud URL in the InfluxDB Cloud UI
For the URL of your specific InfluxDB Cloud instance:
1. Click the **Load Data** icon in the left navigation of your InfluxDB Cloud user interface (UI).
{{< nav-icon "load-data" >}}
2. Go to **Client Libraries**.
3. The URL of your InfluxDB instance is displayed near the top of the page.

View File

@ -169,13 +169,34 @@ Include the following in your request:
##### Example API write request
Below is an example API write request using `curl`:
Below is an example API write request using `curl`.
The URL depends on the version and location of your InfluxDB 2.0 instance.
{{< tabs-wrapper >}}
{{% tabs %}}
[InfluxDB OSS](#)
[{{< cloud-name "short">}}](#)
{{% /tabs %}}
{{% tab-content %}}
```sh
curl -XPOST "http://localhost:9999/api/v2/write?org=YOUR_ORG&bucket=YOUR_BUCKET&precision=s" \
--header "Authorization: Token YOURAUTHTOKEN" \
--data-raw "mem,host=host1 used_percent=23.43234543 1556896326"
```
{{% /tab-content %}}
{{% tab-content %}}
{{% cloud-msg %}}
For the specific URL of your {{< cloud-name "short" >}} instance, see [InfluxDB Cloud URLs](/v2.0/cloud/urls/).
{{% /cloud-msg %}}
```sh
curl -XPOST "YOUR-INFLUXDB-CLOUD-URL/api/v2/write?org=YOUR_ORG&bucket=YOUR_BUCKET&precision=s" \
--header "Authorization: Token YOURAUTHTOKEN" \
--data-raw "mem,host=host1 used_percent=23.43234543 1556896326"
```
{{% /tab-content %}}
{{< /tabs-wrapper >}}
### Others

View File

@ -39,16 +39,10 @@ Specify the following:
##### urls
An array of URLs for your InfluxDB v2.0 instances.
_By default, InfluxDB runs on port `9999`._
{{% cloud-msg %}}
###### {{< cloud-name "short" >}} URL
To write data to an {{< cloud-name "short" >}} instance, use the URL of your
{{< cloud-name "short" >}} user interface (UI).
{{< cloud-name >}} requires HTTPS.
For example: <code>https:<nolink>//us-west-2-1.aws.cloud2.influxdata.com</code>
{{% /cloud-msg %}}
By default, InfluxDB 2.0 OSS runs on port `9999`.
If using **{{< cloud-name >}}**, see [InfluxDB Cloud URLs](/v2.0/cloud/urls/) for information
about which URLs to use.
**{{< cloud-name "short">}} requires HTTPS**.
##### token
Your InfluxDB v2.0 authorization token.
@ -80,13 +74,13 @@ export INFLUX_TOKEN=YourAuthenticationToken
{{% code-tab-content %}}
```sh
$env:INFLUX_TOKEN = YourAuthenticationToken"
$env:INFLUX_TOKEN = "YourAuthenticationToken"
```
{{% /code-tab-content %}}
{{% code-tab-content %}}
```sh
set INFLUX_TOKEN=YourAuthenticationToken
set INFLUX_TOKEN=YourAuthenticationToken
# Make sure to include a space character at the end of this command.
```
{{% /code-tab-content %}}
@ -107,12 +101,12 @@ The name of the bucket to write data to.
#### Example influxdb_v2 configuration
The example below illustrates `influxdb_v2` configurations that write to InfluxDB OSS or {{< cloud-name >}}.
{{< code-tabs-wrapper >}}
{{% code-tabs %}}
{{< tabs-wrapper >}}
{{% tabs %}}
[InfluxDB OSS](#)
[{{< cloud-name "short" >}}](#)
{{% /code-tabs %}}
{{% code-tab-content %}}
{{% /tabs %}}
{{% tab-content %}}
```toml
# ...
@ -124,13 +118,18 @@ The example below illustrates `influxdb_v2` configurations that write to InfluxD
# ...
```
{{% /code-tab-content %}}
{{% code-tab-content %}}
{{% /tab-content %}}
{{% tab-content %}}
{{% cloud-msg %}}
For the specific URL of your {{< cloud-name "short" >}} instance, see [InfluxDB Cloud URLs](/v2.0/cloud/urls/).
{{% /cloud-msg %}}
```toml
# ...
[[outputs.influxdb_v2]]
urls = ["https://us-west-2-1.aws.cloud2.influxdata.com"]
urls = ["https://example.cloud2.influxdata.com"]
token = "$INFLUX_TOKEN"
organization = "example-org"
bucket = "example-bucket"
@ -138,8 +137,8 @@ The example below illustrates `influxdb_v2` configurations that write to InfluxD
# ...
```
{{% /code-tab-content %}}
{{< /code-tabs-wrapper >}}
{{% /tab-content %}}
{{< /tabs-wrapper >}}
{{% note %}}