updated documenation regarding multiple bucket access

[ilich]

Issue #, if available:
The documentation does not mention that it is possible to provide access to multiple buckets

Description of changes:

• Added the note about multiple bucket access
• Added note regarding S3 bucket resource policy

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[simonkrol]

Hi @ilich,

That seems reasonable to me, I'll add a task to have this included in an upcoming release. While you won't see this PR get merged due to our internal policy, once the changes have been released, you'll see the PR get closed and a link to this PR and your Github profile included in the External Contributors section at the bottom of the readme.

Thanks for your contributions to SIH,
Simon

[ilich]

Hi Simon,

Thank you for the update and for the useful architecture pattern.

[simonkrol]

Hi @ilich,

I'm working on including this internally for an upcoming release, but wanted to get a few more details from you.

When you updated the source buckets, and had to manually update the role, were you changing things through the Lambda environment variables? If so, if you update that value through the template parameters(by updating the stack with the same template), does the role get updated properly?

Thanks,
Simon

[ilich]

The comma-separated list of buckets works well. The policy created by the CDK scripts handled all of them.

The resource policy is an existing policy we had. It was created manually, and I had to update it manually as well. I added that note more for debugging purposes because the original error we had in runtime was a bit misleading