Merge pull request #2727 from splunk/urbiz-OD6926-aws-custom-services

[7143]: AWS Custom services

Author: aurbiztondo-splunk

_includes/gdi/available-aws.rst

@@ -1,6 +1,8 @@
 .. note:: For trace monitoring see :ref:`apm-gdi`.
 
-You can collect metrics and metadata from the following AWS services:
+You can collect metrics and metadata out-of-the-box from the AWS services listed on this page. 
+
+You can also collect data from any custom service you've created in AWS, or from any namespace defined by AWS that Splunk Observability Cloud doesn't support by default and is not on this list. You can select which custom services to monitor at the Splunk Observability Cloud UI or :new-page:`configure them using the API <https://dev.splunk.com/observability/docs/integrations/aws_integration_overview#Specify-AWS-namespaces>`.
 
 .. list-table::
   :header-rows: 1
@@ -494,7 +496,7 @@ The following applies:
 #. EC2 tags & properties only
 #. Collected by the Splunk Distribution of the Collector for Kubernetes
 
-The following applies to GovCloud regions:
+If you're in a GovCloud region the following applies:
 
 * Metric sync in GovCloud regions is limited to namespaces supported by AWS. Verify the specific namespaces available in your GovCloud region in the official AWS documentation :new-page:`Services in AWS GovCloud (US) Regions <https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/using-services.html>`.
 * AWS doesn't currently provide FIPS-complaint endpoints to retrieve tags. If you set up tags in your AWS GovCloud infrastructure do not include any sensitive information. In Splunk Observability Cloud AWS tags are identified by the prefix ``aws_tag``.

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

@@ -141,14 +141,22 @@ CloudWatch Metric Streams supports filtering by namespace and metric name but do
     <h2>Imported data<a name="aws-imported-data" class="headerlink" href="#aws-imported-data" title="Permalink to this headline">¶</a></h2>
   </embed>
 
-By default, Splunk Observability Cloud brings in data from all supported AWS services associated with your account. See :ref:`Supported integrations in Splunk Observability Cloud <aws-integrations>`.
+By default, Splunk Observability Cloud brings in data from all supported AWS services associated with your account. See :ref:`Supported integrations in Splunk Observability Cloud <aws-integrations>` for a complete list of the services supported by default. 
 
 To manage the amount of data to import, see :ref:`aws-infra-import`.  
 
 .. raw:: html
 
   <embed>
-    <h3>Recommended stats<a name="aws-metricstreams" class="headerlink" href="#aws-metricstreams" title="Permalink to this headline">¶</a></h3>
+    <h3>Custom services<a name="aws-custom-services" class="headerlink" href="#aws-custom-services" title="Permalink to this headline">¶</a></h3>
+  </embed>
+
+You can also collect data from any custom service you've created in AWS, or from any namespace defined by AWS that Splunk Observability Cloud doesn't support by default. You can select which custom services to monitor at the Splunk Observability Cloud UI or :new-page:`configure them using the API <https://dev.splunk.com/observability/docs/integrations/aws_integration_overview#Specify-AWS-namespaces>`.
+
+.. raw:: html
+
+  <embed>
+    <h3>Recommended stats<a name="aws-recstats" class="headerlink" href="#aws-recstats" title="Permalink to this headline">¶</a></h3>
   </embed>
 
 If you're polling data, by default Splunk Observability Cloud only imports certain stats, which are based on AWS' own recommended stats and vary with each service. See the :ref:`list of recommended stats <aws-recommended-stats>` used by Splunk Observability Cloud.