AWS aurora-dsql documentation change
Summary
Removed preview disclaimer, improved Kinesis read script to handle shards, updated operation type labels in CDC consumer example
Security assessment
Changes include usability improvements for reading from Kinesis streams and updated operation type handling. The removal of 'op' variable in deduplication example doesn't indicate security fixes. No security vulnerabilities or security features are documented.
Diff
diff --git a/aurora-dsql/latest/userguide/cdc-setup.md b/aurora-dsql/latest/userguide/cdc-setup.md index a9875e58b..09334b5ef 100644 --- a//aurora-dsql/latest/userguide/cdc-setup.md +++ b//aurora-dsql/latest/userguide/cdc-setup.md @@ -11,6 +10,0 @@ PrerequisitesStep 1: Create an Amazon Kinesis data streamStep 2: Create an IAM r -###### Important - -This feature is provided as an AWS Preview and is subject to change. For more information, see section 2, Betas and Previews, in the [AWS Service Terms](https://aws.amazon.com/service-terms/). To learn more about pricing for CDC streams, see the [Aurora DSQL pricing page](https://aws.amazon.com/rds/aurora/dsql/pricing/). - -Before general availability, we will add new operation types (`"op": "u"` for updates) to your stream payload. To ensure your application handles these changes without modification, treat any unrecognized `op` value as an upsert by applying the `after` payload. See [Understanding CDC records](./cdc-record-format.html) for details. - @@ -220 +214,2 @@ Insert a row into a table on your Aurora DSQL cluster. For example: -Read from the Kinesis data stream to verify that the CDC record arrived: +Read from the Kinesis data stream to verify that the CDC record arrived. Because Aurora DSQL uses randomized partition keys, the record can land on any shard. The following script checks the shards on the stream. CDC records can take a few seconds to arrive because of replication lag—if the output is empty, wait a moment and re-run the script. + @@ -221,0 +217,4 @@ Read from the Kinesis data stream to verify that the CDC record arrived: + for SHARD_ID in $(aws kinesis list-shards \ + --stream-name my-cdc-stream \ + --region region \ + --query 'Shards[].ShardId' --output text); do @@ -225 +224 @@ Read from the Kinesis data stream to verify that the CDC record arrived: - --shard-id shardId-000000000000 \ + --shard-id "$SHARD_ID" \ @@ -232 +231,3 @@ Read from the Kinesis data stream to verify that the CDC record arrived: - --region region + --region region \ + --query 'Records[].Data' --output text + done @@ -322,5 +323 @@ The following Python script reads CDC records from a Kinesis data stream and pri - # Aurora DSQL currently emits "c" for both inserts and updates. A subsequent - # release will emit "u" for updates, and "c" for inserts. Design your - # consumer to handle all three values; this map stays correct across the - # transition. - op_labels = {"c": "INSERT/UPDATE", "u": "UPDATE", "d": "DELETE"} + op_labels = {"c": "INSERT", "u": "UPDATE", "d": "DELETE"} @@ -364 +361 @@ The script prints each change event as it arrives. You see output similar to the - [INSERT/UPDATE] public.test_cdc txId=ffthunp5stx6ffs2vyfqoatmfu ts_ns=1705318200000000000 type=full + [INSERT] public.test_cdc txId=ffthunp5stx6ffs2vyfqoatmfu ts_ns=1705318200000000000 type=full @@ -388 +384,0 @@ Because Aurora DSQL CDC uses at-least-once delivery, production apps should dedu - op = payload["op"] @@ -430 +426 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -CDC streams (Preview) +CDC streams