docs: update LocalStack Replicator document to add support for batch replication (#184)

Author: quetzalliwrites

src/content/docs/aws/tooling/aws-replicator.mdx

@@ -64,6 +64,7 @@ If you have the AWS CLI v1 installed or no installation of the AWS CLI, the foll
 ### Trigger a replication job
 
 Replication jobs can be triggered using the LocalStack CLI or an HTTP API.
+
 Both methods have two steps:
 
 1. Submit a replication job.
@@ -72,10 +73,10 @@ Both methods have two steps:
 #### Using the LocalStack CLI
 
 The Replicator CLI is part of the LocalStack CLI.
+
 Follow the [installation instructions](/aws/getting-started/installation/#installing-localstack-cli) to set it up.
 
-To start a replication job, get the ARN of the resource to replicate.
-Then, trigger the job using the command:
+To start a replication job, get the ARN of the resource to replicate. Then, trigger the job using the command:
 
 ```bash showLineNumbers
 export LOCALSTACK_AUTH_TOKEN=<auth token>
@@ -84,10 +85,10 @@ export AWS_DEFAULT_REGION=...
 # export AWS_ACCESS_KEY_ID=
 # export AWS_SECRET_ACCESS_KEY=
 localstack replicator start \
- --resource-type <resource-type> \
- --resource-identifier <identifier> \
- [--target-account-id <account-id>] \
- [--target-region-name <region-name>]
+  --resource-type <resource-type> \
+  --resource-identifier <identifier> \
+  [--target-account-id <account-id>] \
+  [--target-region-name <region-name>]
 ```
 
 :::note
@@ -98,8 +99,24 @@ localstack replicator start --resource-arn <resource-arn>
 ```
 :::
 
-This triggers the replication job.
-The output will look similar to:
+You can also trigger batch replication jobs using the `--replication-type BATCH` flag.
+
+This currently supports the `AWS::SSM::Parameter` resource type and allows you to replicate all parameters under a given path prefix.
+
+For example, to replicate all parameters under `/dev/`:
+
+```bash
+localstack replicator start \
+  --replication-type BATCH \
+  --resource-type AWS::SSM::Parameter \
+  --resource-identifier /dev/
+```
+
+The `--resource-identifier` in this case must be a path prefix (not a wildcard or glob). All parameters under that prefix will be discovered and replicated.
+
+If `--replication-type` is not specified, the default is `SINGLE_RESOURCE`.
+
+The command triggers a replication job. The output will look similar to:
 
 ```json showLineNumbers
 {
@@ -112,18 +129,26 @@ The output will look similar to:
     "identifier": "myParameter"
   }
 }
-```
+``` 
 
 :::note
 - `--target-account-id` specifies the destination AWS account for replication.
   If not set, the resource is replicated into account `000000000000`.
+
 - `--target-region-name` specifies the destination AWS region.
   If not set, the resource is replicated into the default region from the provided credentials.
 :::
 
+
 #### Using the HTTP API
 
-To trigger replication via the HTTP API, send a `POST` request to `http://localhost.localstack.cloud:4566/_localstack/replicator/jobs` with the following payload:
+To trigger replication via the HTTP API, send a `POST` request to:
+
+```bash 
+ http://localhost.localstack.cloud:4566/_localstack/replicator/jobs
+ ```
+ 
+Use the following payload:
 
 ```json showLineNumbers
 {
@@ -143,13 +168,36 @@ To trigger replication via the HTTP API, send a `POST` request to `http://localh
 }
 ```
 
+To replicate multiple SSM parameters under a shared path, you can use `replication_type: "BATCH"` with the same `resource_type` and a path-style `identifier`. 
+
+For example:
+
+```json
+{
+  "replication_type": "BATCH",
+  "replication_job_config": {
+    "resource_type": "AWS::SSM::Parameter",
+    "identifier": "/dev/"
+  },
+  "source_aws_config": {
+    "aws_access_key_id": "...",
+    "aws_secret_access_key": "...",
+    "region_name": "..."
+  }
+} 
+```
+
+This triggers a batch replication job that discovers and replicates all SSM parameters under the `/dev/` path prefix.
+
+
 ### Check Replication Job Status
 
 Replication jobs run asynchronously, so you need to poll their status to check when they finish.
 
 #### Using the LocalStack CLI
 
 When creating a replication job, the response includes a `job_id`.
+
 Use this ID to check the job status:
 
 ```bash
@@ -158,7 +206,7 @@ export LOCALSTACK_AUTH_TOKEN=<auth token>
 localstack replicator status <job-id>
 ```
 
-This command returns the job status in JSON format, for example:
+This command returns the job status in JSON format. For example, here's a single-resource replication job:
 
 ```json showLineNumbers
 {
@@ -173,8 +221,29 @@ This command returns the job status in JSON format, for example:
 }
 ```
 
-For long-running jobs, the CLI can poll the status until the job reaches a terminal state.
-To wait for the job to finish, use the `--follow` flag.
+For a batch replication job, the output may include additional fields indicating how many resources were successfully replicated or failed:
+
+```json
+{
+  "job_id": "9acdc850-f71b-4474-b138-1668eb8b8396",
+  "state": "SUCCEEDED",
+  "error_message": null,
+  "type": "BATCH",
+  "replication_config": {
+    "resource_type": "AWS::SSM::Parameter",
+    "identifier": "/dev/"
+  },
+  "result": {
+    "resources_succeeded": 2,
+    "resources_failed": 0
+  }
+}
+``` 
+
+Jobs of type `BATCH` may include a `result` object with `resources_succeeded` and `resources_failed` fields.
+
+For long-running jobs, the CLI can poll the status until the job reaches a terminal state. To wait for the job to finish, use the `--follow` flag.
+
 
 #### Using the HTTP API