Merge branch 'v1.10' into shubham1172/add-bulk-publish-doc

Signed-off-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com>

daprdocs/content/en/reference/components-reference/supported-bindings/http.md

@@ -20,6 +20,13 @@ spec:
   metadata:
   - name: url
     value: http://something.com
+  - name: MTLSRootCA
+    value: /Users/somepath/root.pem #<path to root CA> or <pem encoded string>
+  - name: MTLSClientCert
+    value: /Users/somepath/client.pem #<path to client cert> or <pem encoded string>
+  - name: MTLSClientKey
+    value: /Users/somepath/client.key #<path to client key> or <pem encoded string>
+
 ```
 
 ## Spec metadata fields
@@ -27,6 +34,9 @@ spec:
 | Field              | Required | Binding support | Details | Example |
 |--------------------|:--------:|--------|--------|---------|
 | url                | Y        | Output |The base URL of the HTTP endpoint to invoke | `http://host:port/path`, `http://myservice:8000/customers`
+| MTLSRootCA         | N        | Output |Path to root ca certificate or pem encoded string |
+| MTLSClientCert     | N        | Output |Path to client certificate or pem encoded string  |
+| MTLSClientKey      | N        | Output |Path client private key or pem encoded string |
 
 ## Binding support
 
@@ -292,6 +302,17 @@ curl -d '{ "operation": "get" }' \
 
 {{< /tabs >}}
 
+## Using mTLS or enabling client TLS authentication along with HTTPS
+You can configure the HTTP binding to use mTLS or client TLS authentication along with HTTPS by providing the `MTLSRootCA`, `MTLSClientCert`, and `MTLSClientKey` metadata fields in the binding component.
+
+These fields can be passed as a file path or as a pem encoded string. 
+- If the file path is provided, the file is read and the contents are used. 
+- If the pem encoded string is provided, the string is used as is.
+When these fields are configured, the Dapr sidecar uses the provided certificate to authenticate itself with the server during the TLS handshake process.
+
+### When to use:
+You can use this when the server with which the HTTP binding is configured to communicate requires mTLS or client TLS authentication.
+
 
 ## Related links
 

daprdocs/content/en/reference/components-reference/supported-pubsub/setup-aws-snssqs.md

@@ -105,14 +105,21 @@ Using SQS FIFO (`fifo` metadata field set to `"true"`) per AWS specifications pr
 
 Specifying `fifoMessageGroupID` limits the number of concurrent consumers of the FIFO queue used to only one but guarantees global ordering of messages published by the app's Dapr sidecars. See [this AWS blog post](https://aws.amazon.com/blogs/compute/solving-complex-ordering-challenges-with-amazon-sqs-fifo-queues/) to better understand the topic of Message Group IDs and FIFO queues.
 
+To avoid losing the order of messages delivered to consumers, the FIFO configuration for the SQS Component requires the `concurrencyMode` metadata field set to `"single"`.
+
 #### Default parallel `concurrencyMode`
 
 Since v1.8.0, the component supports the `"parallel"` `concurrencyMode` as its default mode. In prior versions, the component default behavior was calling the subscriber a single message at a time and waiting for its response.
 
+#### SQS dead-letter Queues
+
+When configuring the PubSub component with SQS dead-letter queues, the metadata fields `messageReceiveLimit` and `sqsDeadLettersQueueName` must both be set to a value. For `messageReceiveLimit`, the value must be greater than `0` and the `sqsDeadLettersQueueName` must not be empty string.
+
 {{% alert title="Important" color="warning" %}}
 When running the Dapr sidecar (`daprd`) with your application on EKS (AWS Kubernetes) node/pod already attached to an IAM policy defining access to AWS resources, you **must not** provide AWS access-key, secret-key, and tokens in the definition of the component spec.  
 {{% /alert %}}
 
+
 ## Create an SNS/SQS instance
 
 {{< tabs "Self-Hosted" "Kubernetes" "AWS" >}}

daprdocs/data/components/pubsub/aws.yaml

@@ -1,6 +1,6 @@
 - component: AWS SNS/SQS
   link: setup-aws-snssqs
-  state: Beta
+  state: Stable
   version: v1
   since: "1.6"
   features: