s3-credentials
s3-credentials copied to clipboard
simonw
A tool for creating credentials for accessing S3 buckets
Users with multiple AWS accounts can declare [named profiles](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html) to manage the different sets of credentials/regions. It would be ideal if `s3-credentials` accepted a `--profile` argument, just like the `aws`...
I'm not an AWS expert. I would feel a lot more comfortable if some AWS experts could review this tool and make sure that what it is doing makes sense...
I already have `delete-user` - this would be a similar utility but for deleting buckets. Mainly so I don't have to remember how to do it with `awscli`.
Would have been useful here: https://github.com/simonw/s3-credentials/issues/47#issuecomment-1114321878
It's frustrating when using `s3-credentials put-object` that you have to specify the key name each time, rather than deriving that from the filename: s3-credentials put-object simonwillison-cors-allowed-public \ click_default_group-1.2.2-py3-none-any.whl \ /tmp/click-default-group/dist/click_default_group-1.2.2-py3-none-any.whl...
Currently, when issuing create for an existing bucket and user, a new access key and secret key is created for that user and added to the user's set of access...
If a bad or expired session token is set, the create command fails with a misleading error that an existing bucket doesn't exist, if *--create-bucket* isn't specified. If *--create-bucket* **is**...
If you want to access S3 from a Lambda function, AWS recommend you create a dedicated role that the Lambda function can then use. But... you still need to attach...
The new `--prefix` option from #12 lets you set a wildcard prefix for key access - but it strikes me that it would also be useful to be able to...
> Incidentally, trying to call create with the same username 3 times hits the issue you've noted above, that there can only be 2 active access keys: > > ```bash...