-
Notifications
You must be signed in to change notification settings - Fork 0
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
As a user, I want to store a copy of my archive data in AWS Deep Archive / Glacier #73
Comments
tagup with MCP - we (PDS) will be able to set up glacier ousevles. |
@ramesh-maddegoda At monthly MCP meeting today (7/8/24), we explored the following options instead of using glaciers:
Could you please evaluate these approaches with Nucleus? |
@viviant100 poking at this a bit online, I think what the folks on the MCP call may have been referring to was Cross-Region Replication. We could then:
To kick off this effort, since this does not really need Nucleus in the loop, can you help with a couple sub-tasks:
After that, we can pilot out what it looks like to set something like this up. |
Now, in MCP it takes more than 2 hours sometimes to create MWAA in MCP with Terraform and it fails with the following error.
Created the request https://jaas.gsfc.nasa.gov/servicedesk/customer/portal/2/GSD-3804 to get long term access keys to avoid this problem. |
This ticket was unblocked after finding a solution to #118 |
Created pull request: #119 |
Status: Initially had an issue with pushing to Glacier. Need to set |
We finally want a replication across regions and we do that using a replication rule configured in terraform (as done for the ODR bucket). |
Create a pull request #120 |
The PR is merged and next step is to document the needed configuration, a ticket will be created for that. |
This can be closed. Wrap-up of NASA-PDS/planetary-data-cloud#75 will include the necessary documentation. |
Checked for duplicates
Yes - I've already checked
π§βπ¬ User Persona(s)
Archivist
πͺ Motivation
...so that I can have a copy of my data available in the event of corruption or disaster recovery
π Additional Details
No response
Acceptance Criteria
Given
When I perform
Then I expect
βοΈ Engineering Details
Tightly coupled with cloud requirement: NASA-PDS/planetary-data-cloud#75
The text was updated successfully, but these errors were encountered: