awscli 1.37.3__py3-none-any.whl → 1.37.5__py3-none-any.whl

awscli/examples/ecr-public/get-registry-catalog-data.rst

@@ -0,0 +1,14 @@
+**To retrieve catalog metadata for a public ECR registry**
+
+The following ``get-registry-catalog-data`` retrieves catalog metadata for an ECR public registry. ::
+
+    aws ecr-public get-registry-catalog-data \
+        --region us-east-1
+
+Output::
+
+    {
+        "registryCatalogData": {
+            "displayName": "YourCustomPublicRepositoryalias"
+        }
+    }

awscli/examples/ecr-public/get-repository-catalog-data.rst

@@ -0,0 +1,29 @@
+**To retrieve catalog metadata for a repository in a public registry**
+
+The following ``get-repository-catalog-data`` example lists the catalog metadata for the repository ``project-a/nginx-web-app`` in a public registry. ::
+
+    aws ecr-public get-repository-catalog-data \
+        --repository-name project-a/nginx-web-app \
+        --region us-east-1
+
+Output::
+
+    {
+        "catalogData": {
+            "description": "My project-a ECR Public Repository",
+            "architectures": [
+                "ARM",
+                "ARM 64",
+                "x86",
+                "x86-64"
+            ],
+            "operatingSystems": [
+                "Linux"
+            ],
+            "logoUrl": "https://d3g9o9u8re44ak.cloudfront.net/logo/491d3846-8f33-4d8b-a10c-c2ce271e6c0d/4f09d87c-2569-4916-a932-5c296bf6f88a.png",
+            "aboutText": "## Quick reference\n\nMaintained <truncated>",
+            "usageText": "## Supported architectures\n\namd64, arm64v8\n\n## <truncated>"
+        }
+    }
+
+For more information, see `Repository catalog data <https://docs.aws.amazon.com/AmazonECR/latest/public/public-repository-catalog-data.html>`__ in the *Amazon ECR Public*.

awscli/examples/ecr-public/list-tags-for-resource.rst

@@ -0,0 +1,28 @@
+**To list tags for a public repository in a public registry**
+
+The following ``list-tags-for-resource`` example lists the tags for a resource named ``project-a/nginx-web-app`` in a public registry. ::
+
+    aws ecr-public list-tags-for-resource \
+        --resource-arn arn:aws:ecr-public::123456789012:repository/project-a/nginx-web-app \
+        --region us-east-1
+
+Output::
+
+    {
+        "tags": [
+            {
+                "Key": "Environment",
+                "Value": "Prod"
+            },
+            {
+                "Key": "stack",
+                "Value": "dev1"
+            },
+            {
+                "Key": "Name",
+                "Value": "project-a/nginx-web-app"
+            }
+        ]
+    }
+
+For more information, see `List tags for a public repository <https://docs.aws.amazon.com/AmazonECR/latest/public/ecr-public-using-tags.html>`__ in the *Amazon ECR Public*.

awscli/examples/ecr-public/put-registry-catalog-data.rst

@@ -0,0 +1,15 @@
+**To create or update catalog metadata for a public ECR registry**
+
+The following ``put-registry-catalog-data`` creates or updates catalog metadata for an ECR public registry. Only accounts that have the verified account badge can have a registry display name. ::
+
+    aws ecr-public put-registry-catalog-data \
+        --region us-east-1 \
+        --display-name <YourCustomPublicRepositoryalias>
+
+Output::
+
+    {
+        "registryCatalogData": {
+            "displayName": "YourCustomPublicRepositoryalias"
+        }
+    }

awscli/examples/ecr-public/put-repository-catalog-data.rst

@@ -1,4 +1,4 @@
-**Example 1: To creates or updates the catalog data for a repository in a public registry.**
+**To create or update the catalog data for a repository in a public registry**
 
 The following ``put-repository-catalog-data`` example creates or update catalog data for reposiotry named `project-a/nginx-web-app` in a public registry, along with logoImageBlob, aboutText, usageText and tags information. ::
 
@@ -10,6 +10,7 @@ The following ``put-repository-catalog-data`` example creates or update catalog
 Contents of ``repository-catalog-data.json``::
 
     {
+        "repositoryName": "project-a/nginx-web-app",
         "catalogData": {
             "description": "My project-a ECR Public Repository",
             "architectures": [
@@ -21,9 +22,9 @@ Contents of ``repository-catalog-data.json``::
             "operatingSystems": [
                 "Linux"
             ],
-            "logoImageBlob": "iVBORw0KGgoAAAANSUhEUgAAAYYAAAGGCAMAAABIXtbXAAAAq1BMVEVHcEz// <abbreviated>",
+            "logoImageBlob": "iVBORw0KGgoA<<truncated-for-better-reading>>ErkJggg==",
             "aboutText": "## Quick reference.",
-            "usageText": "## Supported architectures are as follows"
+            "usageText": "## Supported architectures are as follows."
         }
     }
 
@@ -41,7 +42,7 @@ Output::
             "operatingSystems": [
                 "Linux"
             ],
-            "logoUrl": "https://d3g9o9u8re44ak.cloudfront.net/logo/491d3846-8f33-4d8b-a10c-c2ce271e6c0d/4f09d87c-2569-4916-a932-5c296bf6f88a.png",
+            "logoUrl": "https://d3g9o9u8re44ak.cloudfront.net/logo/df86cf58-ee60-4061-b804-0be24d97ccb1/4a9ed9b2-69e4-4ede-b924-461462d20ef0.png",
             "aboutText": "## Quick reference.",
             "usageText": "## Supported architectures are as follows."
         }

awscli/examples/ecr-public/tag-resource.rst

@@ -0,0 +1,21 @@
+**Example 1: To tags an existing public repository in a public registry**
+
+The following ``tag-resource`` example tags a repository named ``project-a/nginx-web-app`` in a public registry. ::
+
+    aws ecr-public tag-resource \
+        --resource-arn arn:aws:ecr-public::123456789012:repository/project-a/nginx-web-app \
+        --tags Key=stack,Value=dev \
+        --region us-east-1
+
+For more information, see `Using Tags for a public repository <https://docs.aws.amazon.com/AmazonECR/latest/public/ecr-public-using-tags.html>`__ in the *Amazon ECR Public*.
+
+**Example 2: To tag an existing public repository with multiple tags in a public registry.**
+
+The following ``tag-resource`` example tags an existing repository with multiple tags. ::
+
+    aws ecr-public tag-resource \
+        --resource-arn arn:aws:ecr-public::890517186334:repository/project-a/nginx-web-app  \
+        --tags Key=key1,Value=value1 Key=key2,Value=value2 Key=key3,Value=value3 \
+        --region us-east-1
+
+For more information, see `Using Tags for a public repository <https://docs.aws.amazon.com/AmazonECR/latest/public/ecr-public-using-tags.html>`__ in the *Amazon ECR Public*.

awscli/examples/ecr-public/untag-resource.rst

@@ -0,0 +1,12 @@
+**Example 1: To untags an existing public repository in a public registry**
+
+The following ``untag-resource`` example tags a repository named ``project-a/nginx-web-app`` in a public registry. ::
+
+    aws ecr-public untag-resource \
+        --resource-arn arn:aws:ecr-public::123456789012:repository/project-a/nginx-web-app \
+        --tag-keys stack \
+        --region us-east-1
+
+This command produces no output.
+
+For more information, see `Using Tags for a public repository <https://docs.aws.amazon.com/AmazonECR/latest/public/ecr-public-using-tags.html>`__ in the *Amazon ECR Public*.

awscli/examples/ecs/describe-service-deployments.rst

