docs: add missing S3 permissions

[lzap]

I was testing this on a newly created account and two permissions were missing.

[achilleas-k]

Thanks!

[lzap]

I am adding resource to be aligned with the linked doc.

[achilleas-k]

Thanks again!

[lzap]

DO NOT MERGE SORRY

==> osbuild-temp.amazon-ebs.centos9: 2025/01/14 17:37:44 error: cannot upload AMI: AccessDenied: User: arn:aws:iam::399777895069:user/lzap-packer is not authorized to perform: s3:DeleteObject on resource: "arn:aws:s3:::lzap-packer/9943c33b-5a14-4e18-bcb8-d3024b56fcfe-disk.raw" because no identity-based policy allows the s3:DeleteObject action

Looks like one is missing. Drafting now.

[lzap]

Now it works.

[lzap]

Forgot to push the last permission yesterday's evening. OMG what a pain, now I swear it works :-D

[achilleas-k]

I saw the word demo in the resource names and had to look up how they're used exactly. We should mention in the text above that amzn-s3-demo-import-bucket and amzn-s3-demo-export-bucket are example names. They are, right?

It should also be enough to just have one, maybe? Or change the name to reflect our use case as a slightly more concrete example. Like bib-ec2-image-upload-bucket-example or something.

Or am I wrong about what this all means?

[lzap]

This is really the bucket name in ARN format, I was trying to match what is documented in the linked AWS doc rather than this README. I can change if you insist, I take it since this is part of the documentation it should be more clear to a user who is copy-pasting these blocks into AWS UI that they should replace this one as well.