Allow S3 operations after bucket creation change #38

New issue

Closed

opened 2024-06-26 08:10:04 +00:00 by alexvanin · 3 comments

alexvanin commented

2024-06-26 08:10:04 +00:00

Owner

After TrueCloudLab/frostfs-s3-gw#407 user won't be able to operate with created bucket, because user (wallet) doesn't have any policies that allow it.

Policies can be set:

with separate makefile target
during init-aio.sh

After https://git.frostfs.info/TrueCloudLab/frostfs-s3-gw/pulls/407 user won't be able to operate with created bucket, because user (wallet) doesn't have any policies that allow it. Policies can be set: * with separate makefile target * during init-aio.sh

alexvanin commented

2024-06-26 08:11:33 +00:00

Author

Owner

@dkirillov can you share some frostfs-cli commands that you've used in dev-env so gateway works?

dkirillov commented

2024-06-26 09:51:35 +00:00

Member

Actually, I've used iam 🙈. But I suppose the following command (from http-gw doc) is kind of analogue:

$ frostfs-cli ape-manager add -r <endpoint> --wallet <wallet> \
  --target-type container --target-name 9dfzyvq82JnFqp5svxcREf2iy6XNuifYcJPusEDnGK9Z \
  --rule "allow Object.* RequestCondition:"\$Actor:publicKey"=03b09baabff3f6107c7e9acb8721a6fc5618d45b50247a314d82e548702cce8cd5 *" \
  --chain-id <chainID>

Actually, I've used iam 🙈. But I suppose the following command (from [http-gw doc](https://git.frostfs.info/TrueCloudLab/frostfs-http-gw/src/branch/master/README.md#example)) is kind of analogue: ``` $ frostfs-cli ape-manager add -r <endpoint> --wallet <wallet> \ --target-type container --target-name 9dfzyvq82JnFqp5svxcREf2iy6XNuifYcJPusEDnGK9Z \ --rule "allow Object.* RequestCondition:"\$Actor:publicKey"=03b09baabff3f6107c7e9acb8721a6fc5618d45b50247a314d82e548702cce8cd5 *" \ --chain-id <chainID> ```

alexvanin commented

2024-07-11 15:16:36 +00:00

Author

Owner

Done in nightly-v1.6 branch and is going to be merged in master