Merge pull request #2462 from splunk/urbiz-OD6538-aws-managed-ts

[6538]: AWS-managed TS doc
splunk · Nov 20, 2024 · f7ebbe7 · f7ebbe7
2 parents e54ec59 + b2b7a92
commit f7ebbe7
Show file tree

Hide file tree

Showing 8 changed files with 124 additions and 7 deletions.
diff --git a/_images/gdi/aws-ts-awsmanaged1.png b/_images/gdi/aws-ts-awsmanaged1.png
diff --git a/_images/gdi/aws-ts-awsmanaged2.png b/_images/gdi/aws-ts-awsmanaged2.png
diff --git a/_images/gdi/aws-ts-awsmanaged3.png b/_images/gdi/aws-ts-awsmanaged3.png
diff --git a/_images/gdi/aws-ts-awsmanaged4.png b/_images/gdi/aws-ts-awsmanaged4.png
diff --git a/gdi/get-data-in/connect/aws/aws-troubleshooting.rst b/gdi/get-data-in/connect/aws/aws-troubleshooting.rst
@@ -7,7 +7,12 @@ Troubleshoot your AWS integration
 .. meta::
    :description: Resolve AWS policy, permission conflicts, and other issues in Splunk Observability Cloud.
 
-If you experience difficulties when connecting Splunk Observability Cloud to your Amazon Web Services (AWS) account or using the platform, read on to troubleshoot common issues. See :ref:`aws-ts-metric-streams` for issues specific to Metric Streams. 
+If you experience difficulties when connecting Splunk Observability Cloud to your Amazon Web Services (AWS) account or using the platform, read on to troubleshoot common issues. 
+
+See also the following docs:
+
+* :ref:`aws-ts-metric-streams` for issues specific to Splunk-managed Metric Streams. 
+* :ref:`aws-ts-ms-aws` for issues specific to AWS-managed Metric Streams.
 
 If issues persist, you can also contact :ref:`support`.  
 

diff --git a/gdi/get-data-in/connect/aws/aws-ts-metric-streams.rst b/gdi/get-data-in/connect/aws/aws-ts-metric-streams.rst
@@ -1,17 +1,15 @@
 .. _aws-ts-metric-streams:
 
 ******************************************************
-Troubleshoot AWS Metric Streams
+Troubleshoot Splunk-managed Metric Streams
 ******************************************************
 
 .. meta::
   :description: Troubleshoot AWS Metric Streams related issues.
 
 See the following topics when experiencing AWS Metric Streams related issues.
 
-.. note::
-
-  See also :ref:`aws-troubleshooting`.
+.. note:: See also :ref:`aws-troubleshooting` and :ref:`aws-ts-ms-aws`.
 
 I've enabled Splunk-managed Metric Streams in my AWS integration but I do not see any metrics streaming in
 ==========================================================================================================

diff --git a/gdi/get-data-in/connect/aws/aws-ts-ms-aws.rst b/gdi/get-data-in/connect/aws/aws-ts-ms-aws.rst
@@ -0,0 +1,113 @@
+.. _aws-ts-ms-aws:
+
+******************************************************
+Troubleshoot AWS-managed Metric Streams
+******************************************************
+
+.. meta::
+  :description: Troubleshoot AWS-managed Metric Streams related issues.
+
+See the following topics when experiencing AWS-managed Metric Streams related issues.
+
+.. note:: See also :ref:`aws-troubleshooting` and :ref:`aws-ts-metric-streams`.
+
+I've enabled AWS-managed Metric Streams in my AWS integration but I do not see any metrics streaming in
+==========================================================================================================
+
+Log in to your AWS console and review the following:
+
+Check the Metric Stream integration settings 
+----------------------------------------------------------------------
+
+In your CloudWatch console check the following:
+
+* The :strong:`Errors` chart must show zero errors.
+
+* The destination and output format must look similar to what is visible on the screenshot below. Note that your destination URL might use a different realm, for example https://ingest.us0.signalfx.com/v1/cloudwatch_metric_stream.
+
+.. image:: /_images/gdi/aws-ts-awsmanaged1.png
+    :width: 70%
+    :alt: Metric Stream settings
+
+Check the associated Firehose stream configuration
+----------------------------------------------------------------------
+
+Go to your AWS console and check your Firehose stream configuration:
+
+.. image:: /_images/gdi/aws-ts-awsmanaged2.png
+      :width: 70%
+      :alt: Firehose configuration
+
+Check the associated Firehose stream metrics 
+----------------------------------------------------------------------
+
+Make sure that:
+
+* :strong:`Incoming records` must have non-zero values. 
+
+  * Note that if there's a low volume of traffic going through the stream, the value of ``IncomingRecords (per second average)`` can be significantly lower than ``RecordsPerSecondLimit``, and therefore it might look like there are no incoming records. 
+
+* :strong:`HTTP endpoint delivery success` must be 100%. 
+
+.. image:: /_images/gdi/aws-ts-awsmanaged3.png
+      :width: 70%
+      :alt: Firehose stream metrics
+
+If there are any errors visible on the HTTP endpoint delivery success chart, update the Firehose stream destination settings to ensure that the HTTP endpoint is correct and use a new access token with INGEST scope.  
+
+  * Note that your destination URL might use a different realm, for example https://ingest.us0.signalfx.com/v1/cloudwatch_metric_stream.
+
+.. image:: /_images/gdi/aws-ts-awsmanaged4.png
+      :width: 70%
+      :alt: Destination settings
+
+Review roles and permissions 
+-----------------------------------
+
+Check the following:
+
+* Review the AWS role used by the Metric Streams. 
+
+* Make sure all required permissions are included, and that the CloudWatch metric stream region and the region listed in the AWS policy are the same.
+
+  * To find the AWS role used by the Metric Stream, go to the Stream overview page under the :strong:`Service Role to write to Amazon Data Firehose` label.
+
+This is a sample AWS policy:
+
+.. code-block:: none
+
+  {
+      "Version": "2012-10-17",
+      "Statement": [
+          {
+              "Effect": "Allow",
+              "Action": [
+                  "firehose:PutRecord",
+                  "firehose:PutRecordBatch"
+              ],
+              "Resource": [
+                  "arn:aws:firehose:eu-west-2:906383545488:deliverystream/PUT-HTP-7pH7O"
+              ]
+          }
+      ]
+  }
+
+These are the trust relationships:
+
+.. code-block:: none
+
+  {
+      "Version": "2012-10-17",
+      "Statement": [
+          {
+              "Effect": "Allow",
+              "Principal": {
+                  "Service": "streams.metrics.cloudwatch.amazonaws.com"
+              },
+              "Action": "sts:AssumeRole"
+          }
+      ]
+  }
+
+
+
diff --git a/gdi/get-data-in/connect/aws/get-awstoc.rst b/gdi/get-data-in/connect/aws/get-awstoc.rst
@@ -23,12 +23,13 @@ Connect AWS to Splunk Observability Cloud
   Send AWS logs to Splunk Platform <aws-logs>
   Next steps <aws-post-install>
   Troubleshoot your AWS integration <aws-troubleshooting>
-  Troubleshoot Metric Streams <aws-ts-metric-streams>
+  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
 
-You have several data ingestion and connection methods when it comes to monitoring your Amazon Web Services (AWS) data in Splunk Observability Cloud. 
+Splunk Observability Cloud offers you several data ingestion and connection methods to monitor your Amazon Web Services (AWS) data. 
 
 .. note:: If you want to send AWS data to the Splunk platform, use the Splunk add-on. Learn more at :new-page:`Splunk Add-on for AWS <https://docs.splunk.com/Documentation/AddOns/released/AWS/Description>`.