releases: 73374797
This data as json
| html_url | id | author | node_id | tag_name | target_commitish | name | draft | prerelease | created_at | published_at | body | repo | reactions | mentions_count |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/simonw/s3-credentials/releases/tag/0.12.1 | 73374797 | 9599 | RE_kwDOGUV9is4EX5xN | 0.12.1 | main | 0.12.1 | 0 | 0 | 2022-08-01T19:45:53Z | 2022-08-01T19:50:53Z | - Using the `--policy` or `--statement` options now implies `--user-permissions-boundary=none`. Previously it was easy to use these options to accidentally create credentials that did not work as expected since they would have a default permissions boundary that locked them down to only being able to access S3. [#74](https://github.com/simonw/s3-credentials/issues/74) - The `s3-credentials.AmazonS3FullAccess` role created by this tool in order to issue temporary credentials previously used the default `MaxSessionDuration` value of 3600, preventing it from creating credentials that could last more than an hour. This has been increased to 12 hours. See [this issue comment](https://github.com/simonw/s3-credentials/issues/75#issuecomment-1201643771) for instructions on fixing your existing role if this bug is affecting your account. [#75](https://github.com/simonw/s3-credentials/issues/75) | 423984522 |
Links from other tables
- 0 rows from release in assets