Hello AWS Customer,
I understand you are trying to send a timestamp from in the future and it seems to not show up.
So, according to this timestream quota document: https://docs.aws.amazon.com/timestream/latest/developerguide/ts-limits.html#limits.default
Future ingestion period in minutes --> The maximum lead time (in minutes) for your time series data compared to the current system time. The default value is 15 minutes. For example, if the future ingestion period is 15 minutes, then Timestream will accept data that is up to 15 minutes ahead of the current system time.
So, you might be providing the future time which is greater than 15 minutes of the current system time. However, if your input future time is within 15 minutes and still not able to see the timestamp, i would recommend you to open a case with AWS Premium Support so the engineer can look into the logs/configuration to see if anything is missing/wrong.
What happens when you give TimeStream a timestamp in the future?Accepted Answerasked 8 months ago
Calculating measure from multi part LoRaWAN uplink message before storing in Timestream databaseAccepted Answerasked 3 months ago
How to use the payload's timestamp?asked a year ago
Errors at dimensions (empty value) in Timestream from an IoT RuleAccepted Answerasked a year ago
Input local timestamp in timestreamasked 3 months ago
IOT Core rules to map timestamp to timestreamAccepted Answerasked 9 months ago
Ingesting IoT Data to Timestream with TimestampAccepted Answerasked 2 years ago
IoT Rule -> Timestreamasked a month ago
Timestamp not taken over when inserting data via IoT Coreasked 2 years ago
AWS IoT Core Timestream Rule Action in ap-southeast-2asked 3 months ago