---
title: "Create a scrape job | Grafana Labs"
description: "Learn how to create and configure scrape jobs to collect specific metrics from your AWS services."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Create a scrape job

In this milestone, you’ll create a scrape job to customize metric collection from your AWS services. Scrape jobs let you specify which metrics to collect, set collection intervals, and apply filters to optimize performance and costs.

Scrape jobs provide granular control over metric collection, enabling you to focus on the most important metrics for your monitoring needs while avoiding unnecessary data collection.

1. In Grafana Cloud, open the navigation menu and select **Observability > Cloud provider > AWS**, then click the **Configuration** tab.

To create the scrape job, complete the following steps:

01. Select the **CloudWatch metrics scrape** tile.
02. Click **Add new scrape job**.
03. Select the AWS account you created in the previous milestone.
04. Enter a descriptive name for the scrape job in the **Scrape job name** field, for example `EC2-Production-Monitoring`.
05. Leave the **Include your AWS resource tags** checkbox selected. This option is selected by default because Cloud Provider Observability for AWS requires tag data on the scrape info metrics for the best possible dashboard experience.
06. Optionally, add static labels for easier filtering and grouping. Static labels are key-value pairs added to all metrics exported by this scrape job. In the **Static labels** section, enter a label key, for example `environment`, enter a value, for example `production`, and click **Add**.
07. Select the AWS services that you want to scrape. Find services by using search or browsing the list of services. A default set of metrics is collected for each service, which you can configure in the next step.
08. Optionally, enter the names of any custom CloudWatch namespaces that you want to scrape. Separate namespace names with a comma. In the next step, you’ll manually configure the metrics to collect for each namespace.
09. For each service that you selected, you can optionally choose **Edit metrics** to view and configure each metric and its corresponding statistics to collect.
    
    If you specified custom namespaces, you must choose **Edit metrics** for each namespace, and then type the exact name of each metric and its corresponding statistics to collect.
10. Click **Create scrape job** to begin collecting metrics.

The scrape job begins collecting metrics according to your configuration.

In your next milestone, you’ll monitor the job status to verify data is getting sent from your Amazon account to Grafana Cloud.

* * *

### More to explore (optional)

- [Create a scrape job using Terraform](/docs/grafana-cloud/monitor-infrastructure/monitor-cloud-provider/aws/cloudwatch-metrics/config-cw-metric-scrape/#create-a-scrape-job-using-terraform)

Were you successful?

![No](/media/images/svg/thumbs-up.svg) No

![Yes](/media/images/svg/thumbs-up.svg) Yes

Super! You can move to the next step.

* * *

### Troubleshooting

Explore the following troubleshooting topics if you need help:

- [Verify AWS IAM permissions](/docs/grafana-cloud/monitor-infrastructure/monitor-cloud-provider/aws/cloudwatch-metrics/config-cw-metric-scrape/#verify-aws-iam-permissions)
- [Check resource tagging](/docs/grafana-cloud/monitor-infrastructure/monitor-cloud-provider/aws/cloudwatch-metrics/config-cw-metric-scrape/#check-resource-tagging)

Please tell us what didn't work:

Submit

Submitting...

There was an error with your submission.

Thank you!

Need more support? Check out these [helpful resources.](/help/)