You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: gdi/get-data-in/connect/aws/aws-prereqs.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -412,7 +412,7 @@ Read more at the official AWS documentation:
412
412
413
413
* :new-page:`AWS Organization Service Control Policies <https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html>`
414
414
* :new-page:`Permissions boundaries for IAM entities <https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html>`
415
-
* :new-page:`Troubleshooting IAM permission access denied or unauthorized errors <https://web.archive.org/web/20231129090004/https://repost.aws/knowledge-center/troubleshoot-iam-permission-errors>`
415
+
* :new-page:`Troubleshooting IAM permission access denied or unauthorized errors <https://repost.aws/knowledge-center/troubleshoot-iam-permission-errors>`
Copy file name to clipboardExpand all lines: gdi/get-data-in/connect/aws/aws-troubleshooting.rst
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,22 +18,22 @@ If issues persist, you can also contact :ref:`support`.
18
18
Error validating your AWS connection
19
19
=========================================
20
20
21
-
The automatic attempt to validate a connection that you just configured fails, so there is no connection between Splunk Observability Cloud and your AWS account.
21
+
The automatic attempt to validate a connection that you just configured fails, so there is no connection between Splunk Observability Cloud and your AWS account. This can include failed API calls with ``400`` error codes.
22
22
23
23
Cause
24
24
^^^^^^
25
25
26
-
The connection might fail due to invalid Identity Access Management (IAM) policy used by your AWS integration.
26
+
The connection might fail due to your AWS integration using invalid Identity Access Management (IAM) policies, or missing some of the required permissions.
27
27
28
-
If you use the AWS Organizations' :new-page:`Service control policies <https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html>` or :new-page:`Permission boundaries for IAM entities <https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html>`, they
28
+
If you use AWS Organizations' :new-page:`Service control policies <https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html>` or :new-page:`Permission boundaries for IAM entities <https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html>`, they
29
29
might impact the AWS IAM policy you're using to connect to Splunk Observability Cloud.
30
30
31
31
Solution
32
32
^^^^^^^^^
33
33
34
-
Ensure all :ref:`aws-required-permissions` are included in your IAM policy.
34
+
Make sure to include all the required policies to connect your AWS account to Splunk Observability Cloud, as described in :ref:`aws-required-permissions`. Note that required permissions depend on your connection method (polling or Metric Streams), and that tag collection requires specific permissions.
35
35
36
-
Also review the AWS Organizations' policies and boundaries you're using.
36
+
You also need to review the AWS Organizations' policies and boundaries you're using.
When you set up a test in Splunk Synthetic Monitoring, you can configure the viewport and network connection of the device from which the test is simulated.
31
29
32
30
Because Browser tests capture the visual experience of a page, while Uptime and API tests only capture response data, viewport applies to Browser tests only. Network connection applies to all test types.
Browser tests in Splunk Synthetic Monitoring capture the visual experience of a user interacting with your application. The viewport is the framed area on a device's screen for viewing information, such as the browser window on a desktop. By default, Browser tests run from a desktop-sized viewport. You can configure tests to run from other viewport sizes to test the user experience from a variety of window sizes and device types.
42
36
43
37
When you set up a test, you can choose the viewport size from a list of common devices, or set a custom viewport by height and width.
You can run Browser, Uptime, or API tests to simulate network connections of various latencies, including Mobile LTE, Mobile 3G, DSL, Mobile 5G, and cable internet. Testing your site from a variety of connection types lets you monitor the experience of users in a variety of settings.
Specify locations for your tests to simulate traffic from a range of checkpoints around the world, or use private locations to test sites from within a private network.
82
64
83
65
For more, see:
@@ -88,12 +70,9 @@ For more, see:
88
70
.. * See :ref:`private-locations` to set up private locations.
You can use the play and pause buttons in the more menu (|more|) of your tests to pause or resume data collection.
98
77
99
78
The current status of a test is updated every time you load the :guilabel:`Test Overview` page in Splunk Synthetic Monitoring. The following table describes the possible status types for each test.
@@ -117,14 +96,9 @@ The current status of a test is updated every time you load the :guilabel:`Test
Choosing informative names for your tests and alerts helps organize content. Here are some guidelines:
129
103
130
104
* Add a category as a prefix to your test name like group, application, brand, or team names so that you can simplify searches. For example, these two Browser tests start with ``[ButtercupGames]``.
@@ -136,13 +110,9 @@ Choosing informative names for your tests and alerts helps organize content. Her
136
110
:alt:This image shows two Browser tests with the prefix [ButtercupGames].
Follow these guidelines to troubleshoot a broken test.
147
117
148
118
#. (Optional) Make a copy of the test so that you can check various solutions before fixing the original test.
@@ -159,12 +129,9 @@ Follow these guidelines to troubleshoot a broken test.
159
129
#. Verify that there is one instance only of the selector you want to use in your test. If the selector appears more than once your test might break again in the future. Unique selectors provide optimal test performance.
0 commit comments