docs: Publish NGINXaaS for GC pre-release docs (#1285)

Publish NGINXaaS for GC pre-release docs

Author: JTorreG

content/_index.md

@@ -43,7 +43,7 @@ Learn how to deliver, manage, and protect your applications using F5 NGINX produ
 {{</card-section>}}
 
 {{<card-section showAsCards="true" title="F5 NGINX as a Service">}}
-  {{<card title="F5 NGINXaaS for Azure" titleUrl="/nginxaas/azure/" brandIcon="NGINX-for-Azure-product-icon.svg" isLanding="true">}}
+  {{<card title="F5 NGINXaaS for Azure" titleUrl="/nginxaas/azure/" brandIcon="F5-NGINXaaS-icon.svg" isLanding="true">}}
     Infrastructure-as-a-Service (IaaS) version of NGINX Plus for your Microsoft Azure application stack.
   {{</card >}}
 {{</card-section>}}

content/includes/nginxaas-google/access-console.md

@@ -0,0 +1,6 @@
+---
+nd-docs: DOCS-000
+---
+
+- Visit [https://console.nginxaas.net/](https://console.nginxaas.net/) to access the NGINXaaS Console.
+- Log in to the console with your Google credentials.

content/includes/nginxaas-google/create-or-import-nginx-config.md

@@ -0,0 +1,24 @@
+---
+nd-docs: DOCS-000
+---
+
+In the NGINXaaS Console,
+
+1. On the left menu, select **Configurations**.
+1. Select **Add Configuration** to add a new NGINX configuration.
+1. You can either create a new configuration from scratch or copy an existing configuration:
+
+   - Select **New configuration** to create a new config.
+      - Provide a name for your configuration and an optional description.
+      - Change the configuration path if needed.
+      - Select to start with the "NGINXaaS Default" (a basic NGINX setup) or an empty configuration file.
+      - Select **Next**.
+   - Select **Copy existing configuration** to use one of the existing configuration files in your account as template.
+      - Provide a name for your configuration and an optional description.
+      - Change the configuration path if needed.
+      - Use the **Choose configuration to copy** list to select the configuration file you want to copy.
+      - Use the **Choose configuration version to copy** list to select the version of the configuration file you want to copy.
+      - Select **Next**.
+
+1. Modify the configuration file as needed and select **Save**.
+   - You can import certificates using the **Add file** option.

content/includes/nginxaas-google/logging-config-access-logs.md

@@ -0,0 +1,39 @@
+---
+nd-docs: DOCS-000
+---
+
+NGINX access logs are disabled by default. You can enable access logs by adding **access_log** directives to your NGINX configuration to specify the location of the logs and formats. The log path should always be configured to be inside **/var/log/nginx**.
+
+```nginx
+http {
+	log_format myfmt '$remote_addr - $remote_user [$time_local] '
+						   '"$request" $status $body_bytes_sent '
+						   '"$http_referer" "$http_user_agent" "$gzip_ratio"';
+
+	access_log /var/log/nginx/nginx-access.log myfmt;
+	# ...
+}
+```
+
+{{< call-out "note" >}} The **$time_local** variable includes the date and time for each log. It helps with ordering logs after export. {{< /call-out >}}
+
+To explicitly disable access logs, apply the following config:
+
+```nginx
+http {
+	access_log off;
+}
+```
+
+or
+
+```nginx
+http {
+	access_log /dev/null;
+}
+```
+
+To learn more about how to specify `access_log` in different configuration levels and their effect, see [access_log](https://nginx.org/en/docs/http/ngx_http_log_module.html#access_log)
+
+{{< call-out "warning" >}}Keep NGINX logs in the **/var/log/nginx** directory. Otherwise, you may lose data from your logs.
+{{< /call-out >}}

content/includes/nginxaas-google/logging-config-error-logs.md

@@ -0,0 +1,19 @@
+---
+nd-docs: DOCS-000
+---
+
+NGINX error logs are disabled by default. You can enable error logs by adding **error_log** directives to your NGINX configuration to specify the location of the logs and formats. The log path should always be configured to be inside **/var/log/nginx**.
+
+While you should configure log files in the **/var/log/nginx** directory, you can change the filename and severity level. For example, the following line in the NGINX configuration sends errors to the `nginx-error.log` file, and limits messages to a severity level of **emerg**:
+
+```nginx
+error_log /var/log/nginx/nginx-error.log emerg;
+```
+
+Alternatively, you can disable error logs completely with the following line:
+
+```nginx
+error_log /dev/null;
+```
+
+To learn more about how to specify `error_log` in different configuration levels, see the documentation of the [error_log](https://nginx.org/en/docs/ngx_core_module.html?#error_log) directive.

content/includes/nginxaas-google/ncu-description.md

@@ -0,0 +1,11 @@
+---
+nd-docs: "DOCS-1476"
+---
+
+An NGINX Capacity Unit (NCU) quantifies the capacity of an NGINX instance based on the underlying compute resources. This abstraction allows you to specify the desired capacity in NCUs without having to consider the regional hardware differences.
+
+An NGINX Capacity Unit consists of the following parameters:
+
+* CPU: an NCU provides 20 [Azure Compute Units](https://learn.microsoft.com/en-us/azure/virtual-machines/acu) (ACUs)
+* Bandwidth: an NCU provides 60 Mbps of network throughput
+* Concurrent connections: an NCU provides 400 concurrent connections. This performance is not guaranteed when NGINX App Protect WAF is used with NGINXaaS

content/includes/nginxaas-google/ssl-tls-prerequisites.md

@@ -0,0 +1,5 @@
+---
+nd-docs: DOCS-000
+---
+
+TBD SSL Prerequisites for NGINXaaS for Google Cloud

content/includes/nginxaas-google/terraform-prerequisites.md

@@ -0,0 +1,6 @@
+---
+nd-docs: DOCS-000
+---
+
+- Confirm that you meet the [NGINXaaS Prerequisites]({{< ref "/nginxaas-google/getting-started/prerequisites.md" >}}).
+

content/includes/nginxaas-google/terraform-resources.md

@@ -0,0 +1,5 @@
+---
+nd-docs: DOCS-000
+---
+
+TBD NGINXaaS for Google Cloud Terraform resources

content/includes/nginxaas-google/update-nginx-config.md

@@ -0,0 +1,14 @@
+---
+nd-docs: DOCS-000
+---
+
+1. On the left menu, select **Configurations**.
+1. On the list of configurations, select the ellipses (three dots) icon next to the configuration you want to update.
+1. Select **Edit**.
+1. Update the "Description" field as needed and select **Next**.
+1. Select the file you want to update in the file tree.
+   - Certificates can only be copied, moved, or renamed.
+1. Modify the configuration file(s) as needed and select **Next**.
+1. Review the changes using the "Inline" or "Side-by-side"  views and select **Save**.
+
+You will see a notification confirming that the configuration was updated successfully.