Introduction

This directory contains examples on how to use AWS CLI/boto3 to exercise the RadosGW extensions to the S3 API. This is an extension to the AWS SDK.

Users

For the standard client to support these extensions, the service-2.sdk-extras.json file should be added. You can place it under the default folder ~/.aws/models/s3/2006-03-01/ or create a custom one /path/to/custom/folder/models/s3/2006-03-01/ and add it to AWS_DATA_PATH environment variable. For more information see here.

Python

The boto3 client could be used with the extensions, code samples exists in this directory.

AWS CLI

The standard AWS CLI may also be used with these extensions. For example:

Unordered listing:

aws --endpoint-url http://localhost:8000 s3api list-objects --bucket=mybucket --allow-unordered

Unordered listing (version 2):

aws --endpoint-url http://localhost:8000 s3api list-objects-v2 --bucket=mybucket --allow-unordered

Topic creation with endpoint:

aws --endpoint-url http://localhost:8000 sns create-topic --name=mytopic --attributes='{"push-endpoint": "amqp://localhost:5672", "amqp-exchange": "ex1", "amqp-ack-level": "broker"}'

Expected output:

{
    "TopicArn": "arn:aws:sns:default::mytopic"
}

Get topic attributes:

aws --endpoint-url http://localhost:8000 sns get-topic-attributes --topic-arn="arn:aws:sns:default::mytopic"

Expected output:

{
  "Attributes": {
    "User": "",
    "Name": "mytopic",
    "EndPoint": "{\"EndpointAddress\":\"amqp://localhost:5672\",\"EndpointArgs\":\"Attributes.entry.1.key=push-endpoint&Attributes.entry.1.value=amqp://localhost:5672&Attributes.entry.2.key=amqp-exchange&Attributes.entry.2.value=ex1&Attributes.entry.3.key=amqp-ack-level&Attributes.entry.3.value=broker&Version=2010-03-31&amqp-ack-level=broker&amqp-exchange=ex1&push-endpoint=amqp://localhost:5672\",\"EndpointTopic\":\"mytopic\",\"HasStoredSecret\":\"false\",\"Persistent\":\"false\"}",
    "TopicArn": "arn:aws:sns:default::mytopic",
    "OpaqueData": ""
  }
}

Bucket notifications with filtering extensions (bucket must exist before calling this command):

aws --region=default --endpoint-url http://localhost:8000 s3api put-bucket-notification-configuration --bucket=mybucket --notification-configuration='{"TopicConfigurations": [{"Id": "notif1", "TopicArn": "arn:aws:sns:default::mytopic", "Events": ["s3:ObjectCreated:*", "s3:ObjectRemoved:*"], "Filter": {"Metadata": {"FilterRules": [{"Name": "x-amz-meta-foo", "Value": "bar"}, {"Name": "x-amz-meta-hello", "Value": "world"}]}, "Key": {"FilterRules": [{"Name": "regex", "Value": "([a-z]+)"}]}}}]}'

Get configuration of a specific notification of a bucket:

aws --endpoint-url http://localhost:8000 s3api get-bucket-notification-configuration --bucket=mybucket --notification=notif1

Expected output:

{
  "TopicConfigurations": [
    {
      "Id": "notif1",
      "TopicArn": "arn:aws:sns:default::mytopic",
      "Events": [
        "s3:ObjectCreated:*",
        "s3:ObjectRemoved:*"
      ],
      "Filter": {
        "Key": {
          "FilterRules": [
            {
              "Name": "regex",
              "Value": "([a-z]+)"
            }
          ]
        },
        "Metadata": {
          "FilterRules": [
            {
              "Name": "x-amz-meta-foo",
              "Value": "bar"
            },
            {
              "Name": "x-amz-meta-hello",
              "Value": "world"
            }
          ]
        }
      }
    }
  ]
}

Developers

Anyone developing an extension to the S3 API supported by AWS, please modify service-2.sdk-extras.json (all extensions should go into the same file), so that boto3 could be used to test the new API. In addition, python files with code samples should be added to this directory demonstrating use of the new API. When testing you changes please:

make sure that the modified file is in the boto3 path as explained above
make sure that the standard S3 tests suit is not broken, even with the extensions files in the path