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

[FEATURE]: Migrate DLP S3 buckets to us-east-1 #1131

Open
Tracked by #1017
karkir0003 opened this issue Feb 9, 2024 · 2 comments
Open
Tracked by #1017

[FEATURE]: Migrate DLP S3 buckets to us-east-1 #1131

karkir0003 opened this issue Feb 9, 2024 · 2 comments
Labels
code cleanup Cleaning up the code

Comments

@karkir0003
Copy link
Member

karkir0003 commented Feb 9, 2024

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 to us-east-1 to keep our resources closer to where we are, we need to do some work in migrating the S3 buckets to us-east-1.

Proposed Approach
The following S3 buckets are currently used in DLP:

  • Remove the dlp-executions-bucket stored in us-west-2. Rename to dlp-trainspace-bucket and store in us-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 actor
  • Move the dlp-upload-bucket that was stored in us-west-2 to us-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 in us-west-2
  • Clean up any code that uses the dlp-executions-bucket and ensure that we are writing trainspace data to dlp-trainspace-bucket
  • We also might want to ensure that any code that writes uploaded file data to the dlp-upload-bucket still works as intended
@karkir0003 karkir0003 added the enhancement New feature or request label Feb 9, 2024
@karkir0003 karkir0003 moved this from Backlog to Todo in DLP Project Board Feb 9, 2024
@karkir0003 karkir0003 added code cleanup Cleaning up the code and removed enhancement New feature or request labels Feb 9, 2024
Copy link
Contributor

github-actions bot commented Feb 9, 2024

Hello @karkir0003! Thank you for submitting the Feature Request Form. We appreciate your contribution. 👋

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:

  1. Checkout the main branch:
```
 git checkout nextjs
```
  1. Pull the latest changes from the remote main branch:
```
 git pull origin nextjs
```
  1. 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

@karkir0003
Copy link
Member Author

@noah-iversen do you by any chance know if this is done?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code cleanup Cleaning up the code
Projects
Status: Todo
Development

No branches or pull requests

1 participant