S3 Credentials Versions Save

A tool for creating credentials for accessing S3 buckets

0.8

2 years ago
  • s3-credentials create my-bucket --public option for creating public buckets, which allow anyone with knowledge of a filename to download that file. This works by attaching this public bucket policy to the bucket after it is created. #42
  • s3-credentials put-object now sets the Content-Type header on the uploaded object. The type is detected based on the filename, or can be specified using the new --content-type option. #43
  • s3-credentials policy my-bucket --public-bucket outputs the public bucket policy that would be attached to a bucket of that name. #44

0.7

2 years ago
  • s3-credentials policy command, to output the JSON policy that would be used directly to the terminal. #37
  • README now includes examples of the three different policies. #36
  • s3-credentials put-object and s3-credentials get-object commands for uploading and downloading files from an S3 bucket. #38

0.6

2 years ago
  • create --dry-run option outputs a summary of changes that would be made to an AWS account without applying them. #35
  • s3-credentials whoami command now uses sts.GetCallerIdentity, which means it works with any kind of access key. #33

0.5

2 years ago
  • 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
  • Redesigned read-only and read-write policies to no longer use wildcards and instead explicitly list allowed actions. #15
  • Commands now accept an optional --auth file/path.json option to specify a JSON or INI file containing the credentials to use. #29
  • New s3-credentials list-buckets --details option to include ACLs, website configuration and bucket policies. #22
  • New s3-credentials create --format ini option for outputting INI format instead of JSON. #17
  • Now uses botocore.stub in some of the tests - thanks, Niko Abeler. #16
  • Added integration tests, run using pytest --integration, which exercise the tool against an AWS account and delete any created resources afterwards. #30
  • Added tips section to the README, including how to access CloudTrail

0.4

2 years ago
  • 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

2 years ago
  • s3-credentials delete-user command for deleting a user along with all of their access keys and inline policies. #10

0.2

2 years ago
  • New s3-credentials list-buckets command. #9
  • Added section to the documentation about configuring the tool.

0.1

2 years ago
  • 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
  • s3-credentials list-users lists all of the users for the current AWS account. #4
  • s3-credentials list-user-policies lists inline policies for the specifeid users, or all users. #5
  • s3-credentials whoami shows information about the currently authenticated user.