RMI Services API Key Rotation
As part of security improvement for our services and recommendation from Sec Ops team, we need to rotate the API keys used in RMI services. Furthermore, this exercise needs to be done once every 3 months.
What to do
If you are the owner of these services (you can also refer to this spreadsheet):
econ-hlv-app
nvs-accom-image-classification-svc
nvs-accom-ner-svc
nvs-image-deduplication-svc
nvs-ner-chunking-svc
nvs-par-automation-svc
nvs-us-query-auto-correct
pps
Please help to:
- Check the new API key for staging and production in vault. We store the API keys under
secret/[your-team-name]/api/[your-model-name]/keys
.
- Make sure you can hit your service for both staging and production using the new API key.
- Ask the clients that call your APIs to update the API key to call your services.
- Migrate your services to use Auth0 asap so that you and your client don’t need to do this operation every 3 months
:happy_face:
- Note that if you decided to migrate your service to auth0, there will be a downtime to your service because you need to delete the old deployment before redeploy to use auth0. Please plan accordingly with the clients before doing the migration.
Timeline
- June 10th, 2022: Deletion of old API keys
Support
If you have any questions or need additional support, you can mention @data-mlep in #rm-support.
Thank you
:bows: