# Uplink CLI generate S3 --writeonly

**URL:** <https://forum.storj.io/t/uplink-cli-generate-s3-writeonly/16170>\
**Category:** troubleshooting\
**Created:** [November 18, 2021, 12:50am UTC](https://forum.storj.io/t/uplink-cli-generate-s3-writeonly/16170 "2021-11-18T00:50:52Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [November 18, 2021, 7:55am UTC](https://forum.storj.io/t/uplink-cli-generate-s3-writeonly/16170/5 "2021-11-18T07:55:32Z")

</div>

You can make a feature request here: [DCS feature requests - voting - Storj Community Forum (official)](https://forum.storj.io/c/ideas-and-suggestions/dcs-feature-requests/36), however the python binding is a third party repo, it depends on their maintainers. So maybe better to make an issue in the [Issues · storj-thirdparty/uplink-python · GitHub](https://github.com/storj-thirdparty/uplink-python/issues)

I would suggest not to use the s3 protocol where possible. It has limitations mentioned here: [Programmatic Granting of new Access keys - #2 by Alexey](https://forum.storj.io/t/programmatic-granting-of-new-access-keys/16069/2)

For grant permissions - you need to specify

```auto
uplink share --readonly=false --writeonly --not-after +1h --register sj://[bucket]/[folder]

```

I know it feels counter-intuitive, so I made an internal ticket a while ago. This problem should be solved in the `uplinkng` tool (it’s expected to be merged to `uplink` when all features will mature), see [[Tech Preview] Uplinkng (new enhanced uplink cli)](https://forum.storj.io/t/tech-preview-uplinkng-new-enhanced-uplink-cli/15876), [Changelog v1.42.4](https://forum.storj.io/t/changelog-v1-42-4/15982), [Release preparation v1.43](https://forum.storj.io/t/release-preparation-v1-43/16114)

The explanation of such a behavior - the `uplink share` command generates read-only grants by default, thus specifying the `--writeonly` option will extends the default `--readonly=true` option with the `--writeonly=true` option, thus by binary logic it results to no permissions at all. So you need to disable the read-only flag and enable write-only flag. Please, note - it will produce:

```auto
=========== ACCESS RESTRICTIONS ==========================================================
Download : Disallowed
Upload : Allowed
Lists : Disallowed
Deletes : Allowed
NotBefore : No restriction
NotAfter : 2021-11-18 12:08:59

```

So, if you want to disable deletes or enable downloads - you need to explicitly specify that.

---

_[View the full topic](https://forum.storj.io/t/uplink-cli-generate-s3-writeonly/16170)._