You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/includes/nginx-one/cloud-access.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,15 @@ files:
4
4
- content/nginx-one/getting-started.md
5
5
---
6
6
7
-
Confirm an F5 Distributed Cloud tenant has been provisioned for you. Log in to MyF5 and review your subscriptions. You should see within one of your subscriptions "Distributed Cloud". This could be in either an NGINX subscription or a Distributed Cloud. If the above does not appear in any of your subscriptions, reach out to either your F5 Account Team or Customer Success Manager.
7
+
Confirm that an F5 Distributed Cloud tenant has been provisioned for you.
8
8
9
-
With access, you or someone in your organization should have an email from [email protected] asking you to update your password when the tenant was created. The account name referenced in the E-Mail in bold is the tenant name.
9
+
1. Log in to [MyF5](https://my.f5.com/manage/s/) and review your subscriptions.
10
+
2. Look for **Distributed Cloud** in one of your subscriptions. This could appear under an NGINX subscription or a Distributed Cloud subscription.
10
11
11
-
Navigate to https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/ to access F5 Distributed Cloud. If you have never logged in, select the **Forgot Password?** option in the log in screen. Alternatively, if someone within your organization has access, ask them to add you as a user within your tenant with a role providing permissions for NGINX One.
12
+
If you don’t see **Distributed Cloud** in any subscription, contact your F5 account team or Customer Success Manager.
13
+
14
+
When your tenant is created, you or someone in your organization should receive an email from **[email protected]** asking you to set your password. The account name in bold in the email is your tenant name.
15
+
16
+
Go to `https://<TENANT_NAME>.console.ves.volterra.io/` to access F5 Distributed Cloud.
17
+
If you have never signed in, select **Forgot Password?** on the sign-in page.
18
+
Alternatively, ask someone in your organization with access to add you as a user in your tenant with a role that includes permissions for NGINX One Console.
Copy file name to clipboardExpand all lines: content/nginx-one/workshops/lab1/getting-started-with-nginx-one.md
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,8 @@ You need:
41
41
- NGINX One service enabled
42
42
- Basic Linux and NGINX knowledge
43
43
44
+
{{< include "/nginx-one/cloud-access.md" >}}
45
+
44
46
---
45
47
46
48
## How NGINX One Console works
@@ -59,22 +61,16 @@ When you register a new instance, NGINX One Console gives you a `curl` command t
59
61
60
62
A data plane key is required to connect an instance to NGINX One Console. Once connected, you can monitor and manage the instance from the NGINX One Console dashboard.
61
63
62
-
For more about NGINX Agent, see the [NGINX Agent overview]({{< ref "/agent/overview/about.md" >}}).
64
+
For more about NGINX Agent, see the [NGINX Agent overview]({{< ref "/nginx-one/agent/overview/about.md" >}}).
63
65
64
66
---
65
67
66
68
## Open NGINX One Console
67
69
68
-
1. Go to [https://console.ves.volterra.io/login/start](https://console.ves.volterra.io/login/start).
69
-
2. Sign in with your F5 Distributed Cloud account.
70
-
3. On the home page, find the **NGINX One** tile.
71
-
4. Select the tile to open NGINX One Console.
72
-
5. Confirm the service status is **Enabled**.
73
-
6. Select **Visit Service** to open the **Overview** dashboard in NGINX One Console.
70
+
{{< include "/nginx-one/cloud-access-nginx.md" >}}
74
71
75
-
If NGINX One Console isn’t enabled, ask your F5 Distributed Cloud administrator for access.
76
72
77
-
When no NGINX instances are connected, the NGINX One Console dashboard stays empty. After you add instances, the dashboard shows metrics like availability, version, and usage trends.
73
+
Until you add NGINX instances are connected, the NGINX One Console dashboard remains empty. After you add instances, the dashboard shows metrics like availability, version, and usage trends.
78
74
79
75
---
80
76
@@ -122,4 +118,4 @@ Go to [Lab 2: Run workshop components with Docker]({{< ref "nginx-one/workshops/
122
118
## References
123
119
124
120
-[Create and manage data plane keys]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md" >}})
0 commit comments