- Más nuevo
- Más votos
- Más comentarios
Hello,
If I understood your question correctly, you were able to set the S3 error logs location, but can't see this location on the table details page?
If so, there are two options to check if this table uses a right S3 path:
- Using CLI run
aws timestream-write describe-table --table-name %tablename% --database-name %databasename%
- Using console you could go to the table details page and then press "Edit" button. It will show you the path which is currently used by this table.
Hope this will help you.
Hello, thanks for your answer.
if i check with CLI, i have : aws timestream-write describe-table --table-name %mytable% --database-name %mydb% { "Table": { "Arn": "arn:aws:timestream:eu-central-1:%myorg%:database/%mydb%/table/%mytable% ", "TableName": "%mytable% ", "DatabaseName": "%mydb%", "TableStatus": "ACTIVE", "RetentionProperties": { "MemoryStoreRetentionPeriodInHours": 4, "MagneticStoreRetentionPeriodInDays": 36500 }, "CreationTime": "2021-12-19T16:51:09.344000+00:00", "LastUpdatedTime": "2022-01-06T13:18:45.232000+00:00", "MagneticStoreWriteProperties": { "EnableMagneticStoreWrites": true, "MagneticStoreRejectedDataLocation": { "S3Configuration": { "BucketName": "%MYBUCKETISHERE%", "EncryptionOption": "SSE_S3" } } } } }
On My bucket, i have only the name of bucket ( no / and no /foldername) it's seems set.
But if i trigger error, when i write the same value with a time compatible with magnetic storage, i never see a log into bucket. ( but i can see rejected record with my test software in console mode).
Or maybe, this log will be only use if the write are proceessed asynchrounously ( big batch ) ?
Contenido relevante
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 7 meses
- OFICIAL DE AWSActualizada hace 3 años