Doc week updates

gabydreckschmidt · gabydreckschmidt · commit 321bba1dfbd9 · 2020-06-18T17:50:16.000+02:00
diff --git a/Livy-api.md b/Livy-api.md
@@ -406,5 +406,6 @@ Content-Length: 17
 ```
 
 ## Learn more
+{: #learn-more-livy}
 
 - For interactive workloads see [Spark Interactive](/docs/AnalyticsEngine?topic=AnalyticsEngine-spark-interactive).
diff --git a/Retrieve-IAM-access-token.md b/Retrieve-IAM-access-token.md
@@ -62,7 +62,7 @@ Authorization: Bearer eyJraWQiOiIyMDE3MDgwOS0wMDowMDowMCIsImFsZyI6IlJTMjU2In0...
 Before you can create a token by using the {{site.data.keyword.Bluemix_notm}} CLI, check that you have met the following prerequisites:
 
 1. You have a valid IBMid.
-2. You have downloaded and installed the [{{site.data.keyword.Bluemix_notm}} CLI](https://{DomainName}/docs/cli?topic=cloud-cli-install-ibmcloud-cli).
+2. You have downloaded and installed the [{{site.data.keyword.Bluemix_notm}} CLI](/docs/cli?topic=cli-install-ibmcloud-cli).
 
 To create a token using {{site.data.keyword.Bluemix_notm}} CLI:
 
diff --git a/aggregating-logs.md b/aggregating-logs.md
@@ -57,8 +57,8 @@ The following prerequisites must be met before you can begin collecting cluster
 
 - You must have an existing {{site.data.keyword.iae_full_notm}} service instance. Presently, REST API is the only mode with which you can configure log aggregation.
 - You must create an IBM Log Analysis with LogDNA service instance. To create an instance in {{site.data.keyword.Bluemix_short}}, see [IBM Log Analysis with LogDNA
-](https://cloud.ibm.com/observe/logging){: external}. For details on monitoring and managing log data with IBM Log Analysis with LogDNA, see [provisioning a service instance](/docs/Log-Analysis-with-LogDNA?topic=LogDNA-provision){: external}.
-- You must have access to the LogDNA ingestion key. See [Getting the ingestion key](/docs/Log-Analysis-with-LogDNA?topic=LogDNA-ingestion_key){: external}.
+](https://cloud.ibm.com/observe/logging){: external}. For details on monitoring and managing log data with IBM Log Analysis with LogDNA, see [provisioning a service instance](/docs/Log-Analysis-with-LogDNA?topic=Log-Analysis-with-LogDNA-provision){: external}.
+- You must have access to the LogDNA ingestion key. See [Getting the ingestion key](/docs/Log-Analysis-with-LogDNA?topic=Log-Analysis-with-LogDNA-ingestion_key){: external}.
 - You must have the following IAM access permissions (roles) to the {{site.data.keyword.iae_full_notm}} service instance and the resource group. Two types of roles exist:
 
     -	**Platform management role**: here you must have viewer access or above to the resource group that contains {{site.data.keyword.iae_full_notm}}.
diff --git a/at-tracker.md b/at-tracker.md
@@ -21,7 +21,7 @@ subcollection: AnalyticsEngine
 
 As a security officer, auditor, or manager, you can use the **Activity Tracker** service to track how users and applications interact with {{site.data.keyword.iae_full_notm}} in {{site.data.keyword.cloud}}.
 
-{{site.data.keyword.at_full_notm}} records user-initiated activities that change the state of a service in {{site.data.keyword.cloud_notm}}. You can use this service to investigate abnormal activity and critical actions and to comply with regulatory audit requirements. In addition, you can be alerted about actions as they happen. The events that are collected comply with the Cloud Auditing Data Federation (CADF) standard. For more information, see the documentation about the [Activity Tracker with LogDNA](/docs/Activity-Tracker-with-LogDNA?topic=logdnaat-getting-started#getting-started){: new_window}.
+{{site.data.keyword.at_full_notm}} records user-initiated activities that change the state of a service in {{site.data.keyword.cloud_notm}}. You can use this service to investigate abnormal activity and critical actions and to comply with regulatory audit requirements. In addition, you can be alerted about actions as they happen. The events that are collected comply with the Cloud Auditing Data Federation (CADF) standard. For more information, see the documentation about the [Activity Tracker with LogDNA](/docs/Activity-Tracker-with-LogDNA?topic=Activity-Tracker-with-LogDNA-getting-started#getting-started){: new_window}.
 
 
 The following table lists the actions that generate an event:
@@ -58,4 +58,4 @@ Events are available in the following locations:
 * Germany
 * Japan
 
-{{site.data.keyword.at_full_notm}} can have only one instance per location. To view events, you must access the web UI of the {{site.data.keyword.at_full_notm}} service in the same location where your service instance is available. For more information, see [Launching the web UI through the IBM Cloud UI](/docs/Activity-Tracker-with-LogDNA?topic=logdnaat-launch#launch_step2).
+{{site.data.keyword.at_full_notm}} can have only one instance per location. To view events, you must access the web UI of the {{site.data.keyword.at_full_notm}} service in the same location where your service instance is available. For more information, see [Launching the web UI through the IBM Cloud UI](/docs/Activity-Tracker-with-LogDNA?topic=Activity-Tracker-with-LogDNA-launch#launch_step2).
diff --git a/best-practices.md b/best-practices.md
@@ -165,7 +165,7 @@ To facilitate monitoring and troubleshooting your applications and jobs, you can
 
 By configuring log aggregation, you can externalize the log files, which means that these files can be accessed even after the cluster was deleted.
 
-When you configure {{site.data.keyword.iae_full_notm}} to work with the LogDNA instance, we encourage you to select to connect to the private endpoints of the instance, to increase performance and save costs. See [Configuring private endpoints](/docs/Log-Analysis-with-LogDNA?topic=LogDNA-endpoints).
+When you configure {{site.data.keyword.iae_full_notm}} to work with the LogDNA instance, we encourage you to select to connect to the private endpoints of the instance, to increase performance and save costs. See [Configuring private endpoints](/docs/Log-Analysis-with-LogDNA?topic=Log-Analysis-with-LogDNA-endpoints).
 
 ## Switch regions for disaster recovery
 {: #disaster-recovery}
diff --git a/configure-COS-S3-object-storage.md b/configure-COS-S3-object-storage.md
@@ -28,7 +28,7 @@ To work with {{site.data.keyword.cos_short}} in an {{site.data.keyword.iae_full_
 
 1. Provision an {{site.data.keyword.cos_short}} service instance in {{site.data.keyword.Bluemix_short}}. See [Creating a new service instance](/docs/cloud-object-storage/iam?topic=cloud-object-storage-provision).
 
-  Create an {{site.data.keyword.Bluemix_short}} bucket in the  region of your choice and select the configuration, such as  resiliency (regional or cross-regional), and storage volume and price. See [Creating buckets to store your data](/docs/cloud-object-storage/iam?topic=cloud-object-storage-getting-started).
+  Create an {{site.data.keyword.Bluemix_short}} bucket in the  region of your choice and select the configuration, such as  resiliency (regional or cross-regional), and storage volume and price. See [Creating buckets to store your data](/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage).
 
   Make a note of the bucket name that you created. You will need it later when you configure {{site.data.keyword.iae_full_notm}} to work with {{site.data.keyword.cos_short}}.
 1. [Get the {{site.data.keyword.cos_short}} credentials](/docs/AnalyticsEngine?topic=AnalyticsEngine-get-cos-credentials).
diff --git a/customizing-using-script.md b/customizing-using-script.md
@@ -1,7 +1,7 @@
 ---
 
 copyright:
-  years: 2017, 2019
+  years: 2017, 2020
 lastupdated: "2019-07-31"
 
 subcollection: AnalyticsEngine
@@ -22,4 +22,4 @@ To enable an application to connect to {{site.data.keyword.cos_full_notm}}, you
 
 One way of doing this is to use a customization script to configure the properties that need to be updated in the core-site.xml file. It uses the Ambari configs.py file to make the required changes.
 
-This [customization sample script](https://github.com/IBM-Cloud/IBM-Analytics-Engine/blob/master/customization-examples/associate-cos.sh) configures the {{site.data.keyword.iae_full_notm}} cluster with HMAC authentication parameters. The example shows the complete source code of the customization script. You can modify the script for IAM authentication style parameters. The sample configuration script restarts the affected services that need to be restarted. These services are started immediately instead of sleeping for a long random interval after the Ambari API was triggered. 
+This [customization sample script](https://github.com/IBM-Cloud/IBM-Analytics-Engine/blob/master/customization-examples/associate-cos.sh) configures the {{site.data.keyword.iae_full_notm}} cluster with HMAC authentication parameters. The example shows the complete source code of the customization script. You can modify the script for IAM authentication style parameters. The sample configuration script restarts the affected services that need to be restarted. These services are started immediately instead of sleeping for a long random interval after the Ambari API was triggered.
diff --git a/data-skipping-config.md b/data-skipping-config.md
@@ -183,6 +183,7 @@ select * from table where shortType > cast(1 as short)
 ```
 
  ## Learn more
