Merge pull request #2669 from splunk/tcarter-O11YDOCS-7075-GCPsupport

tcarter-O11YDOCS-7075-GCPsupport

Author: tcarter-splunk

conf.py

@@ -47,7 +47,7 @@
 release = ''
 language = 'en'
 
-exclude_patterns = ['_build', 'venv/lib/*/site-packages', '**/site-packages', 'Thumbs.db', '.DS_Store','z_cheat-sheets', 'README.md', 'CONTRIBUTING.md', '.github/pull_request_template.md', 'gdi/couchdb/couchdb.md', 'apm/find-root-cause.rst']
+exclude_patterns = ['_build', 'venv/lib/*/site-packages', '**/site-packages', 'Thumbs.db', '.DS_Store','z_cheat-sheets', 'README.md', 'CONTRIBUTING.md', '.github/pull_request_template.md', 'gdi/couchdb/couchdb.md', 'apm/find-root-cause.rst', '.git']
 
 # THEME CONFIGURATION
 #######################

gdi/get-data-in/connect/aws/aws-connect-polling.rst

@@ -54,7 +54,7 @@ In this step you need to choose the following connection options:
 
   * Metadata.
   * Cost and usage metrics.
-  * CloudWatch metrics. 
+  * CloudWatch metrics.
 
 In the CloudWatch Metrics option, select :guilabel:`Polling` as the ingestion method, and set up the polling rate at which you want Splunk Observability Cloud to poll CloudWatch for metric data.
 

gdi/get-data-in/connect/aws/get-awstoc.rst

@@ -8,27 +8,27 @@ Connect AWS to Splunk Observability Cloud
   :description: Connection planning information and links to the different ways to connect AWS to Splunk Observability Cloud.
 
 .. toctree::
-  :hidden:
-  :maxdepth: 5
-
-  AWS authentication, permissions and regions <aws-prereqs>
-  Supported Amazon services <https://docs.splunk.com/observability/en/gdi/integrations/cloud-aws.html#cloud-aws>
-  Compare connection options <aws-compare-connect>
-  Connect via polling <aws-connect-polling>
-  Connect with Splunk-managed Metrics Streams <aws-connect-ms>
-  Connect with AWS-managed Metric Streams <aws-console-ms>  
-  Connect to AWS using the Splunk API <aws-apiconfig>  
-  Connect to AWS with Terraform <aws-terraformconfig>
-  CloudFormation and Terraform templates <aws-cloudformation>
-  Send AWS logs to Splunk Platform <aws-logs>
-  Next steps <aws-post-install>
-  Troubleshoot your AWS integration <aws-troubleshooting>
-  Troubleshoot AWS CloudWatch polling <aws-ts-polling>
-  Troubleshoot Splunk-managed Metric Streams <aws-ts-metric-streams>
-  Troubleshoot AWS-managed Metric Streams <aws-ts-ms-aws>
-  aws-recommended-stats.rst
-  GetMetricStatistics API deprecation notice <aws-api-notice>
-  aws-tutorial/about-aws-tutorial.rst
+   :hidden:
+   :maxdepth: 5
+
+   AWS authentication, permissions and regions <aws-prereqs>
+   Supported Amazon services <https://docs.splunk.com/observability/en/gdi/integrations/cloud-aws.html#cloud-aws>
+   Compare connection options <aws-compare-connect>
+   Connect via polling <aws-connect-polling>
+   Connect with Splunk-managed Metrics Streams <aws-connect-ms>
+   Connect with AWS-managed Metric Streams <aws-console-ms>  
+   Connect to AWS using the Splunk API <aws-apiconfig>  
+   Connect to AWS with Terraform <aws-terraformconfig>
+   CloudFormation and Terraform templates <aws-cloudformation>
+   Send AWS logs to Splunk Platform <aws-logs>
+   Next steps <aws-post-install>
+   Troubleshoot your AWS integration <aws-troubleshooting>
+   Troubleshoot AWS CloudWatch polling <aws-ts-polling>
+   Troubleshoot Splunk-managed Metric Streams <aws-ts-metric-streams>
+   Troubleshoot AWS-managed Metric Streams <aws-ts-ms-aws>
+   aws-recommended-stats.rst
+   GetMetricStatistics API deprecation notice <aws-api-notice>
+   aws-tutorial/about-aws-tutorial.rst
 
 Splunk Observability Cloud offers you several data ingestion and connection methods to monitor your Amazon Web Services (AWS) data. 
 

splunkplatform/unified-id/unified-identity.rst

@@ -21,7 +21,7 @@ When you integrate your Splunk Cloud Platform and Splunk Observability Cloud ins
 Who can access Single Sign On (SSO) and the benefits of Unified Identity?
 ==========================================================================================
 
-All customers who have both Splunk Cloud Platform and Splunk Observability Cloud can access Unified Identity. Users must be on Splunk Cloud Platform version 9.x and higher. The AWS or GCP region for your Splunk Cloud Platform instance must map to your Splunk Observability Cloud instance realm as shown in the following table:
+All customers who have both Splunk Cloud Platform and Splunk Observability Cloud can access Unified Identity. Users must be on Splunk Cloud Platform version 9.x and higher. The AWS region for your Splunk Cloud Platform instance must map to your Splunk Observability Cloud instance realm as shown in the following table:
 
 .. list-table::
    :header-rows: 1