Connect to AWS using the guided setup in Splunk Observability Cloud 🔗
If you have administrator privileges for Splunk Observability Cloud and your Amazon Web Services (AWS) account, you can use guided setup to do the following:
Connect AWS to Observability Cloud.
Configure metrics and logs collection.
If you want to activate Metric Streams, read the specific instructions.
For other ways to connect Observability Cloud to AWS, see Connect to AWS and send data to Observability Cloud.
Access the guided setup for AWS integration 🔗
To access the guided setup for AWS integration, perform the following steps:
Log in to Splunk Observability Cloud.
Open the Amazon Web Services guided setup. Optionally, you can navigate to the guided setup on your own:
On the left navigation menu, select .
Select Add Integration to open the Integrate Your Data page.
On the Integrate Your Data page, select the tile for Amazon Web Services.
Follow the steps provided in the guided setup.
Note
While choosing data sources, you might see the option to import all data from built-in CloudWatch namespaces. Select it to ensure that built-in dashboards display automatically.
Authenticate to establish a connection between your AWS account and Splunk Observability Cloud. You’ll need the default IAM policy, which guided setup prompts you to copy in the Prepare AWS Account step. Read about the authentication options.
Select the rate at which you want Splunk Observability Cloud to poll CloudWatch for metric data, with 1 minute as the minimum value, and 10 minutes as the maximum value. For example, a value of 300 polls metrics once every 5 minutes. Poll rate is expressed in seconds.
If you run into a problem, the guided setup displays an error message in context at the step with the problem. The error message summarizes and suggests a fix for that problem.
To learn more about how to get AWS CloudWatch data into Observability Cloud, watch this video on the Splunk YouTube channel.
Activate Metric Streams 🔗
To activate Metric Streams, use the guided setup, and take the following considerations into account:
On the Define AWS connection screen, deactivate the CloudWatch Metrics polling box.
When creating the new AWS IAM policy, add these additional permissions to the ones already suggested in the guided setup.
Follow the instructions to activate Metric Streams.
Update your settings and deploy the CloudFormation template following these steps.
Review the default AWS integration settings 🔗
After creating an AWS IAM policy and assigning it to a particular role through the guided setup, you can modify your configuration.
Limit the scope of data collection 🔗
By default, Splunk Observability Cloud will bring in data from all supported AWS services associated with your account, with certain limitations.
To manage the amount of data to import, see Specify and limit the data and metadata to import.
Use the check box options in the guided setup to limit the scope of your data collection. These are the available options:
Amazon Cost and Usage Metrics
CloudWatch Metrics polling (you can deactivate it altogether, or deactivate the polling but activate AWS Metric Streams instead)
CloudWatch Logs
AWS regions to fetch data from
AWS services to fetch data from
In the Data Management menu in Observability Cloud, edit any integration to limit data import.
Use the AWS console to revise the contents of the
ActionandResourcefields.
Select a CloudFormation template 🔗
Select a CloudFormation template to collect logs or Metric Streams for each AWS region that you want to operate in.
Next steps 🔗
After you connect Splunk Observability Cloud with AWS, you can use Observability Cloud to track a series of metrics and analyze your AWS data in real time.
See the AWS official documentation for a list of the available AWS resources.
See how to leverage data from integration with AWS for more information.