S3-credentials

Latest version: v0.16.1

Safety actively analyzes 642295 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

0.6

- `create --dry-run` option outputs a summary of changes that would be made to an AWS account without applying them. [35](https://github.com/simonw/s3-credentials/issues/35)
- `s3-credentials whoami` command now uses `sts.GetCallerIdentity`, which means it works with any kind of access key. [33](https://github.com/simonw/s3-credentials/issues/33)

0.5

- New `s3-credentials create --duration 20m` option. This creates temporary credentials that only last for the specified time, by creating a role and using `STS.AssignRole()` to retrieve credentials. [27](https://github.com/simonw/s3-credentials/issues/27)
- Redesigned read-only and read-write policies to no longer use wildcards and instead explicitly list allowed actions. [15](https://github.com/simonw/s3-credentials/issues/15)
- Commands now accept an optional `--auth file/path.json` option to specify a JSON or INI file containing the credentials to use. [29](https://github.com/simonw/s3-credentials/issues/29)
- New `s3-credentials list-buckets --details` option to include ACLs, website configuration and bucket policies. [22](https://github.com/simonw/s3-credentials/issues/22)
- New `s3-credentials create --format ini` option for outputting INI format instead of JSON. [17](https://github.com/simonw/s3-credentials/issues/17)
- Now uses `botocore.stub` in some of the tests - thanks, Niko Abeler. [16](https://github.com/simonw/s3-credentials/pull/16)
- Added integration tests, run using `pytest --integration`, which exercise the tool against an AWS account and delete any created resources afterwards. [30](https://github.com/simonw/s3-credentials/issues/30)
- Added tips section to the README, including how to access CloudTrail

0.4

- New options for authenticating with AWS: `--access-key`, `--secret-key`, `--session-token`, `--endpoint-url`. 2
- Various improvements to JSON policies - thanks, jdub! 11
- `--policy filename.json` option for specifying a custom JSON policy. 14

0.3

- `s3-credentials delete-user` command for deleting a user along with all of their access keys and inline policies. [10](https://github.com/simonw/s3-credentials/issues/10)

0.2

- New `s3-credentials list-buckets` command. [9](https://github.com/simonw/s3-credentials/issues/9)
- Added section to the documentation about configuring the tool.

0.1

- Initial release
- `s3-credentials create name-of-bucket` creates a new user with read-write access only to the specified S3 bucket, creates an access key for that user and outputs it to the console. [3](https://github.com/simonw/s3-credentials/issues/3)
- `s3-credentials list-users` lists all of the users for the current AWS account. [4](https://github.com/simonw/s3-credentials/issues/4)
- `s3-credentials list-user-policies` lists inline policies for the specifeid users, or all users. [5](https://github.com/simonw/s3-credentials/issues/5)
- `s3-credentials whoami` shows information about the currently authenticated user.

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.