ceph/s3-tests is one of the open-source repositories TopGit tracks, currently at 373 stars, written primarily in Python. Compatibility tests for S3 clones
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
These tests have moved into the https://github.com/ceph/ceph repository and will no longer be maintained here.
========================
S3 compatibility tests
This is a set of unofficial Amazon AWS S3 compatibility
tests, that can be useful to people implementing software
that exposes an S3-like API. The tests use the Boto2 and Boto3 libraries.
The tests use the Tox tool. To get started, ensure you have the tox
software installed; e.g. on Debian/Ubuntu::
sudo apt-get install tox
You will need to create a configuration file with the location of the
service and two different credentials. A sample configuration file named
s3tests.conf.SAMPLE has been provided in this repo. This file can be
used to run the s3 tests on a Ceph cluster started with vstart.
Once you have that file copied and edited, you can run the tests with::
Some tests have attributes set based on their current reliability and
things like AWS not enforcing their spec stricly. You can filter tests
based on their attributes::
S3TEST_CONF=aws.conf tox -- -m 'not fails_on_aws'
Most of the tests have both Boto3 and Boto2 versions. Tests written in
Boto2 are in the s3tests directory. Tests written in Boto3 are
located in the s3test_boto3 directory.
You can run only the boto3 tests with::
S3TEST_CONF=your.conf tox -- s3tests/functional
========================
STS compatibility tests
This section contains some basic tests for the AssumeRole, GetSessionToken and AssumeRoleWithWebIdentity API's. The test file is located under s3tests/functional.
To run the STS tests, the vstart cluster should be started with the following parameter (in addition to any parameters already used with it)::
You can filter tests based on the attributes. There is a attribute named test_of_sts to run AssumeRole and GetSessionToken tests and webidentity_test to run the AssumeRoleWithWebIdentity tests. If you want to execute only test_of_sts tests you can apply that filter as below::
For running webidentity_test you'll need have Keycloak running.
In order to run any STS test you'll need to add "iam" section to the config file. For further reference on how your config file should look check s3tests.conf.SAMPLE.
========================
IAM policy tests
This is a set of IAM policy tests.
This section covers tests for user policies such as Put, Get, List, Delete, user policies with s3 actions, conflicting user policies etc
These tests uses Boto3 libraries. Tests are written in the s3test_boto3 directory.
These iam policy tests uses two users with profile name "iam" and "s3 alt" as mentioned in s3tests.conf.SAMPLE.
If Ceph cluster is started with vstart, then above two users will get created as part of vstart with same access key, secrete key etc as mentioned in s3tests.conf.SAMPLE.
Out of those two users, "iam" user is with capabilities --caps=user-policy=* and "s3 alt" user is without capabilities.
Adding above capabilities to "iam" user is also taken care by vstart (If Ceph cluster is started with vstart).
To run these tests, create configuration file with section "iam" and "s3 alt" refer s3tests.conf.SAMPLE.
Once you have that configuration file copied and edited, you can run all the tests with::
Ceph has extensions for the bucket logging S3 API. For the tests to cover these extensions, the following file: examples/rgw/boto3/service-2.sdk-extras.json from the Ceph repo,
should be copied to the: ~/.aws/models/s3/2006-03-01/ directory on the machine where the tests are run.
If the file is not present, the tests will still run, but the extension tests will be skipped. In this case, the bucket logging object roll time must be decreased manually from its default of
300 seconds to 5 seconds::
TopGit's last sync did not record any GitHub topics for ceph/s3-tests. GitHub topics appear in the right sidebar of a repository page; that's the authoritative place to check.
How active is development on ceph/s3-tests?
The most recent commit recorded on ceph/s3-tests was 1 month ago, based on the GitHub push timestamp. The repository has 331 forks — one of the better signals of community interest.
How many stars does ceph/s3-tests have?
ceph/s3-tests has 373 GitHub stars — refresh the page for the live number, or check github.com/ceph/s3-tests. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What language is ceph/s3-tests written in?
ceph/s3-tests is written primarily in Python. GitHub's language field is based on the largest share of bytes in the default branch.
Where do I read more about ceph/s3-tests?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/ceph/s3-tests is the definitive source.
Read full README in the tab above.
Still deciding about s3-tests?
One click hands the question to an AI along with this page — see what it says about s3-tests.