-
Notifications
You must be signed in to change notification settings - Fork 2
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
Deploy Multi-tenant Registry to production and sync data #271
Comments
Status: Working with SAs for syncing the data to prod |
Some issues with bigger index. |
Based on the last discussion with @tloubrieu-jpl and @alexdunnjpl we need a python script that will compared the 3 registries that are missing certain documents and import them over in MCP from JPL AWS. rms-registry : 21 |
@sjoshi-jpl keeps working on the ECS components. I will create a new ticket for @alexdunnjpl to work on the missing documents. |
@alexdunnjpl has made the migration of the remaining documents to the production Opensearch serverless. |
@sjoshi-jpl works on the infrastructure for authentication. After meeting the lambda authorizers are going to be simplified. |
Merging the lambda; next is IAM roles and Cognito |
Status: Working on getting identity pools/user pools deployed to production |
This is done. In production. |
Thanks @tloubrieu-jpl @sjoshi-jpl @jordanpadams! 🎉 (And yes, the SAs too 😁) |
💡 Description
⚔️ Parent Epic / Related Tickets
No response
The text was updated successfully, but these errors were encountered: