Secure Secrets Management
Learn best practices for securely handling API keys, tokens, and other sensitive information in edge environments.
Secure Secrets Management is a free Edge Computing with Cloudflare Workers & Deno lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Edge Computing with Cloudflare Workers & Deno learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
What Are Edge Secrets?
When building applications, especially at the edge, you often need to handle sensitive information. These are called secrets.
Secrets include things like API keys, database credentials, authentication tokens, and private encryption keys. They are critical for your application's security and functionality.
Dangers of Hardcoding Secrets
A common mistake, especially for beginners, is to hardcode secrets directly into your application's source code.
- Exposure: Anyone with access to your code (e.g., in a public Git repository) can see your secrets.
- Rotation Issues: Changing a secret means changing and redeploying your code everywhere it's used.
- Security Breach: A single leak can compromise your entire system.
Cloudflare Worker Environment Variables
Cloudflare Workers provide a secure way to manage secrets using environment variables. These variables are:
- Injected securely at runtime, not stored in your code.
- Encrypted at rest by Cloudflare.
- Specific to each Worker, allowing fine-grained control.
They are accessed via the env object in your Worker's fetch handler.
Accessing Worker Secrets Demo
This Worker accesses an environment variable named MY_API_KEY. Notice how the secret itself is never hardcoded in the script.
Try running it! (The actual key won't be shown for security).
export default {
async fetch(request, env, ctx) {
const apiKey = env.MY_API_KEY; // Access the secret
if (apiKey) {
return new Response(`Secret accessed! Length: ${apiKey.length}`);
} else {
return new Response(
"MY_API_KEY environment variable not set.",
{ status: 400 }
);
}
},
};Deno Environment Variables
Similar to Workers, Deno applications also use environment variables for secrets. You can access them using Deno.env.
For local development, you might use .env files (though not directly supported by Deno, tools like deno task or third-party modules can help). For Deno Deploy, secrets are configured securely through their platform UI or CLI.
Using Deno Secrets Demo
Here's a simple Deno script that retrieves a secret named DB_PASSWORD from its environment variables. Run this example to see it in action.
const dbPassword = Deno.env.get("DB_PASSWORD");
if (dbPassword) {
console.log(`Database password accessed. Length: ${dbPassword.length}`);
} else {
console.log("DB_PASSWORD environment variable not set.");
console.log("To set: env DB_PASSWORD='mysecret' deno run --allow-env main.ts");
}Managing Secrets with Wrangler CLI
For Cloudflare Workers, the Wrangler CLI is your go-to tool for managing secrets. It encrypts and securely uploads them to Cloudflare's infrastructure.
wrangler secret put <NAME>: Prompts for a secret value and uploads it.wrangler secret delete <NAME>: Removes a secret.wrangler secret list: Lists all secrets for your Worker.
This keeps secrets out of your wrangler.toml file and source code.
Principle of Least Privilege
A crucial security principle is the Principle of Least Privilege. This means:
- Granting only the minimum necessary permissions to access resources.
- Only giving access to secrets to the specific services or users that absolutely need them.
Avoid giving a Worker access to a secret it doesn't actually use, even if it seems convenient.
Secret Rotation and Auditing
Even with secure storage, secrets can be compromised. Implement these practices:
- Secret Rotation: Regularly change your API keys and tokens (e.g., every 90 days). This limits the window of opportunity for attackers if a secret is leaked.
- Auditing: Monitor and log access to your secrets. This helps detect unusual activity and potential breaches.
Automate these processes where possible to reduce manual overhead.
Secrets Management Check
Test your understanding of secure secrets management.
Recap: Secure Secrets
In this lesson, we learned about the importance of securely managing sensitive information in edge applications.
- Never hardcode secrets.
- Utilize platform-provided environment variables (Cloudflare Workers
env, DenoDeno.env). - Use tools like Wrangler CLI for secure secret deployment.
- Follow the Principle of Least Privilege.
- Implement regular secret rotation and auditing.
These practices are fundamental to building robust and secure edge applications.
Frequently asked questions
Is the “Secure Secrets Management” lesson free?
Yes — the full text of “Secure Secrets Management” is free to read here on the web, and the Edge Computing with Cloudflare Workers & Deno course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Edge Computing with Cloudflare Workers & Deno course, upgrade to CoddyKit PRO.
What will I learn in “Secure Secrets Management”?
Learn best practices for securely handling API keys, tokens, and other sensitive information in edge environments. You practise Edge Computing with Cloudflare Workers & Deno with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Edge Computing with Cloudflare Workers & Deno?
No prior experience is required. Edge Computing with Cloudflare Workers & Deno on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Secure Secrets Management” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Edge Computing with Cloudflare Workers & Deno lesson?
Yes. Every Edge Computing with Cloudflare Workers & Deno lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.