+ {: #learn-more-data-skipping}
 
  Click the following link for code samples that show you how to use the configuration options described in this topic:
 
diff --git a/data-skipping.md b/data-skipping.md
@@ -40,7 +40,7 @@ Note that the metadata is typically much smaller than the data. If changes are m
 
 ## Geospatial data skipping
 
- Data skipping is also supported for queries on geospatial datasets with latitude and longitude columns using [geospatial functions](https://www.ibm.com/support/knowledgecenter/en/SSCJDQ/com.ibm.swg.im.dashdb.analytics.doc/doc/geo_functions.html) from the [spatio-temporal library](/docs/AnalyticsEngine?topic=AnalyticsEngine-geospacial-lib).
+ Data skipping is also supported for queries on geospatial datasets with latitude and longitude columns using [geospatial functions](https://www.ibm.com/support/knowledgecenter/en/SSCJDQ/com.ibm.swg.im.dashdb.analytics.doc/doc/geo_functions.html) from the [spatio-temporal library](/docs/AnalyticsEngine?topic=AnalyticsEngine-geospatial-geotemporal-lib).
 
  In order to benefit from data skipping you can collect min/max indexes on the latitude and longitude columns.
 
@@ -55,4 +55,4 @@ Note that the metadata is typically much smaller than the data. If changes are m
  - ST_Within
  - ST_Overlaps
  - ST_EnvelopesIntersect
- - ST_IntersectsInterior
+ - ST_IntersectsInterior
diff --git a/geospacial-lib.md b/geospacial-lib.md
@@ -58,6 +58,7 @@ After you have registered `STContext` in your notebook, you can begin exploring
 - [Routing functions](/docs/AnalyticsEngine?topic=AnalyticsEngine-routing-functions)
 
 ## Learn more
+{: #learn-more-goespatio-lib}
 
 Check out the following Python notebooks to learn how to use the spacio-temporal library functions in Python notebooks. To access these notebooks, you need an {{site.data.keyword.DSX_full}} instance. See [Provisioning an {{site.data.keyword.DSX_full}} instance](https://cloud.ibm.com/catalog/services/watson-studio){: external}.
 
diff --git a/get-cos-credentials.md b/get-cos-credentials.md
@@ -75,7 +75,7 @@ To configure {{site.data.keyword.iae_full_notm}} to work with {{site.data.keywor
 
 ### Service endpoints
 
-As a user of {{site.data.keyword.cos_short}}, you not only need to know the API key or the HMAC keys to configure {{site.data.keyword.cos_short}}, but also the {{site.data.keyword.iae_full_notm}} service endpoints to connect to {{site.data.keyword.cos_short}}. See [Selecting regions and endpoints](/docs/infrastructure/cloud-object-storage-infrastructure?topic=cloud-object-storage-infrastructure-select-regions-and-endpoints) for help on which endpoints to use based on your {{site.data.keyword.cos_short}} bucket type, such as regional versus cross-regional.
+As a user of {{site.data.keyword.cos_short}}, you not only need to know the API key or the HMAC keys to configure {{site.data.keyword.cos_short}}, but also the {{site.data.keyword.iae_full_notm}} service endpoints to connect to {{site.data.keyword.cos_short}}. See [Selecting regions and endpoints](/docs/cloud-object-storage-infrastructure?topic=cloud-object-storage-infrastructure-select-regions-and-endpoints) for help on which endpoints to use based on your {{site.data.keyword.cos_short}} bucket type, such as regional versus cross-regional.
 
 You can also view the endpoints across regions for your {{site.data.keyword.cos_short}} service by selecting the service on your {{site.data.keyword.Bluemix_short}} dashboard and clicking **Endpoint** in the navigation pane. Always **choose the private endpoint**. Using the public endpoint is slower and more expensive. An example of an endpoint for US-South Cross region is:
 `s3.private.us.cloud-object-storage.appdomain.cloud`
diff --git a/key-management-by-kms.md b/key-management-by-kms.md
@@ -38,7 +38,7 @@ To create a Key protect instance and master keys:
   ```
   - `"encryption.kms.instance.url"`: The URL of your KeyProtect instance, for example,
   ```
-  sc.hadoopConfiguration.set("encryption.kms.instance.url" , "https://keyprotect.us-south.bluemix.net")
+  sc.hadoopConfiguration.set("encryption.kms.instance.url" , "https://<region>.kms.cloud.ibm.com")
   ```
   - `"encryption.key.access.token"`: A valid IAM token with access rights to the required keys in your KeyProtect instance, for example,
   ```
diff --git a/parquet-encryption-on-hive-tables.md b/parquet-encryption-on-hive-tables.md
@@ -60,6 +60,7 @@ To configure Parquet encryption on Hive tables:
   ```
 
 ## Usage examples
+{: #usage-examples-parquet-encryption-hive}
 
 The following examples show you how you can use Parquet encryption on data saved in Hive tables.
 
@@ -73,7 +74,7 @@ The following examples show you how you can use Parquet encryption on data saved
 
   # setup key protect on the hadoop configuration
   hc = spark.sparkContext._jsc.hadoopConfiguration()
-  hc.set("encryption.kms.instance.url", "https://keyprotect.us-south.bluemix.net")
+  hc.set("encryption.kms.instance.url", "https://<region>.kms.cloud.ibm.com")
   hc.set("encryption.kms.instance.id", KEY_PROTECT_INSTANCE_ID)
   hc.set("encryption.key.access.token", ACCESS_TOKEN)
 
diff --git a/parquet-encryption.md b/parquet-encryption.md
@@ -96,6 +96,7 @@ The following optional parameters can be used when writing encrypted data:
   ```
 
 ## Usage examples
+{: #usage-examples-parquet-encryption}
 
 The following sample code snippets for Python and Scala show how to create data frames, written to encrypted parquet files, and read from encrypted parquet files.
 
@@ -162,6 +163,7 @@ When reading a Parquet file, the identifier of the master encryption key (MEK) a
 The key encryption key is decrypted with the master encryption key, either locally if the master keys are managed by the application, or in a KeyProtect service if the master keys are managed by {{site.data.keyword.keymanagementservicefull}}. The key encryption keys are cached, so there is no need to interact with the KeyProtect service for each decrypted column or file if they use the same key encryption key. Then the data encryption key (DEK) is decrypted locally, using the key encryption key (KEK).
 
 ## Learn more
+{: #learn-more-parquet-encryption}
 
 Check out the following sample notebook to learn how to use Parquet Encryption:
 
diff --git a/provisioning.md b/provisioning.md
@@ -80,7 +80,7 @@ When provisioning a service instance:
 
 To create a service instance using the {{site.data.keyword.Bluemix_short}} command-line interface:
 
-1. Download and configure the {{site.data.keyword.Bluemix_short}} CLI. Follow the instructions [here](/docs/cli?topic=cloud-cli-getting-started).
+1. Download and configure the {{site.data.keyword.Bluemix_short}} CLI. Follow the instructions [here](/docs/cli?topic=cli-getting-started).
 
 1. Set the API endpoint for your region and log in:
    ```
diff --git a/release-notes.md b/release-notes.md
@@ -115,7 +115,7 @@ Use these notes to learn about the latest features, additions and changes to {{s
 
  Although existing clusters will still continue to work and be supported until September 30, 2019, you should stop using those now and start creating new `AE 1.2` clusters as described in [Best practices](/docs/AnalyticsEngine?topic=AnalyticsEngine-best-practices).
 
- All provisioned instances of AE 1.0 will be deleted after September 30, 2019. See the [deprecation notice](https://www.ibm.com/blogs/bluemix/2019/04/introducing-ibm-analytics-engine-v1-2-and-announcing-the-deprecation-of-ibm-analytics-engine-v1-0/){: external}.
+ All provisioned instances of AE 1.0 will be deleted after September 30, 2019.
 - A new software package `AE 1.2 Hive LLAP` was added to `AE 1.2`, which supports realtime interactive queries. Note however that currently you cannot resize a cluster created using this package.
 - `AE 1.2` supports Python 3.7. Although `AE 1.1` still supports both Python 3.5 and Python 2.7, you should start moving your Python-based applications or code to Python 3.7 now. Especially considering that the open source community has announced the end of support for Python 2.
 - `AE 1.2` does not support HDFS encryption zones. To store sensitive data with encryption requirements, select the appropriate COS encryption options. See details in [Best practices](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-best-practices#cos-encryption).
@@ -145,7 +145,7 @@ Use these notes to learn about the latest features, additions and changes to {{s
 
 ### 30 November 2018
 
-- You can now track life cycle management actions performed on the cluster by users and applications that have access to your service instance. See [Activity Tracker](/docs/AnalyticsEngine?topic=AnalyticsEngine-at-tracker).
+- You can now track life cycle management actions performed on the cluster by users and applications that have access to your service instance. See [Activity Tracker](/docs/AnalyticsEngine?topic=AnalyticsEngine-at_events).
 
 - To view the password of a cluster, a user must have either Writer or Manager IAM role on the {{site.data.keyword.iae_full_notm}} service instance.
 
diff --git a/troubleshooting.md b/troubleshooting.md
@@ -65,21 +65,21 @@ You should delete your service instance and create a new one by using the {{site
 {: troubleshoot}
 {: support}
 
-Tracing can be enabled by setting `BLUEMIX_TRACE` environment variable to `true` (case ignored). When trace is enabled,  additional debugging information is printed to the terminal.
+Tracing can be enabled by setting `IBMCLOUD_TRACE` environment variable to `true` (case ignored). When trace is enabled,  additional debugging information is printed to the terminal.
 
 On Linux/macOS terminal:
 
 ```
-$ export BLUEMIX_TRACE=true
+$ export IBMCLOUD_TRACE=true
 ```
 
 On Windows prompt:
 
 ```
-SET BLUEMIX_TRACE=true
+SET IBMCLOUD_TRACE=true
 ```
 
-To disable tracing, set the `BLUEMIX_TRACE` environment variable to `false` (case ignored).
+To disable tracing, set the `IBMCLOUD_TRACE` environment variable to `false` (case ignored).
 
 ## Command line interface: No cluster endpoint found
 {: #no-cluster-endpoint}
diff --git a/using-go-sdk.md b/using-go-sdk.md
@@ -131,6 +131,7 @@ The Go SDK allows you to construct the service client in one of two ways by:
       - Initializes the service client to use the service endpoint URL, also defined the corresponding environment variable
 
 ## Code samples using `iaesdk`
+{: #code-samples-go}
 
 The following code samples show how to:
 
diff --git a/using-java-sdk.md b/using-java-sdk.md
@@ -132,6 +132,7 @@ The Java SDK allows you to construct the service client in one of two ways by:
       - Initializes the service client to use the service endpoint URL, also defined the corresponding environment variable
 
 ## Code Samples
+{: #code-samples-java}
 
 The following code samples show how to:
 
diff --git a/using-node-js-sdk.md b/using-node-js-sdk.md
@@ -38,6 +38,7 @@ To run the Node.js SDK, you need Node 4.x+. You need to provide the service endp
 The service instance ID is also referred to as a instance GUID. You can retrieve the service instance ID when you create service credentials or through the CLI. See [Retrieving service endpoints](/docs/AnalyticsEngine?topic=AnalyticsEngine-retrieve-endpoints){: external}.
 
 ## Code samples using `iaesdk`
+{: #code-samples-node-js}
 
 Getting started with the Node.js SDK after you have installed it, involves sourcing credentials to the {{site.data.keyword.iae_full_notm}} service, invoking the service and then issuing different cluster commands as shown in the following sample code snippets.
 
diff --git a/using-python-sdk.md b/using-python-sdk.md
@@ -40,6 +40,7 @@ To use the `iaesdk` library, you need the following values:
 - `IAE_ENDPOINT_URL`: The service endpoint URL including the `https://` protocol. See [Service endpoints](https://cloud.ibm.com/apidocs/ibm-analytics-engine#service-endpoints){: external}.
 
 ## Code samples using `iaesdk`
+{: #code-samples-python-sdk}
 
 Getting started with the Python SDK after you have installed it, involves sourcing credentials to the {{site.data.keyword.iae_full_notm}} service, invoking the service and then issuing different cluster commands as shown in the following sample code snippets. The code examples are written for Python 3.7.
 
diff --git a/working-with-hive.md b/working-with-hive.md
