feat: Documentation for Otel to AWS relationships - Elasticache Redis…

… cluster, SQS Queue, Lambda func, Elastic search cluster

src/content/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx

@@ -142,3 +142,22 @@ or with one of the methods below.
 Adding resource attributes prefixed with `tags` will result in a tag on your
 entity in New Relic. For example, adding the attribute `tags.mytag=myvalue`
 will result in the entity tag `mytag=myvalue`.
+
+#### ElastiCache (Redis)
+
+The Amazon CloudWatch Metric Streams integration for
+[Elasticache](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elasticache-monitoring-integration/)
+generates ElastiCache entities in New Relic. These entities will have the
+following entity tags:
+
+* `aws.elasticache.configurationEndpointAddress` or `aws.elasticache.endpointAddress` or `aws.elasticache.primaryEndpointAddress` or `aws.elasticache.readerEndpointAddress`
+* `aws.elasticache.configurationEndpointPort` or `aws.elasticache.endpointPort` or `aws.elasticache.primaryEndpointPort`, `aws.elasticache.readerEndpointPort`
+
+If your services use OpenTelemetry instrumentation for Redis it must emit
+the following attributes for a relationship to be generated:
+
+* `db.system`: This attribute must have the value `redis`.
+* `net.peer.name`: This attribute must match the corresponding endpoint tag of
+  the ElastiCache entity.
+* `net.peer.port`: This attribute must match the corresponding port tag of the
+  ElastiCache entity.