@@ -0,0 +1,54 @@
+**To describe service deployment details**
+
+The following ``describe-service-deployments`` example returns the service deployment details for the service deployment with the ARN ``arn:aws:ecs:us-east-1:123456789012:service-deployment/example-cluster/example-service/ejGvqq2ilnbKT9qj0vLJe``. ::
+
+    aws ecs describe-service-deployments \
+        --service-deployment-arn arn:aws:ecs:us-east-1:123456789012:service-deployment/example-cluster/example-service/ejGvqq2ilnbKT9qj0vLJe
+
+Output::
+
+    {
+        "serviceDeployments": [
+            {
+                "serviceDeploymentArn": "arn:aws:ecs:us-east-1:123456789012:service-deployment/example-cluster/example-service/ejGvqq2ilnbKT9qj0vLJe",
+                "serviceArn": "arn:aws:ecs:us-east-1:123456789012:service/example-cluster/example-service",
+                "clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/example-cluster",
+                "createdAt": "2024-10-31T08:03:30.917000-04:00",
+                "startedAt": "2024-10-31T08:03:32.510000-04:00",
+                "finishedAt": "2024-10-31T08:05:04.527000-04:00",
+                "updatedAt": "2024-10-31T08:05:04.527000-04:00",
+                "sourceServiceRevisions": [],
+                "targetServiceRevision": {
+                    "arn": "arn:aws:ecs:us-east-1:123456789012:service-revision/example-cluster/example-service/1485800978477494678",
+                    "requestedTaskCount": 1,
+                    "runningTaskCount": 1,
+                    "pendingTaskCount": 0
+                },
+                "status": "SUCCESSFUL",
+                "deploymentConfiguration": {
+                    "deploymentCircuitBreaker": {
+                        "enable": true,
+                        "rollback": true
+                    },
+                    "maximumPercent": 200,
+                    "minimumHealthyPercent": 100,
+                    "alarms": {
+                        "alarmNames": [],
+                        "rollback": false,
+                        "enable": false
+                    }
+                },
+                "deploymentCircuitBreaker": {
+                    "status": "MONITORING_COMPLETE",
+                    "failureCount": 0,
+                    "threshold": 3
+                },
+                "alarms": {
+                    "status": "DISABLED"
+                }
+            }
+        ],
+        "failures": []
+    }
+
+For more information, see `View service history using Amazon ECS service deployments <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-deployment.html>`_ in the *Amazon ECS Developer Guide*.

awscli/examples/ecs/describe-service-revisions.rst

@@ -0,0 +1,60 @@
+**To describe service revision details**
+
+The following ``describe-service-revisions`` example returns the service revision details for the service revision with the ARN ``arn:aws:ecs:us-east-1:123456789012:service-revision/example-cluster/example-service/1485800978477494678``. ::
+
+    aws ecs describe-service-revisions \
+        --service-revision-arns arn:aws:ecs:us-east-1:123456789012:service-revision/example-cluster/example-service/1485800978477494678
+
+Output::
+
+    {
+        "serviceRevisions": [
+            {
+                "serviceRevisionArn": "arn:aws:ecs:us-east-1:123456789012:service-revision/example-cluster/example-service/1485800978477494678",
+                "serviceArn": "arn:aws:ecs:us-east-1:123456789012:service/example-cluster/example-service",
+                "clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/example-cluster",
+                "taskDefinition": "arn:aws:ecs:us-east-1:123456789012:task-definition/webserver:5",
+                "capacityProviderStrategy": [
+                    {
+                        "capacityProvider": "FARGATE",
+                        "weight": 1,
+                        "base": 0
+                    }
+                ],
+                "platformVersion": "1.4.0",
+                "platformFamily": "Linux",
+                "networkConfiguration": {
+                    "awsvpcConfiguration": {
+                        "subnets": [
+                            "subnet-0d0eab1bb38d5ca64",
+                            "subnet-0db5010045995c2d5"
+                        ],
+                        "securityGroups": [
+                            "sg-02556bf85a191f59a"
+                        ],
+                        "assignPublicIp": "ENABLED"
+                    }
+                },
+                "containerImages": [
+                    {
+                        "containerName": "aws-otel-collector",
+                        "imageDigest": "sha256:7a1b3560655071bcacd66902c20ebe9a69470d5691fe3bd36baace7c2f3c4640",
+                        "image": "public.ecr.aws/aws-observability/aws-otel-collector:v0.32.0"
+                    },
+                    {
+                        "containerName": "web",
+                        "imageDigest": "sha256:28402db69fec7c17e179ea87882667f1e054391138f77ffaf0c3eb388efc3ffb",
+                        "image": "nginx"
+                    }
+                ],
+                "guardDutyEnabled": false,
+                "serviceConnectConfiguration": {
+                    "enabled": false
+                },
+                "createdAt": "2024-10-31T08:03:29.302000-04:00"
+            }
+        ],
+        "failures": []
+    }
+
+For more information, see `Amazon ECS service revisions <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-revision.html>`_ in the *Amazon ECS Developer Guide*.

awscli/examples/ecs/list-service-deployments.rst

@@ -0,0 +1,25 @@
+**To list service deployments**
+
+The following ``list-service-deployments`` example retrieves the service deployments for the service named ``example-service``. ::
+
+    aws ecs list-service-deployments \
+        --service arn:aws:ecs:us-east-1:123456789012:service/example-cluster/example-service
+
+Output::
+
+    {
+        "serviceDeployments": [
+            {
+                "serviceDeploymentArn": "arn:aws:ecs:us-east-1:123456789012:service-deployment/example-cluster/example-service/ejGvqq2ilnbKT9qj0vLJe",
+                "serviceArn": "arn:aws:ecs:us-east-1:123456789012:service/example-cluster/example-service",
+                "clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/example-cluster",
+                "startedAt": "2024-10-31T08:03:32.510000-04:00",
+                "createdAt": "2024-10-31T08:03:30.917000-04:00",
+                "finishedAt": "2024-10-31T08:05:04.527000-04:00",
+                "targetServiceRevisionArn": "arn:aws:ecs:us-east-1:123456789012:service-revision/example-cluster/example-service/1485800978477494678",
+                "status": "SUCCESSFUL"
+            }
+        ]
+    }
+
+For more information, see `View service history using Amazon ECS service deployments <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-deployment.html>`_ in the *Amazon ECS Developer Guide*.

awscli/examples/eks/describe-cluster.rst

@@ -3,7 +3,7 @@
 The following ``describe-cluster`` example actively running EKS addon in your Amazon EKS cluster. ::
 
     aws eks describe-cluster \
-        --cluster-name my-eks-cluster
+        --name my-eks-cluster
 
 Output::
 

awscli/examples/emr/create-cluster-examples.rst

@@ -114,7 +114,7 @@ The following example references ``configurations.json`` as a local file. ::
 The following example references ``configurations.json`` as a file in Amazon S3. ::
 
     aws emr create-cluster \
-        --configurations https://s3.amazonaws.com/myBucket/configurations.json \
+        --configurations https://s3.amazonaws.com/amzn-s3-demo-bucket/configurations.json \
         --release-label emr-5.9.0 \
         --instance-groups InstanceGroupType=MASTER,InstanceCount=1,InstanceType=m4.large InstanceGroupType=CORE,InstanceCount=2,InstanceType=m4.large \
         --auto-terminate
@@ -223,7 +223,7 @@ The following ``create-cluster`` example uses the ``--enable-debugging`` paramet
 
     aws emr create-cluster \
         --enable-debugging \
-        --log-uri s3://myBucket/myLog \
+        --log-uri s3://amzn-s3-demo-bucket/myLog \
         --release-label emr-5.9.0 \
         --instance-groups InstanceGroupType=MASTER,InstanceCount=1,InstanceType=m4.large InstanceGroupType=CORE,InstanceCount=2,InstanceType=m4.large \
         --auto-terminate
@@ -357,7 +357,7 @@ The following ``create-cluster`` example adds steps by specifying a JAR file sto
 Custom JAR steps require the ``Jar=`` parameter, which specifies the path and file name of the JAR. Optional parameters are ``Type``, ``Name``, ``ActionOnFailure``, ``Args``, and ``MainClass``. If main class is not specified, the JAR file should specify ``Main-Class`` in its manifest file. ::
 
     aws emr create-cluster \
-        --steps Type=CUSTOM_JAR,Name=CustomJAR,ActionOnFailure=CONTINUE,Jar=s3://myBucket/mytest.jar,Args=arg1,arg2,arg3 Type=CUSTOM_JAR,Name=CustomJAR,ActionOnFailure=CONTINUE,Jar=s3://myBucket/mytest.jar,MainClass=mymainclass,Args=arg1,arg2,arg3  \
+        --steps Type=CUSTOM_JAR,Name=CustomJAR,ActionOnFailure=CONTINUE,Jar=s3://amzn-s3-demo-bucket/mytest.jar,Args=arg1,arg2,arg3 Type=CUSTOM_JAR,Name=CustomJAR,ActionOnFailure=CONTINUE,Jar=s3://amzn-s3-demo-bucket/mytest.jar,MainClass=mymainclass,Args=arg1,arg2,arg3  \
         --release-label emr-5.3.1 \
         --instance-groups InstanceGroupType=MASTER,InstanceCount=1,InstanceType=m4.large InstanceGroupType=CORE,InstanceCount=2,InstanceType=m4.large \
         --auto-terminate
@@ -503,7 +503,7 @@ The following ``create-cluster`` example creates an Amazon EMR cluster that uses
 
     aws emr create-cluster \
         --release-label emr-5.30.0 \
-        --log-uri s3://myBucket/myLog \
+        --log-uri s3://amzn-s3-demo-bucket/myLog \
         --log-encryption-kms-key-id arn:aws:kms:us-east-1:110302272565:key/dd559181-283e-45d7-99d1-66da348c4d33 \
         --instance-groups InstanceGroupType=MASTER,InstanceCount=1,InstanceType=m4.large InstanceGroupType=CORE,InstanceCount=2,InstanceType=m4.large
 

awscli/examples/emr/schedule-hbase-backup.rst

@@ -1,28 +1,28 @@
 **Note: This command can only be used with HBase on AMI version 2.x and 3.x**
 
-**1. To schedule a full HBase backup**
+**1. To schedule a full HBase backup**
 >>>>>>> 06ab6d6e13564b5733d75abaf3b599f93cf39a23
 
-- Command::
-
-    aws emr schedule-hbase-backup --cluster-id j-XXXXXXYY --type full --dir
-    s3://myBucket/backup --interval 10 --unit hours --start-time
-    2014-04-21T05:26:10Z --consistent
-
-- Output::
-
-    None
-
-
-**2. To schedule an incremental HBase backup**
-
-- Command::
-
-    aws emr schedule-hbase-backup --cluster-id j-XXXXXXYY --type incremental
-     --dir s3://myBucket/backup --interval 30 --unit minutes --start-time
-    2014-04-21T05:26:10Z --consistent
-
-- Output::
-
-    None
+- Command::
+
+    aws emr schedule-hbase-backup --cluster-id j-XXXXXXYY --type full --dir
+    s3://amzn-s3-demo-bucket/backup --interval 10 --unit hours --start-time
+    2014-04-21T05:26:10Z --consistent
+
+- Output::
+
+    None
+
+
+**2. To schedule an incremental HBase backup**
+
+- Command::
+
+    aws emr schedule-hbase-backup --cluster-id j-XXXXXXYY --type incremental
+     --dir s3://amzn-s3-demo-bucket/backup --interval 30 --unit minutes --start-time
+    2014-04-21T05:26:10Z --consistent
+
+- Output::
+
+    None
 

awscli/examples/importexport/create-job.rst

@@ -17,7 +17,7 @@ The file ``manifest`` is a YAML formatted text file in the current directory wit
   deviceId: 49382
   eraseDevice: yes
   notificationEmail: john.doe@example.com;jane.roe@example.com
-  bucket: myBucket
+  bucket: amzn-s3-demo-bucket
 
 For more information on the manifest file format, see `Creating Import Manifests`_ in the *AWS Import/Export Developer Guide*.
 
@@ -38,7 +38,7 @@ You can also pass the manifest as a string in quotes::
    deviceId: 49382
    eraseDevice: yes
    notificationEmail: john.doe@example.com;jane.roe@example.com
-   bucket: myBucket'
+   bucket: amzn-s3-demo-bucket'
 
 For information on quoting string arguments and using files, see `Specifying Parameter Values`_ in the *AWS CLI User Guide*.
 

awscli/examples/importexport/get-shipping-label.rst

@@ -4,7 +4,7 @@ The following command creates a pre-paid shipping label for the specified job::
 
 The output for the get-shipping-label command looks like the following::
 
-  https://s3.amazonaws.com/myBucket/shipping-label-EX1ID.pdf
+  https://s3.amazonaws.com/amzn-s3-demo-bucket/shipping-label-EX1ID.pdf
 
 The link in the output contains the pre-paid shipping label generated in a PDF. It also contains shipping instructions with a unique bar code to identify and authenticate your device. For more information about using the pre-paid shipping label and shipping your device, see `Shipping Your Storage Device`_ in the *AWS Import/Export Developer Guide*.
 

awscli/examples/importexport/get-status.rst

@@ -6,7 +6,7 @@ The output for the get-status command looks like the following::
 
   2015-05-27T18:58:21Z    manifestVersion:2.0
   generator:Text editor
-  bucket:myBucket
+  bucket:amzn-s3-demo-bucket
   deviceId:49382
   eraseDevice:yes
   notificationEmail:john.doe@example.com;jane.roe@example.com

awscli/examples/ivs-realtime/create-storage-configuration.rst

