226: Add Expected Bucket Owner

[houserx-ioannis]

what

This PR addresses #226 about not being able to specify expected bucket owner in various S3 resources.

why

From AWS docs:

Because Amazon S3 identifies buckets based on their names, an application that uses an incorrect bucket name in a request could inadvertently perform operations against a different bucket than expected. To help avoid unintentional bucket interactions in situations like this, you can use bucket owner condition. Bucket owner condition enables you to verify that the target bucket is owned by the expected AWS account, providing an additional layer of assurance that your S3 operations are having the effects you intend.

references

• Closes Enhancement: include expected_bucket_owner #226

[Gowiem]

Generally looking good! Unfortunately, we need to run some automation to pass our tests. Mind making the suggested change and doing the following locally, adding + committing the result, and pushing to your branch?

make init
make readme

Thanks!

[houserx-jmcc]

Generally looking good! Unfortunately, we need to run some automation to pass our tests. Mind making the suggested change and doing the following locally, adding + committing the result, and pushing to your branch?

make init
make readme

Thanks!

@Gowiem I pushed a commit with these updates, thank you!

[Gowiem]

/terratest

[Gowiem]

[mergify]

Important

Cloud Posse Engineering Team Review Required

This pull request modifies files that require Cloud Posse's review. Please be patient, and a core maintainer will review your changes.

To expedite this process, reach out to us on Slack in the #pr-reviews channel.

[github-actions]

These changes were released in v4.4.0.