diff --git a/awscli/examples/s3api/put-bucket-acl.rst b/awscli/examples/s3api/put-bucket-acl.rst index 42418a8160aa..91a1ed127336 100644 --- a/awscli/examples/s3api/put-bucket-acl.rst +++ b/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). diff --git a/awscli/examples/s3api/put-bucket-cors.rst b/awscli/examples/s3api/put-bucket-cors.rst index 83494f3c058c..65be5da0b721 100644 --- a/awscli/examples/s3api/put-bucket-cors.rst +++ b/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: { diff --git a/awscli/examples/s3api/put-bucket-logging.rst b/awscli/examples/s3api/put-bucket-logging.rst index 8c1242943989..17beeef1226e 100644 --- a/awscli/examples/s3api/put-bucket-logging.rst +++ b/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