Open karkir0003 opened 7 months ago
Hello @karkir0003! Thank you for submitting the Feature Request Form. We appreciate your contribution. :wave:
We will look into it and provide a response as soon as possible.
To work on this feature request, you can follow these branch setup instructions:
Checkout the main branch:
git checkout nextjs
Pull the latest changes from the remote main branch:
git pull origin nextjs
Create a new branch specific to this feature request using the issue number:
git checkout -b feature-1131
Feel free to make the necessary changes in this branch and submit a pull request when you're ready.
Best regards, Deep Learning Playground (DLP) Team
Feature Name
Migrate DLP S3 Buckets to us-east-1
Your Name
Karthik Subramanian
Description
Problem Our DLP S3 Buckets are currently in
us-west-2
region. Due to an initiative to migrate our AWS resources tous-east-1
to keep our resources closer to where we are, we need to do some work in migrating the S3 buckets tous-east-1
.Proposed Approach The following S3 buckets are currently used in DLP:
dlp-executions-bucket
stored inus-west-2
. Rename todlp-trainspace-bucket
and store inus-east-1
. This bucket stores the trainspace data by trainspace id. It's very important to make the "Buckets and Objects not public" condition hold. We wouldn't want to expose the trainspace data to a malicious actordlp-upload-bucket
that was stored inus-west-2
tous-east-1
. This bucket holds the uploaded datasets from the user. Please make sure that access settings and CORS settings are properly configured just like the one inus-west-2
dlp-executions-bucket
and ensure that we are writing trainspace data todlp-trainspace-bucket
dlp-upload-bucket
still works as intended