diff --git a/specs/agents/tracing-instrumentation-db.md b/specs/agents/tracing-instrumentation-db.md
index 837aa832..ec46b0e8 100644
--- a/specs/agents/tracing-instrumentation-db.md
+++ b/specs/agents/tracing-instrumentation-db.md
@@ -69,6 +69,9 @@ The following fields are relevant for database and datastore spans. Where possib
 | __**service.target._**__ |<hr/>|<hr/>|
 |`_.type`| `dynamodb` ||
 |`_.name`| e.g. `us-east-1` | Use same value as `context.db.instance` |
+| __**otel.attributes._**__ |<hr/>|<hr/>|
+|`_["aws.dynamodb.table_names"]`| `[ MyTable ]` | The table names, if available. See [OTel Semantic Conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.23.0/specification/trace/semantic_conventions/instrumentation/aws-sdk.md). Note: this must be a single dotted string key in the `otel.attributes` mapping -- for example `{"otel": {"attributes": {"aws.dynamodb.table_names": [ MyTable ]}}}` -- and *not* a nested object. |
+|`_["aws.dynamodb.projection"]`| `Field1, Field2` | The value of the `ProjectionExpression` request parameter, if available. See [OTel Semantic Conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.23.0/specification/trace/semantic_conventions/instrumentation/aws-sdk.md). Note: this must be a single dotted string key in the `otel.attributes` mapping -- for example `{"otel": {"attributes": {"aws.dynamodb.projection": "Field1, Field2"}}}` -- and *not* a nested object. |
 
 ### AWS S3