@@ -1,21 +1,21 @@
-**To create a composition storage configuration**
-
-The following ``create-storage-configuration`` example creates a composition storage configuration with the specified properties. ::
-
-    aws ivs-realtime create-storage-configuration \
-        --name "test-sc" --s3 "bucketName=test-bucket-name"
-
-Output::
-
-    {
-        "storageConfiguration": {
-            "arn": "arn:aws:ivs:ap-northeast-1:123456789012:storage-configuration/ABabCDcdEFef",
-            "name": "test-sc",
-            "s3": {
-                "bucketName": "test-bucket-name"
-            },
-            "tags": {}
-        }
-    }
-
+**To create a composition storage configuration**
+
+The following ``create-storage-configuration`` example creates a composition storage configuration with the specified properties. ::
+
+    aws ivs-realtime create-storage-configuration \
+        --name "test-sc" --s3 "bucketName=amzn-s3-demo-bucket"
+
+Output::
+
+    {
+        "storageConfiguration": {
+            "arn": "arn:aws:ivs:ap-northeast-1:123456789012:storage-configuration/ABabCDcdEFef",
+            "name": "test-sc",
+            "s3": {
+                "bucketName": "amzn-s3-demo-bucket"
+            },
+            "tags": {}
+        }
+    }
+
 For more information, see `Enabling Multiple Hosts on an Amazon IVS Stream <https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/multiple-hosts.html>`__ in the *Amazon Interactive Video Service User Guide*.

awscli/examples/ivs-realtime/get-storage-configuration.rst

@@ -1,21 +1,21 @@
-**To get a composition storage configuration**
-
-The following ``get-storage-configuration`` example gets the composition storage configuration specified by the given ARN (Amazon Resource Name). ::
-
-    aws ivs-realtime get-storage-configuration \
-        --name arn "arn:aws:ivs:ap-northeast-1:123456789012:storage-configuration/abcdABCDefgh"
-
-Output::
-
-    {
-        "storageConfiguration": {
-            "arn": "arn:aws:ivs:ap-northeast-1:123456789012:storage-configuration/abcdABCDefgh",
-            "name": "test-sc",
-            "s3": {
-                "bucketName": "test-bucket-name"
-            },
-            "tags": {}
-        }
-    }
-
+**To get a composition storage configuration**
+
+The following ``get-storage-configuration`` example gets the composition storage configuration specified by the given ARN (Amazon Resource Name). ::
+
+    aws ivs-realtime get-storage-configuration \
+        --name arn "arn:aws:ivs:ap-northeast-1:123456789012:storage-configuration/abcdABCDefgh"
+
+Output::
+
+    {
+        "storageConfiguration": {
+            "arn": "arn:aws:ivs:ap-northeast-1:123456789012:storage-configuration/abcdABCDefgh",
+            "name": "test-sc",
+            "s3": {
+                "bucketName": "amzn-s3-demo-bucket"
+            },
+            "tags": {}
+        }
+    }
+
 For more information, see `Enabling Multiple Hosts on an Amazon IVS Stream <https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/multiple-hosts.html>`__ in the *Amazon Interactive Video Service User Guide*.

awscli/examples/ivs-realtime/list-storage-configurations.rst

@@ -1,30 +1,30 @@
-**To list composition storage configurations**
-
-The following ``list-storage-configurations`` lists all composition storage configurations for your AWS account, in the AWS region where the API request is processed. ::
-
-    aws ivs-realtime list-storage-configurations
-
-Output::
-
-    {  
-        "storageConfigurations": [
-            {
-                "arn": "arn:aws:ivs:ap-northeast-1:123456789012:storage-configuration/abcdABCDefgh",
-                "name": "test-sc-1",
-                "s3": {
-                    "bucketName": "test-bucket-1-name"
-                },
-                "tags": {}
-            },
-            {
-                "arn": "arn:aws:ivs:ap-northeast-1:123456789012:storage-configuration/ABCefgEFGabc",
-                "name": "test-sc-2",
-                "s3": {
-                    "bucketName": "test-bucket-2-name"
-                },
-                "tags": {}
-            }
-        ]
-    }
-
+**To list composition storage configurations**
+
+The following ``list-storage-configurations`` lists all composition storage configurations for your AWS account, in the AWS region where the API request is processed. ::
+
+    aws ivs-realtime list-storage-configurations
+
+Output::
+
+    {  
+        "storageConfigurations": [
+            {
+                "arn": "arn:aws:ivs:ap-northeast-1:123456789012:storage-configuration/abcdABCDefgh",
+                "name": "test-sc-1",
+                "s3": {
+                    "bucketName": "amzn-s3-demo-bucket-1"
+                },
+                "tags": {}
+            },
+            {
+                "arn": "arn:aws:ivs:ap-northeast-1:123456789012:storage-configuration/ABCefgEFGabc",
+                "name": "test-sc-2",
+                "s3": {
+                    "bucketName": "amzn-s3-demo-bucket-2"
+                },
+                "tags": {}
+            }
+        ]
+    }
+
 For more information, see `Enabling Multiple Hosts on an Amazon IVS Stream <https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/multiple-hosts.html>`__ in the *Amazon Interactive Video Service User Guide*.

