Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make random_password.referer available as an output #224

Open
Speculor opened this issue Mar 16, 2022 · 1 comment
Open

Make random_password.referer available as an output #224

Speculor opened this issue Mar 16, 2022 · 1 comment

Comments

@Speculor
Copy link

Describe the Feature

I would like the random_password.referer generated for the s3 website password policy to be available as an output.

Expected Behavior

random_password.referer is available as a module output

Use Case

This is needed so that it can be used in policy documents for additional buckets. In our case, we have the origin bucket generated by the module in which our static website files (ie index.html) are placed, and we also have an assets bucket in which media files (jpg's etc) are stored. I would like to be able to add the same security policy that the origin bucket has to this assets bucket.

Describe Ideal Solution

random_password.referer is available as an output so that it can be used in subsequent bucket policies

Alternatives Considered

Only alternative I can see is manually getting the value from the origin bucket policy first and then adding it as a string to subsequent bucket policies, which is bad all around.

@Speculor
Copy link
Author

Quick side-note, as our assets bucket was not a static website enabled bucket I was able to use the CloudFront Origin Identity to limit access to it but I believe in other cases (other bucket might be a static website enabled bucket) the point still remains, we need the random password generated to be available as a module output

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant