Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Scenario - Amazon Timestream

Scenario

The following examples use a DevOps monitoring scenario which is outlined in Scheduled queries sample schema.

The examples provide the scheduled query definition where you can plug in the appropriate configurations for where to receive execution status notifications for scheduled queries, where to receive reports for errors encountered during execution of a scheduled query, and the IAM role the scheduled query uses to perform its operations.

You can create these scheduled queries after filling in the preceding options, creating the target (or derived) table, and executing the through the AWS CLI. For example, assume that a scheduled query definition is stored in a file, scheduled_query_example.json. You can create the query using the CLI command.

aws timestream-query create-scheduled-query --cli-input-json file://scheduled_query_example.json --profile aws_profile --region us-east-1

In the preceding command, the profile passed using the --profile option must have the appropriate permissions to create scheduled queries. See Identity-based policies for Scheduled Queries for detailed instructions for the policies and permissions.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.