Secrets on the Build Your Own AI Platform track. Provider keys and database passwords live in a secret store. Jobs receive them at runtime. They are not in the git repo or the image.
This lesson assumes you already worked through Human review.
The idea in practice
Rotate keys. Scope them. Alert on a key used from an unexpected place.
A concrete check
goal = {
'track': 'Build Your Own AI Platform',
'lesson': 'Secrets',
}
checks = [
'input available at decision time',
'score matches the real decision',
'failure case written down',
]
print(goal['lesson'])
for item in checks:
print('-', item)
Run the sketch locally if you have Python. The printout is a reminder of the checks, not a trained model. Replace the strings with the real inputs from your own example before you treat it as a design.
What usually goes wrong
A key in a notebook committed once. When this happens, stop adding parameters or tools. Fix the check, the data, or the permission, then run the same example again.
What to write down
- The input you are allowed to use at decision time.
- The output and the score or pass rule.
- One failure you will test on purpose.
- What you will not claim the system can do.
Practice
Say where a training job should read a key from.
Self-check
- Say Secrets in one sentence that mentions an input and an output.
- Name the failure mode in this lesson and the check that would catch it.
Done when: you can explain this lesson without the page open, and you have a written failure case.