Skip to main content
Free Tool

Secret Name Validator

Check if your secret name is valid for Azure Key Vault or AWS Secrets Manager before you create it. Get instant feedback on naming rules and restrictions.

0 / 127

Allowed Characters

Letters (a-z, A-Z), numbers (0-9), hyphens (-)

Type a secret name to validate

Naming Rules Reference

Azure Key Vault

  • 1–127 characters long
  • Must start with a letter
  • Letters (a-z, A-Z), numbers (0-9), hyphens (-)
  • Cannot start or end with a hyphen
  • Case-insensitive (MySecret = mysecret)

AWS Secrets Manager

  • 1–512 characters long
  • Letters, numbers, and: / _ + = . @ ! -
  • Names starting with "aws/" or "aws:" are reserved
  • Case-sensitive (MySecret ≠ mysecret)
  • Use / for hierarchical naming (e.g. prod/db/password)

Related Tools

Secret Naming Best Practices

Why Secret Naming Conventions Matter

A consistent naming convention makes secrets easier to find, audit, and manage at scale. When your team manages hundreds of secrets across Azure Key Vault and AWS Secrets Manager, a clear naming pattern saves hours of troubleshooting and prevents costly mistakes.

Invalid secret names cause deployment failures that are hard to debug. This secret name validator catches issues before they reach your pipeline.

Recommended Naming Patterns

Pattern Example (Azure) Example (AWS)
environment-service-keyprod-api-db-passwordprod/api/db-password
service-component-typeauth-jwt-signing-keyauth/jwt/signing-key
team-project-secretplatform-gateway-api-keyplatform/gateway/api-key

Azure Key Vault uses hyphens for hierarchy since slashes are not allowed. AWS Secrets Manager supports slashes for folder-like organization.

Azure vs AWS: Key Differences

  • Azure is more restrictive: only alphanumeric and hyphens, max 127 characters, must start with a letter. Case-insensitive.
  • AWS is more flexible: supports slashes, dots, underscores, up to 512 characters. Case-sensitive. Supports hierarchical paths like prod/db/password.
  • If you use both providers, choose a naming pattern that works for Azure's stricter rules (hyphens only, no slashes) to stay compatible across both.

For a full comparison, see our Azure vs AWS Secrets Manager comparison.

Skip the Portal, Manage Secrets Faster

SatisVault validates secret names automatically and lets you create, read, update, and delete secrets right from your browser.

Frequently Asked Questions

What are Azure Key Vault secret name rules?

Azure Key Vault secret names must be 1–127 characters long, start with a letter, and contain only letters (a-z, A-Z), numbers (0-9), and hyphens (-). They cannot start or end with a hyphen. Names are case-insensitive.

What are AWS Secrets Manager naming conventions?

AWS Secrets Manager secret names can be up to 512 characters long and may contain letters, numbers, and the following characters: /_+=.@!-. Names starting with "aws/" or "aws:" are reserved by AWS. Names are case-sensitive.

Can I use special characters in secret names?

Azure Key Vault only allows hyphens (-) besides alphanumeric characters. AWS Secrets Manager is more flexible, allowing: /_+=.@!- in addition to alphanumeric characters. Use the validator above to check specific names.

What is the maximum length for a secret name?

Azure Key Vault allows secret names up to 127 characters. AWS Secrets Manager allows up to 512 characters. Use shorter, descriptive names for easier management and readability.

Are secret names case-sensitive?

Azure Key Vault secret names are case-insensitive, so MySecret and mysecret refer to the same secret. AWS Secrets Manager names are case-sensitive, so they would be treated as two different secrets.

Related Resources