From 3333e8313907ebf38161cec20422dad334722fbd Mon Sep 17 00:00:00 2001 From: Khalim Conn-Kowlessar Date: Wed, 4 Oct 2023 16:08:43 +0100 Subject: [PATCH] trigger redeploy --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 48ec64a1..c933b0ed 100644 --- a/README.md +++ b/README.md @@ -119,3 +119,5 @@ In our terraform stack, we have a module called `s3_presignable_bucket` which co We will generate a pre-signed url and then make a post request to that endpoint to store that data to s3. Part of that process is the creation of an AWS IAM role which contains the permission set to access the bucket, `rerofit-plan-inputs-`. The name of this IAM role is `s3_presign_role_` and for our NextJS application, as it's hosted outside of AWS (for the moment), we need to generate a set of access credentials to give the application access to this bucket. The access key and secret key are automatically generated and stored in AWS secrets manager under `dev/presign_frontend/access_key` and `dev/presign_frontend/secret_key` and need to be set in the environment for the pre-sign api to store csv data to aws. + +# Due Considerations