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

Rotate NewRelic license key and document steps in the wiki #5043

Closed
2 of 3 tasks
FuhuXia opened this issue Jan 17, 2025 · 3 comments
Closed
2 of 3 tasks

Rotate NewRelic license key and document steps in the wiki #5043

FuhuXia opened this issue Jan 17, 2025 · 3 comments
Assignees
Labels
bug Software defect or bug

Comments

@FuhuXia
Copy link
Member

FuhuXia commented Jan 17, 2025

To maintain security, we should rotate NewRelic API keys every a few months. We also received emails from newrelic.com requesting key rotation.

  • Rotate NewRelic API keys by March 1, 2025
  • Document steps in Wiki
  • Set schedule to repeat every 90 days.

Last time it was rotated in 2024-01-08 by ticket #4580

@FuhuXia FuhuXia added the bug Software defect or bug label Jan 17, 2025
@Bagesary Bagesary moved this to 📟 Sprint Backlog [7] in data.gov team board Jan 23, 2025
@Jin-Sun-tts Jin-Sun-tts self-assigned this Feb 5, 2025
@Jin-Sun-tts Jin-Sun-tts moved this from 📟 Sprint Backlog [7] to 🏗 In Progress [8] in data.gov team board Feb 5, 2025
@Jin-Sun-tts
Copy link
Contributor

The old key named "cloud.gov app log" will be deleted, and a new key will be created and reset across all spaces.

For key rotation, refer to New Relic API Key Rotation.

There are two app environment variables related to this key:

NEW_RELIC_LICENSE_KEY is set in inventory-secrets and catalog-secrets for production, staging, and development spaces.
NEWRELIC_LICENSE_KEY is set in logstack-shipper environment variables in the three management spaces.

@Jin-Sun-tts
Copy link
Contributor

Jin-Sun-tts commented Feb 10, 2025

In the development enviornment, NEW_RELIC_LICENSE_KEY also in the user-provided configurations for datagov-harvest-secrets and catalog-next-secrets

Use cf uups to update secrets in regular spaces and cf set-env to update them in management spaces

Restart each app in the development environment after an update. GitHub triggers regular restarts in staging and production.

@Jin-Sun-tts
Copy link
Contributor

Jin-Sun-tts commented Feb 11, 2025

Updated the New Relic license key across all environments.

Documented the process in the wiki: How to Rotate New Relic License Key

Created a ticket for the next key rotation: #5082

@Jin-Sun-tts Jin-Sun-tts moved this from 🏗 In Progress [8] to 👀 Needs Review [2] in data.gov team board Feb 11, 2025
@Jin-Sun-tts Jin-Sun-tts moved this from 👀 Needs Review [2] to ✔ Done in data.gov team board Feb 12, 2025
@Jin-Sun-tts Jin-Sun-tts closed this as completed by moving to ✔ Done in data.gov team board Feb 12, 2025
@hkdctol hkdctol moved this from ✔ Done to 🗄 Closed in data.gov team board Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Software defect or bug
Projects
Archived in project
Development

No branches or pull requests

2 participants