awscli/examples/kendra/create-data-source.rst

@@ -1,24 +1,24 @@
-**To create an Amazon Kendra data source connector**
-
-The following ``create-data-source`` creates and configures an Amazon Kendra data source connector. You can use ``describe-data-source`` to view the status of a data source connector, and read any error messages if the status shows a data source connector "FAILED" to completely create. ::
-
-    aws kendra create-data-source \
-        --name "example data source 1" \
-        --description "Example data source 1 for example index 1 contains the first set of example documents" \
-        --tags '{"Key": "test resources", "Value": "kendra"}, {"Key": "test resources", "Value": "aws"}' \
-        --role-arn "arn:aws:iam::my-account-id:role/KendraRoleForS3TemplateConfigDataSource" \
-        --index-id exampleindex1 \
-        --language-code "es" \
-        --schedule "0 0 18 ? * TUE,MON,WED,THU,FRI,SAT *" \
-        --configuration '{"TemplateConfiguration": {"Template": file://s3schemaconfig.json}}' \
-        --type "TEMPLATE" \
-        --custom-document-enrichment-configuration '{"PostExtractionHookConfiguration": {"LambdaArn": "arn:aws:iam::my-account-id:function/my-function-ocr-docs", "S3Bucket": "s3://my-s3-bucket/scanned-image-text-example-docs"}, "RoleArn": "arn:aws:iam:my-account-id:role/KendraRoleForCDE"}' \
-        --vpc-configuration '{"SecurityGroupIds": ["sg-1234567890abcdef0"], "SubnetIds": ["subnet-1c234","subnet-2b134"]}'
-
-Output::
-
-    {
-        "Id": "exampledatasource1"
-    }
-
+**To create an Amazon Kendra data source connector**
+
+The following ``create-data-source`` creates and configures an Amazon Kendra data source connector. You can use ``describe-data-source`` to view the status of a data source connector, and read any error messages if the status shows a data source connector "FAILED" to completely create. ::
+
+    aws kendra create-data-source \
+        --name "example data source 1" \
+        --description "Example data source 1 for example index 1 contains the first set of example documents" \
+        --tags '{"Key": "test resources", "Value": "kendra"}, {"Key": "test resources", "Value": "aws"}' \
+        --role-arn "arn:aws:iam::my-account-id:role/KendraRoleForS3TemplateConfigDataSource" \
+        --index-id exampleindex1 \
+        --language-code "es" \
+        --schedule "0 0 18 ? * TUE,MON,WED,THU,FRI,SAT *" \
+        --configuration '{"TemplateConfiguration": {"Template": file://s3schemaconfig.json}}' \
+        --type "TEMPLATE" \
+        --custom-document-enrichment-configuration '{"PostExtractionHookConfiguration": {"LambdaArn": "arn:aws:iam::my-account-id:function/my-function-ocr-docs", "S3Bucket": "s3://amzn-s3-demo-bucket/scanned-image-text-example-docs"}, "RoleArn": "arn:aws:iam:my-account-id:role/KendraRoleForCDE"}' \
+        --vpc-configuration '{"SecurityGroupIds": ["sg-1234567890abcdef0"], "SubnetIds": ["subnet-1c234","subnet-2b134"]}'
+
+Output::
+
+    {
+        "Id": "exampledatasource1"
+    }
+
 For more information, see `Getting started with an Amazon Kendra index and data source connector <https://docs.aws.amazon.com/kendra/latest/dg/getting-started.html>`__ in the *Amazon Kendra Developer Guide*.