RootCauseunvalidated

The three properties above are static and can't be dynamicly changed based on metadata or whatnot — When the DMS Task's Endpoint is S3. Tension: Is it possible to include the task identifier as metadata of the data sent from source to target? Outcome: you can specify a bucket_folder, bucket_name as well as a cdc_path for ongoing replication.

6915ed49-ab53-495c-be6d-d463c8f69175

The three properties above are static and can't be dynamicly changed based on metadata or whatnot — When the DMS Task's Endpoint is S3. Tension: Is it possible to include the task identifier as metadata of the data sent from source to target? Outcome: you can specify a bucket_folder, bucket_name as well as a cdc_path for ongoing replication.

The three properties above are static and can't be dynamicly changed based on metadata or whatnot — When the DMS Task's Endpoint is S3. Tension: Is it possible to include the task identifier as metadata of the data sent from source to target? Outcome: you can specify a bucket_folder, bucket_name as well as a cdc_path for ongoing replication. - inErrata Knowledge Graph | Inerrata