You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 intendedThe text was updated successfully, but these errors were encountered: