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

awscli/examples/polly/list-speech-synthesis-tasks.rst

@@ -1,25 +1,25 @@
-**To list your speech synthesis tasks**
-
-The following ``list-speech-synthesis-tasks`` example lists your speech synthesis tasks. ::
-
-    aws polly list-speech-synthesis-tasks 
-
-Output::
-
-    {
-        "SynthesisTasks": [
-            {
-                "TaskId": "70b61c0f-57ce-4715-a247-cae8729dcce9",
-                "TaskStatus": "completed",
-                "OutputUri": "https://s3.us-west-2.amazonaws.com/my-s3-bucket/70b61c0f-57ce-4715-a247-cae8729dcce9.mp3",
-                "CreationTime": 1603911042.689,
-                "RequestCharacters": 1311,
-                "OutputFormat": "mp3",
-                "TextType": "text",
-                "VoiceId": "Joanna"
-            }
-        ]
-    }
-
-For more information, see `Creating long audio files <https://docs.aws.amazon.com/polly/latest/dg/longer-cli.html>`__ in the *Amazon Polly Developer Guide*.
-
+**To list your speech synthesis tasks**
+
+The following ``list-speech-synthesis-tasks`` example lists your speech synthesis tasks. ::
+
+    aws polly list-speech-synthesis-tasks 
+
+Output::
+
+    {
+        "SynthesisTasks": [
+            {
+                "TaskId": "70b61c0f-57ce-4715-a247-cae8729dcce9",
+                "TaskStatus": "completed",
+                "OutputUri": "https://s3.us-west-2.amazonaws.com/amzn-s3-demo-bucket/70b61c0f-57ce-4715-a247-cae8729dcce9.mp3",
+                "CreationTime": 1603911042.689,
+                "RequestCharacters": 1311,
+                "OutputFormat": "mp3",
+                "TextType": "text",
+                "VoiceId": "Joanna"
+            }
+        ]
+    }
+
+For more information, see `Creating long audio files <https://docs.aws.amazon.com/polly/latest/dg/longer-cli.html>`__ in the *Amazon Polly Developer Guide*.
+

awscli/examples/polly/start-speech-synthesis-task.rst

@@ -1,27 +1,27 @@
-**To synthesize text**
-
-The following ``start-speech-synthesis-task`` example synthesizes the text in ``text_file.txt`` and stores the resulting MP3 file in the specified bucket. ::
-
-    aws polly start-speech-synthesis-task \
-        --output-format mp3 \
-        --output-s3-bucket-name my-s3-bucket \
-        --text  file://text_file.txt \
-        --voice-id Joanna
-
-Output::
-
-    {
-        "SynthesisTask": {
-            "TaskId": "70b61c0f-57ce-4715-a247-cae8729dcce9",
-            "TaskStatus": "scheduled",
-            "OutputUri": "https://s3.us-east-2.amazonaws.com/my-s3-bucket/70b61c0f-57ce-4715-a247-cae8729dcce9.mp3",
-            "CreationTime": 1603911042.689,
-            "RequestCharacters": 1311,
-            "OutputFormat": "mp3",
-            "TextType": "text",
-            "VoiceId": "Joanna"
-        }
-    }
-
-For more information, see `Creating long audio files <https://docs.aws.amazon.com/polly/latest/dg/longer-cli.html>`__ in the *Amazon Polly Developer Guide*.
-
+**To synthesize text**
+
+The following ``start-speech-synthesis-task`` example synthesizes the text in ``text_file.txt`` and stores the resulting MP3 file in the specified bucket. ::
+
+    aws polly start-speech-synthesis-task \
+        --output-format mp3 \
+        --output-s3-bucket-name amzn-s3-demo-bucket \
+        --text  file://text_file.txt \
+        --voice-id Joanna
+
+Output::
+
+    {
+        "SynthesisTask": {
+            "TaskId": "70b61c0f-57ce-4715-a247-cae8729dcce9",
+            "TaskStatus": "scheduled",
+            "OutputUri": "https://s3.us-east-2.amazonaws.com/amzn-s3-demo-bucket/70b61c0f-57ce-4715-a247-cae8729dcce9.mp3",
+            "CreationTime": 1603911042.689,
+            "RequestCharacters": 1311,
+            "OutputFormat": "mp3",
+            "TextType": "text",
+            "VoiceId": "Joanna"
+        }
+    }
+
+For more information, see `Creating long audio files <https://docs.aws.amazon.com/polly/latest/dg/longer-cli.html>`__ in the *Amazon Polly Developer Guide*.
+

awscli/examples/qldb/describe-journal-s3-export.rst

@@ -11,7 +11,7 @@ Output::
     {
         "ExportDescription": {
             "S3ExportConfiguration": {
-                "Bucket": "awsExampleBucket",
+                "Bucket": "amzn-s3-demo-bucket",
                 "Prefix": "ledgerexport1/",
                 "EncryptionConfiguration": {
                     "ObjectEncryptionType": "SSE_S3"

awscli/examples/qldb/export-journal-to-s3.rst

@@ -12,7 +12,7 @@ The following ``export-journal-to-s3`` example creates an export job for journal
 Contents of ``my-s3-export-config.json``::
 
     {
-        "Bucket": "awsExampleBucket",
+        "Bucket": "amzn-s3-demo-bucket",
         "Prefix": "ledgerexport1/",
         "EncryptionConfiguration": {
             "ObjectEncryptionType": "SSE_S3"

awscli/examples/qldb/list-journal-s3-exports-for-ledger.rst

@@ -14,7 +14,7 @@ Output::
                 "ExclusiveEndTime": 1568847599.0,
                 "ExportCreationTime": 1568847801.418,
                 "S3ExportConfiguration": {
-                    "Bucket": "awsExampleBucket",
+                    "Bucket": "amzn-s3-demo-bucket",
                     "Prefix": "ledgerexport1/",
                     "EncryptionConfiguration": {
                         "ObjectEncryptionType": "SSE_S3"

awscli/examples/qldb/list-journal-s3-exports.rst

@@ -15,7 +15,7 @@ Output::
                     "EncryptionConfiguration": {
                         "ObjectEncryptionType": "SSE_S3"
                     },
-                    "Bucket": "awsExampleBucket",
+                    "Bucket": "amzn-s3-demo-bucket",
                     "Prefix": "ledgerexport1/"
                 },
                 "RoleArn": "arn:aws:iam::123456789012:role/my-s3-export-role",
@@ -31,7 +31,7 @@ Output::
                     "EncryptionConfiguration": {
                         "ObjectEncryptionType": "SSE_S3"
                     },
-                    "Bucket": "awsExampleBucket",
+                    "Bucket": "amzn-s3-demo-bucket",
                     "Prefix": "ledgerexport1/"
                 },
                 "RoleArn": "arn:aws:iam::123456789012:role/my-s3-export-role",

awscli/examples/rds/download-db-log-file-portion.rst

@@ -1,4 +1,4 @@
-**To download a DB log file**
+**Example 1: To download the latest part of a DB log file**
 
 The following ``download-db-log-file-portion`` example downloads only the latest part of your log file, saving it to a local file named ``tail.txt``. ::
 
@@ -7,7 +7,11 @@ The following ``download-db-log-file-portion`` example downloads only the latest
         --log-file-name log.txt \
         --output text > tail.txt
 
-To download the entire file, you need to include the ``--starting-token 0`` parameter. The following example saves the output to a local file named ``full.txt``. ::
+The saved file might contain blank lines.  They appear at the end of each part of the log file while being downloaded.
+
+**Example 2: To download an entire DB log file**
+
+The following ``download-db-log-file-portion`` example downloads the entire log file, using the ``--starting-token 0`` parameter, and saves the output to a local file named ``full.txt``. ::
 
     aws rds download-db-log-file-portion \
         --db-instance-identifier test-instance \
@@ -15,4 +19,4 @@ To download the entire file, you need to include the ``--starting-token 0`` para
         --starting-token 0 \
         --output text > full.txt
 
-The saved file might contain blank lines.  They appear at the end of each part of the log file while being downloaded.  This generally doesn't cause any trouble in your log file analysis.
+The saved file might contain blank lines.  They appear at the end of each part of the log file while being downloaded.

awscli/examples/resourcegroupstaggingapi/untag-resources.rst

@@ -3,7 +3,7 @@
 The following ``untag-resources`` example removes the specified tag keys and any associated values from the specified resource. ::
 
     aws resourcegroupstaggingapi untag-resources \
-        --resource-arn-list arn:aws:s3:::awsexamplebucket \
+        --resource-arn-list arn:aws:s3:::amzn-s3-demo-bucket \
         --tag-keys Environment CostCenter
 
 Output::

awscli/examples/s3/cp.rst

@@ -45,11 +45,11 @@ Output::
 
 The following ``cp`` command copies a single object to a specified bucket while retaining its original name::
 
-    aws s3 cp s3://mybucket/test.txt s3://mybucket2/
+    aws s3 cp s3://mybucket/test.txt s3://amzn-s3-demo-bucket2/
 
 Output::
 
-    copy: s3://mybucket/test.txt to s3://mybucket2/test.txt
+    copy: s3://mybucket/test.txt to s3://amzn-s3-demo-bucket2/test.txt
 
 **Example 6: Recursively copying S3 objects to a local directory**
 
@@ -85,25 +85,25 @@ When passed with the parameter ``--recursive``, the following ``cp`` command rec
 specified bucket to another bucket while excluding some objects by using an ``--exclude`` parameter.  In this example,
 the bucket ``mybucket`` has the objects ``test1.txt`` and ``another/test1.txt``::
 
-    aws s3 cp s3://mybucket/ s3://mybucket2/ \
+    aws s3 cp s3://mybucket/ s3://amzn-s3-demo-bucket2/ \
         --recursive \
         --exclude "another/*"
 
 Output::
 
-    copy: s3://mybucket/test1.txt to s3://mybucket2/test1.txt
+    copy: s3://mybucket/test1.txt to s3://amzn-s3-demo-bucket2/test1.txt
 
 You can combine ``--exclude`` and ``--include`` options to copy only objects that match a pattern, excluding all others::
 
-    aws s3 cp s3://mybucket/logs/ s3://mybucket2/logs/ \
+    aws s3 cp s3://mybucket/logs/ s3://amzn-s3-demo-bucket2/logs/ \
         --recursive \
         --exclude "*" \
         --include "*.log"
 
 Output::
 
-    copy: s3://mybucket/logs/test/test.log to s3://mybucket2/logs/test/test.log
-    copy: s3://mybucket/logs/test3.log to s3://mybucket2/logs/test3.log
+    copy: s3://mybucket/logs/test/test.log to s3://amzn-s3-demo-bucket2/logs/test/test.log
+    copy: s3://mybucket/logs/test3.log to s3://amzn-s3-demo-bucket2/logs/test3.log
 
 **Example 9: Setting the Access Control List (ACL) while copying an S3 object**
 

awscli/examples/s3/ls.rst

@@ -1,13 +1,13 @@
 **Example 1: Listing all user owned buckets**
 
-The following ``ls`` command lists all of the bucket owned by the user.  In this example, the user owns the buckets ``mybucket`` and ``mybucket2``.  The timestamp is the date the bucket was created, shown in your machine's time zone.  This date can change when making changes to your bucket, such as editing its bucket policy.  Note if  ``s3://`` is used for the path argument ``<S3Uri>``, it will list all of the buckets as well. ::
+The following ``ls`` command lists all of the bucket owned by the user.  In this example, the user owns the buckets ``mybucket`` and ``amzn-s3-demo-bucket2``.  The timestamp is the date the bucket was created, shown in your machine's time zone.  This date can change when making changes to your bucket, such as editing its bucket policy.  Note if  ``s3://`` is used for the path argument ``<S3Uri>``, it will list all of the buckets as well. ::
 
     aws s3 ls
 
 Output::
 
     2013-07-11 17:08:50 mybucket
-    2013-07-24 14:55:44 mybucket2
+    2013-07-24 14:55:44 amzn-s3-demo-bucket2
     
 **Example 2: Listing all prefixes and objects in a bucket**
 

awscli/examples/s3/mv.rst

@@ -32,11 +32,11 @@ Output::
 
 The following ``mv`` command moves a single object to a specified bucket while retaining its original name::
 
-    aws s3 mv s3://mybucket/test.txt s3://mybucket2/
+    aws s3 mv s3://mybucket/test.txt s3://amzn-s3-demo-bucket2/
 
 Output::
 
-    move: s3://mybucket/test.txt to s3://mybucket2/test.txt
+    move: s3://mybucket/test.txt to s3://amzn-s3-demo-bucket2/test.txt
 
 **Example 5: Move all objects and prefixes in a bucket to the local directory**
 
@@ -64,7 +64,7 @@ this example, the directory ``myDir`` has the files ``test1.txt`` and ``test2.jp
 
 Output::
 
-    move: myDir/test1.txt to s3://mybucket2/test1.txt
+    move: myDir/test1.txt to s3://amzn-s3-demo-bucket2/test1.txt
 
 **Example 7: Move all objects and prefixes in a bucket to the local directory, except specified prefix**
 
@@ -72,13 +72,13 @@ When passed with the parameter ``--recursive``, the following ``mv`` command rec
 specified bucket to another bucket while excluding some objects by using an ``--exclude`` parameter.  In this example,
 the bucket ``mybucket`` has the objects ``test1.txt`` and ``another/test1.txt``. ::
 
-    aws s3 mv s3://mybucket/ s3://mybucket2/ \
+    aws s3 mv s3://mybucket/ s3://amzn-s3-demo-bucket2/ \
         --recursive \
         --exclude "mybucket/another/*"
 
 Output::
 
-    move: s3://mybucket/test1.txt to s3://mybucket2/test1.txt
+    move: s3://mybucket/test1.txt to s3://amzn-s3-demo-bucket2/test1.txt
 
 **Example 8: Move an object to the specified bucket and set the ACL**
 

awscli/examples/s3/sync.rst

@@ -21,15 +21,15 @@ prefix and bucket by copying S3 objects. An S3 object will require copying if th
 the last modified time of the source is newer than the last modified time of the destination, or the S3 object does not
 exist under the specified bucket and prefix destination. 
 
-In this example, the user syncs the bucket ``mybucket`` to the bucket ``mybucket2``. The bucket ``mybucket`` contains the objects ``test.txt`` and ``test2.txt``. The bucket
-``mybucket2`` contains no objects::
+In this example, the user syncs the bucket ``mybucket`` to the bucket ``amzn-s3-demo-bucket2``. The bucket ``mybucket`` contains the objects ``test.txt`` and ``test2.txt``. The bucket
+``amzn-s3-demo-bucket2`` contains no objects::
 
-    aws s3 sync s3://mybucket s3://mybucket2
+    aws s3 sync s3://mybucket s3://amzn-s3-demo-bucket2
 
 Output::
 
-    copy: s3://mybucket/test.txt to s3://mybucket2/test.txt
-    copy: s3://mybucket/test2.txt to s3://mybucket2/test2.txt
+    copy: s3://mybucket/test.txt to s3://amzn-s3-demo-bucket2/test.txt
+    copy: s3://mybucket/test2.txt to s3://amzn-s3-demo-bucket2/test2.txt
 
 **Example 3: Sync all S3 objects from the specified S3 bucket to the local directory**
 

awscli/examples/s3api/put-bucket-acl.rst

@@ -1,7 +1,7 @@
 This example grants ``full control`` to two AWS users (*user1@example.com* and *user2@example.com*) and ``read``
 permission to everyone::
 
-   aws s3api put-bucket-acl --bucket MyBucket --grant-full-control emailaddress=user1@example.com,emailaddress=user2@example.com --grant-read uri=http://acs.amazonaws.com/groups/global/AllUsers
+   aws s3api put-bucket-acl --bucket amzn-s3-demo-bucket --grant-full-control emailaddress=user1@example.com,emailaddress=user2@example.com --grant-read uri=http://acs.amazonaws.com/groups/global/AllUsers
 
 See http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTacl.html for details on custom ACLs (the s3api ACL
 commands, such as ``put-bucket-acl``, use the same shorthand argument notation).

awscli/examples/s3api/put-bucket-cors.rst

@@ -1,7 +1,7 @@
 The following example enables ``PUT``, ``POST``, and ``DELETE`` requests from *www.example.com*, and enables ``GET``
 requests from any domain::
 
-   aws s3api put-bucket-cors --bucket MyBucket --cors-configuration file://cors.json
+   aws s3api put-bucket-cors --bucket amzn-s3-demo-bucket --cors-configuration file://cors.json
 
    cors.json:
    {

awscli/examples/s3api/put-bucket-logging.rst

@@ -1,9 +1,9 @@
 **Example 1: To set bucket policy logging**
 
-The following ``put-bucket-logging`` example sets the logging policy for *MyBucket*. First, grant the logging service principal permission in your bucket policy using the ``put-bucket-policy`` command. ::
+The following ``put-bucket-logging`` example sets the logging policy for *amzn-s3-demo-bucket*. First, grant the logging service principal permission in your bucket policy using the ``put-bucket-policy`` command. ::
 
     aws s3api put-bucket-policy \
-        --bucket MyBucket \
+        --bucket amzn-s3-demo-bucket \
         --policy file://policy.json
 
 Contents of ``policy.json``::
@@ -16,7 +16,7 @@ Contents of ``policy.json``::
                 "Effect": "Allow",
                 "Principal": {"Service": "logging.s3.amazonaws.com"},
                 "Action": "s3:PutObject",
-                "Resource": "arn:aws:s3:::MyBucket/Logs/*",
+                "Resource": "arn:aws:s3:::amzn-s3-demo-bucket/Logs/*",
                 "Condition": {
                     "ArnLike": {"aws:SourceARN": "arn:aws:s3:::SOURCE-BUCKET-NAME"},
                     "StringEquals": {"aws:SourceAccount": "SOURCE-AWS-ACCOUNT-ID"}
@@ -28,14 +28,14 @@ Contents of ``policy.json``::
 To apply the logging policy, use ``put-bucket-logging``. ::
 
     aws s3api put-bucket-logging \
-        --bucket MyBucket \
+        --bucket amzn-s3-demo-bucket \
         --bucket-logging-status file://logging.json
 
 Contents of ``logging.json``::
 
    {
         "LoggingEnabled": {
-            "TargetBucket": "MyBucket",
+            "TargetBucket": "amzn-s3-demo-bucket",
             "TargetPrefix": "Logs/"
         }
     }
@@ -46,26 +46,26 @@ For more information, see `Amazon S3 Server Access Logging <https://docs.aws.ama
 
 **Example 2: To set a bucket policy for logging access to only a single user**
 
-The following ``put-bucket-logging`` example sets the logging policy for *MyBucket*. The AWS user *bob@example.com* will have full control over
+The following ``put-bucket-logging`` example sets the logging policy for *amzn-s3-demo-bucket*. The AWS user *bob@example.com* will have full control over
 the log files, and no one else has any access. First, grant S3 permission with ``put-bucket-acl``. ::
 
     aws s3api put-bucket-acl \
-        --bucket MyBucket \
+        --bucket amzn-s3-demo-bucket \
         --grant-write URI=http://acs.amazonaws.com/groups/s3/LogDelivery \
         --grant-read-acp URI=http://acs.amazonaws.com/groups/s3/LogDelivery
 
 Then apply the logging policy using ``put-bucket-logging``. ::
 
     aws s3api put-bucket-logging \
-        --bucket MyBucket \
+        --bucket amzn-s3-demo-bucket \
         --bucket-logging-status file://logging.json
 
 Contents of ``logging.json``::
 
     {
         "LoggingEnabled": {
-            "TargetBucket": "MyBucket",
-            "TargetPrefix": "MyBucketLogs/",
+            "TargetBucket": "amzn-s3-demo-bucket",
+            "TargetPrefix": "amzn-s3-demo-bucket-logs/",
             "TargetGrants": [
                 {
                     "Grantee": {

awscli/examples/s3api/put-bucket-policy.rst

@@ -1,7 +1,7 @@
-This example allows all users to retrieve any object in *MyBucket* except those in the *MySecretFolder*. It also
+This example allows all users to retrieve any object in *amzn-s3-demo-bucket* except those in the *MySecretFolder*. It also
 grants ``put`` and ``delete`` permission to the root user of the AWS account ``1234-5678-9012``::
 
-   aws s3api put-bucket-policy --bucket MyBucket --policy file://policy.json
+   aws s3api put-bucket-policy --bucket amzn-s3-demo-bucket --policy file://policy.json
 
    policy.json:
    {
@@ -10,13 +10,13 @@ grants ``put`` and ``delete`` permission to the root user of the AWS account ``1
             "Effect": "Allow",
             "Principal": "*",
             "Action": "s3:GetObject",
-            "Resource": "arn:aws:s3:::MyBucket/*"
+            "Resource": "arn:aws:s3:::amzn-s3-demo-bucket/*"
          },
          {
             "Effect": "Deny",
             "Principal": "*",
             "Action": "s3:GetObject",
-            "Resource": "arn:aws:s3:::MyBucket/MySecretFolder/*"
+            "Resource": "arn:aws:s3:::amzn-s3-demo-bucket/MySecretFolder/*"
          },
          {
             "Effect": "Allow",
@@ -27,7 +27,7 @@ grants ``put`` and ``delete`` permission to the root user of the AWS account ``1
                "s3:DeleteObject",
                "s3:PutObject"
             ],
-            "Resource": "arn:aws:s3:::MyBucket/*"
+            "Resource": "arn:aws:s3:::amzn-s3-demo-bucket/*"
          }
       ]
    }

awscli/examples/s3api/put-object-acl.rst

@@ -1,7 +1,7 @@
 The following command grants ``full control`` to two AWS users (*user1@example.com* and *user2@example.com*) and ``read``
 permission to everyone::
 
-   aws s3api put-object-acl --bucket MyBucket --key file.txt --grant-full-control emailaddress=user1@example.com,emailaddress=user2@example.com --grant-read uri=http://acs.amazonaws.com/groups/global/AllUsers
+   aws s3api put-object-acl --bucket amzn-s3-demo-bucket --key file.txt --grant-full-control emailaddress=user1@example.com,emailaddress=user2@example.com --grant-read uri=http://acs.amazonaws.com/groups/global/AllUsers
 
 See http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTacl.html for details on custom ACLs (the s3api ACL
 commands, such as ``put-object-acl``, use the same shorthand argument notation).

awscli/examples/securitylake/create-subscriber.rst

@@ -0,0 +1,83 @@
+**Example 1: To create a subscriber with data access**
+
+The following ``create-subscriber`` example creates a subscriber in Security Lake with access to data in the current AWS Region for the specified subscriber identity for an AWS source. ::
+
+    aws securitylake create-subscriber \
+        --access-types "S3" \
+        --sources '[{"awsLogSource": {"sourceName": "VPC_FLOW","sourceVersion": "2.0"}}]' \
+        --subscriber-name 'opensearch-s3' \
+        --subscriber-identity '{"principal": "029189416600","externalId": "123456789012"}'
+
+Output::
+
+    {
+        "subscriber": {
+            "accessTypes": [
+                "S3"
+            ],
+            "createdAt": "2024-07-17T19:08:26.787000+00:00",
+            "roleArn": "arn:aws:iam::773172568199:role/AmazonSecurityLake-896f218b-cfba-40be-a255-8b49a65d0407",
+            "s3BucketArn": "arn:aws:s3:::aws-security-data-lake-us-east-1-um632ufwpvxkyz0bc5hkb64atycnf3",
+            "sources": [
+                {
+                    "awsLogSource": {
+                        "sourceName": "VPC_FLOW",
+                        "sourceVersion": "2.0"
+                    }
+                }
+            ],
+            "subscriberArn": "arn:aws:securitylake:us-east-1:773172568199:subscriber/896f218b-cfba-40be-a255-8b49a65d0407",
+            "subscriberId": "896f218b-cfba-40be-a255-8b49a65d0407",
+            "subscriberIdentity": {
+                "externalId": "123456789012",
+                "principal": "029189416600"
+            },
+            "subscriberName": "opensearch-s3",
+            "subscriberStatus": "ACTIVE",
+            "updatedAt": "2024-07-17T19:08:27.133000+00:00"
+        }
+    }
+
+For more information, see `Creating a subscriber with data access <https://docs.aws.amazon.com/security-lake/latest/userguide/subscriber-data-access.html#create-subscriber-data-access>`__ in the *Amazon Security Lake User Guide*.
+
+**Example 2: To create a subscriber with query access**
+
+The following ``create-subscriber`` example creates a subscriber in Security Lake with query access in the current AWS Region for the specified subscriber identity. ::
+
+    aws securitylake create-subscriber \
+        --access-types "LAKEFORMATION" \
+        --sources '[{"awsLogSource": {"sourceName": "VPC_FLOW","sourceVersion": "2.0"}}]' \
+        --subscriber-name 'opensearch-s3' \
+        --subscriber-identity '{"principal": "029189416600","externalId": "123456789012"}'
+
+Output::
+
+    {
+        "subscriber": {
+            "accessTypes": [
+                "LAKEFORMATION"
+            ],
+            "createdAt": "2024-07-18T01:05:55.853000+00:00",
+            "resourceShareArn": "arn:aws:ram:us-east-1:123456789012:resource-share/8c31da49-c224-4f1e-bb12-37ab756d6d8a",
+            "resourceShareName": "LakeFormation-V2-NAMENAMENA-123456789012",
+            "sources": [
+                {
+                    "awsLogSource": {
+                        "sourceName": "VPC_FLOW",
+                        "sourceVersion": "2.0"
+                    }
+                }
+            ],
+            "subscriberArn": "arn:aws:securitylake:us-east-1:123456789012:subscriber/e762aabb-ce3d-4585-beab-63474597845d",
+            "subscriberId": "e762aabb-ce3d-4585-beab-63474597845d",
+            "subscriberIdentity": {
+                "externalId": "123456789012",
+                "principal": "029189416600"
+            },
+            "subscriberName": "opensearch-s3",
+            "subscriberStatus": "ACTIVE",
+            "updatedAt": "2024-07-18T01:05:58.393000+00:00"
+        }
+    }
+
+For more information, see `Creating a subscriber with query access <https://docs.aws.amazon.com/security-lake/latest/userguide/subscriber-query-access.html#create-query-subscriber-procedures>`__ in the *Amazon Security Lake User Guide*.

awscli/examples/synthetics/associate-resource.rst

@@ -0,0 +1,11 @@
+**To associate a canary with a group**
+
+The following ``associate-resource`` example associates a canary with a group named ``demo_group``. ::
+
+    aws synthetics associate-resource \
+        --group-identifier demo_group \
+        --resource-arn arn:aws:synthetics:us-east-1:123456789012:canary:demo_canary
+
+This command produces no output.
+
+For more information, see `Synthetic monitoring (canaries) <https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries.html>`__ in the *Amazon CloudWatch User Guide*.

awscli/examples/synthetics/create-canary.rst

@@ -0,0 +1,48 @@
+**To create a canary**
+
+The following ``create-canary`` example creates a canary named ``demo_canary``. ::
+
+    aws synthetics create-canary \
+        --name demo_canary \
+        --code '{"S3Bucket": "artifacts3bucket", "S3Key":"demo_canary.zip", "Handler": "index.lambda_handler"}' \
+        --artifact-s3-location s3://amzn-s3-demo-bucket/demo_canary.zip \
+        --execution-role-arn arn:aws:iam::123456789012:role/demo_canary_role \
+        --schedule Expression="rate(10 minutes)" \
+        --runtime-version syn-nodejs-puppeteer-9.1
+
+Output::
+
+    {
+        "Canary": {
+            "Id": "a1b2c3d4-5678-90ab-cdef-example11111",
+            "Name": "demo_canary",
+            "Code": {
+                "Handler": "index.lambda_handler"
+            },
+            "ExecutionRoleArn": "arn:aws:iam::123456789012:role/demo_canary_role",
+            "Schedule": {
+                "Expression": "rate(10 minutes)",
+                "DurationInSeconds": 0
+            },
+            "RunConfig": {
+                "TimeoutInSeconds": 600,
+                "MemoryInMB": 1000,
+                "ActiveTracing": false
+            },
+            "SuccessRetentionPeriodInDays": 31,
+            "FailureRetentionPeriodInDays": 31,
+            "Status": {
+                "State": "CREATING",
+                "StateReasonCode": "CREATE_PENDING"
+            },
+            "Timeline": {
+                "Created": "2024-10-15T19:03:08.826000+05:30",
+                "LastModified": "2024-10-15T19:03:08.826000+05:30"
+            },
+            "ArtifactS3Location": "amzn-s3-demo-bucket/demo_canary.zip",
+            "RuntimeVersion": "syn-nodejs-puppeteer-9.1",
+            "Tags": {}
+        }
+    }
+
+For more information, see `Synthetic monitoring (canaries) <https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries.html>`__ in the *Amazon CloudWatch User Guide*.

awscli/examples/synthetics/create-group.rst

@@ -0,0 +1,21 @@
+**To create a group**
+
+The following ``create-group`` example creates a group named ``demo_group``. ::
+
+    aws synthetics create-group \
+        --name demo_group
+
+Output::
+
+    {
+        "Group": {
+            "Id": "example123",
+            "Name": "demo_group",
+            "Arn": "arn:aws:synthetics:us-east-1:123456789012:group:example123",
+            "Tags": {},
+            "CreatedTime": "2024-10-15T14:47:23.811000+05:30",
+            "LastModifiedTime": "2024-10-15T14:47:23.811000+05:30"
+        }
+    }
+
+For more information, see `Synthetic monitoring (canaries) <https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries.html>`__ in the *Amazon CloudWatch User Guide*.

awscli/examples/synthetics/delete-canary.rst

@@ -0,0 +1,10 @@
+**To permanently delete a canary**
+
+The following ``delete-canary`` example deletes a canary named ``demo_canary``. ::
+
+    aws synthetics delete-canary \
+        --name demo_canary
+
+This command produces no output.
+
+For more information, see `Synthetic monitoring (canaries) <https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries.html>`__ in the *Amazon CloudWatch User Guide*.

awscli/examples/synthetics/delete-group.rst

@@ -0,0 +1,10 @@
+**To delete a group**
+
+The following ``delete-group`` example deletes a group named ``demo_group``. ::
+
+    aws synthetics delete-group \
+        --group-identifier demo_group
+
+This command produces no output.
+
+For more information, see `Synthetic monitoring (canaries) <https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries.html>`__ in the *Amazon CloudWatch User Guide*.