{"id":442,"date":"2026-11-03T09:06:02","date_gmt":"2026-11-03T07:06:02","guid":{"rendered":"https:\/\/john-nessime.com\/blog\/?p=442"},"modified":"2026-11-03T09:06:02","modified_gmt":"2026-11-03T07:06:02","slug":"aws-secrets-manager-vs-parameter-store","status":"publish","type":"post","link":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/","title":{"rendered":"AWS Secrets Manager vs Parameter Store: Stop Deciding on Price"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">The pull request comment was one line: why is the database password in Parameter Store and the Stripe key in Secrets Manager?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Nobody had a good answer. Both were added in a hurry, months apart, by different people, and each choice made sense on the day it was made. That is how most AWS accounts end up with secrets in two places. Not by design, by accumulation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The comparison usually gets framed as a pricing question: Parameter Store&#8217;s standard tier has no storage charge, Secrets Manager bills per secret, so use Parameter Store until somebody complains. That framing is wrong, and it stays invisible for months before it costs you anything. What separates these two services is what happens when a value <em>changes<\/em>, not what it costs to sit there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This post covers the failure modes that actually bite, the four levers that decide <strong>AWS Secrets Manager vs Parameter Store<\/strong> for any given value, a decision procedure you can run against a real inventory, and the arguments about this that do not survive contact with a running system.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The two failure modes that actually bite<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Rotation that succeeds while your application quietly breaks<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Secrets Manager&#8217;s single user rotation strategy changes the password on the existing database user. AWS documents a short window between the password changing in the database and the secret being updated, during which calls using the rotated credentials can be denied. Retry logic covers that window.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is the documented gap. The one that catches people is quieter.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your application fetched the credential once at boot, cached it in a module-level variable, and never looked again. Rotation completes. The rotation function logs success. Nothing breaks. Then a container recycles, picks up the new value and works fine, while older containers keep running on connections opened before the change. It looks healthy right up until a connection pool churns and part of your fleet starts failing authentication against a service you have not deployed in weeks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The alternating users strategy exists for exactly this. Instead of changing one user&#8217;s password, Secrets Manager clones the user and alternates which one it updates, so a valid credential exists on both sides of every change. The price is a second database user and a separate superuser secret with permission to do the cloning. AWS recommends single user for most cases and for interactive or one-off credentials, and alternating users where the application needs high availability.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The rule I use: if consumers cache and you rotate on a schedule, you need alternating users or an explicit refresh path. A shorter cache TTL narrows the window, it does not close it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">A throughput ceiling you do not own<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Parameter Store read throughput is a quota on the account and Region, not on the parameter and not on the caller. Every cold start, every task boot, every CI job in that account draws from the same budget. The default is sized for low-volume workloads, and there is an opt-in higher throughput setting that raises the ceiling for an additional charge.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The failure presents as an application bug. A scale-out event or a chatty pipeline fans out, <code>GetParameter<\/code> starts returning <code>ThrottlingException<\/code>, and services fail at boot for reasons unrelated to the code anybody just shipped. Nothing in the console tells you that you are near the line.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Both services have quotas. The difference is blast radius: Secrets Manager throttling is annoying, Parameter Store throttling is a shared resource problem where one team&#8217;s new batch job degrades another team&#8217;s deploys. Alarm on throttling for both before you need to. CloudWatch does it natively, and if your dashboards live in Grafana Cloud or a self-hosted Grafana, pull the metric across so the alert lands where people actually look.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Where Parameter Store wins, and where it hurts<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Parameter Store is not primarily a secrets store. It is a hierarchical configuration store that encrypts when you ask it to. Hold that framing and its behaviour becomes predictable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Where it wins:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Configuration that is not confidential.<\/strong> AMI IDs, feature flags, queue names, tuning values. Putting these in Secrets Manager means paying a per-secret charge for data with no confidentiality requirement.<\/li>\n\n\n\n<li><strong>Hierarchies and bulk reads.<\/strong> Path-based naming plus <code>GetParametersByPath<\/code> pulls a whole subtree in one call, which is what a service wants at startup.<\/li>\n\n\n\n<li><strong>No storage charge on the standard tier,<\/strong> so nobody is incentivized to cram unrelated values together to save money.<\/li>\n\n\n\n<li><strong>Parameter policies and AWS public parameters<\/strong> live here, including read-only values AWS publishes for things like current AMI IDs.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Where it hurts:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>No rotation.<\/strong> You write the function, schedule it, and own verification and rollback yourself.<\/li>\n\n\n\n<li><strong>CloudFormation cannot create an encrypted parameter.<\/strong> The <code>AWS::SSM::Parameter<\/code> resource accepts <code>String<\/code> and <code>StringList<\/code> only. You can reference an existing encrypted parameter through the <code>ssm-secure<\/code> dynamic reference, and only on the resource properties that support that pattern.<\/li>\n\n\n\n<li><strong>No recovery window.<\/strong> Delete is delete, and parameter history does not survive deleting the parameter.<\/li>\n\n\n\n<li><strong>Cross-account sharing requires the advanced tier,<\/strong> through Resource Access Manager.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Where AWS Secrets Manager wins, and where it hurts<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Secrets Manager is a lifecycle service. Storage is the least interesting thing it does.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Where it wins:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Managed rotation<\/strong> for Amazon RDS, Aurora, Redshift and DocumentDB, using AWS-published rotation functions and two documented strategies.<\/li>\n\n\n\n<li><strong>Versioning with staging labels.<\/strong> <code>AWSCURRENT<\/code>, <code>AWSPENDING<\/code> and <code>AWSPREVIOUS<\/code> give rotation a defined state machine and give you a last known good version to fall back to.<\/li>\n\n\n\n<li><strong>A recovery window on delete,<\/strong> between seven and thirty days, defaulting to thirty.<\/li>\n\n\n\n<li><strong>Cross-region replication and resource policies<\/strong> as first-class features, so multi-Region and cross-account access are properties of the secret rather than things you build.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Where it hurts:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cost scales by multiplication.<\/strong> Storage bills per secret per month, prorated hourly, and every cross-region replica bills as its own secret. The multiplier is secrets times environments times Regions.<\/li>\n\n\n\n<li><strong>The recovery window is a deployment trap.<\/strong> Destroy an environment, apply again, and the create fails because the name is still reserved.<\/li>\n\n\n\n<li><strong>Managed rotation only covers databases.<\/strong> Anything else means writing your own function, so you carry the operational burden without the free tier.<\/li>\n\n\n\n<li><strong>The pricing model pushes you toward bundling.<\/strong> One secret per value is the clean design and the expensive one, so teams pack fields into JSON and lose per-value IAM granularity.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Four levers that decide AWS Secrets Manager vs Parameter Store<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Does the value have to change on a schedule?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If yes, and it is a credential for RDS, Aurora, Redshift or DocumentDB, use Secrets Manager and stop deliberating. You are not paying for storage. You are paying to avoid writing, testing and maintaining a rotation function, and to inherit a staging-label state machine that makes a failed rotation recoverable instead of an outage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the value never changes on a schedule, an AMI ID, a webhook URL, a vendor key you replace manually once a year, then rotation machinery buys you nothing.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. How many independent gates guard the read path?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is the lever people skip, and it matters more than the service choice.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Both services encrypt through KMS. The question is whether KMS is a second, independent authorization decision or a formality. An encrypted parameter under the AWS managed key for Systems Manager is decrypted through that key on behalf of the service, so in practice the SSM permission is the gate. Encrypt under a customer managed key instead and the caller must also be allowed <code>kms:Decrypt<\/code> on that specific key. Now two policies in two services both have to say yes, and you can scope the key policy to a named set of roles independently of who may call Systems Manager. The first gate protects the API surface, the second protects the plaintext.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same split exists in Secrets Manager, between the AWS managed key and one you create.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Store an encrypted parameter under a customer managed key\n# instead of the AWS managed default.\naws ssm put-parameter \n  --name \"\/prod\/billing\/db-password\" \n  --type SecureString \n  --key-id \"alias\/prod-app-secrets\" \n  --value \"REPLACE_ME\" \n  --overwrite\n\n# Reading it now needs ssm:GetParameter AND\n# kms:Decrypt on alias\/prod-app-secrets.\naws ssm get-parameter \n  --name \"\/prod\/billing\/db-password\" \n  --with-decryption \n  --query \"Parameter.Value\" \n  --output text<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">There is a second payoff. A customer managed key makes the decrypt call attributable in CloudTrail against a key policy you control, which turns &#8220;someone read a secret&#8221; into &#8220;this role decrypted this value with this key at this time&#8221;. That is usually what an auditor is asking for, and it is independent of which store you land on.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. What does the retrieval path look like under load?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Neither service is designed to be called on every request. Both punish you for it in different currencies: Parameter Store with a shared throughput ceiling, Secrets Manager with a per-call charge.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The answer for both is caching, and AWS ships the mechanism rather than making you build it. The Secrets Manager Agent, now published under the name AWS Workload Credentials Provider, runs as a sidecar or local service, holds secrets in memory, and serves them to your application over a local HTTP endpoint, so the app makes one call instead of thousands and needs no AWS SDK dependency to do it. For Lambda, the AWS Parameters and Secrets Lambda Extension does the equivalent inside the execution environment and covers both services.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Caching moves the problem rather than removing it. A cached credential is a stale credential during rotation, which loops straight back to lever one.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. How does the value get created and destroyed?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Creation first. CloudFormation cannot create an encrypted parameter, so if your pipeline is CloudFormation or CDK and the value must be encrypted from the moment it exists, Secrets Manager is the path of least resistance. The usual workarounds, a Lambda-backed custom resource or creating the parameter out of band, both move the secret outside the template that claims to own it. That is a real cost, not a detail.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Destruction is where the surprise lives. Secrets Manager schedules deletion after a recovery window with a minimum of seven days and a default of thirty, and the name stays reserved for the duration.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Shorten the recovery window to the documented minimum.\naws secretsmanager delete-secret \n  --secret-id prod\/billing\/db \n  --recovery-window-in-days 7\n\n# Or skip the window entirely. There is no undo after this.\naws secretsmanager delete-secret \n  --secret-id ephemeral\/pr-1482\/db \n  --force-delete-without-recovery<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">AWS notes the actual deletion runs as an asynchronous background process, so deleting and immediately recreating a secret with the same name needs backoff and retry even with the force flag. This is why per-branch environments built with Terraform or OpenTofu fail on their second run. Use the force flag deliberately, put a unique suffix in the name, or keep ephemeral values in Parameter Store where deletion is immediate.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Cost levers, without quoting numbers that will age<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Published rates change. The billing mechanisms are stable, and the mechanisms are what let you predict the bill.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Parameter Store standard tier<\/strong> carries no storage charge. The advanced tier is charged per parameter, and the higher throughput setting is charged separately as an account and Region level switch.<\/li>\n\n\n\n<li><strong>Secrets Manager<\/strong> charges per stored secret per month, prorated hourly, plus a charge per block of API calls. Replicas count as separate stored secrets.<\/li>\n\n\n\n<li><strong>KMS<\/strong> charges a monthly fee per customer managed key plus a request charge on cryptographic operations. This applies to both services and it is the line most estimates forget.<\/li>\n\n\n\n<li><strong>Rotation<\/strong> has no separate line item, but the rotation function bills as ordinary Lambda usage.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Two consequences. The Secrets Manager multiplier is not the number of secrets, it is secrets across environments across Regions, and replicas are the sneaky term because nobody remembers enabling them. And the advanced parameter tier is a one-way door: you can promote a standard parameter to advanced, but you cannot demote it, because reverting would truncate the value. Undoing that means delete and recreate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you cannot see which term is growing, break the bill down by service and tag before you migrate anything. Cost Explorer handles the single-account case; for cross-account views without building the aggregation yourself, tools like Vantage or CloudZero will answer &#8220;is this secret count, replication, or retrieval frequency&#8221; in a few minutes. That is a better use of an afternoon than guessing.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A decision procedure you can run today<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Take an actual list of values and walk each one through this. It takes about a minute each.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Is it confidential at all?<\/strong> If no, Parameter Store, plain <code>String<\/code> type, done. Do not encrypt configuration for the aesthetics.<\/li>\n\n\n\n<li><strong>Is it a database credential that should rotate on a schedule?<\/strong> Secrets Manager with managed rotation. Choose single user or alternating users based on whether consumers cache.<\/li>\n\n\n\n<li><strong>Does it need scheduled rotation but is not a supported database?<\/strong> You are writing a function either way. Secrets Manager if you want versioning, staging labels and a recovery window; Parameter Store if the free tier matters more and you accept owning the lifecycle.<\/li>\n\n\n\n<li><strong>Does it need to exist in more than one Region or account?<\/strong> Secrets Manager gives you replication and resource policies directly. Parameter Store shares across accounts through Resource Access Manager, advanced tier only.<\/li>\n\n\n\n<li><strong>Does CloudFormation or CDK create it?<\/strong> Encrypted parameters are not creatable there, so it is Secrets Manager or an accepted out-of-band step.<\/li>\n\n\n\n<li><strong>Is it read frequently?<\/strong> Cache it either way, then return to step two, because caching and rotation interact and that interaction is where outages come from.<\/li>\n\n\n\n<li><strong>Everything else<\/strong> goes to Parameter Store, encrypted under a customer managed key.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Most accounts land with the large majority of values in Parameter Store and a short list of rotating database credentials in Secrets Manager. That split is healthy. What is not healthy is being unable to say why a particular value is where it is.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Once you accept you will use both, the operational work is making them look like one system: one naming convention across both stores, IAM scoped to the path rather than the service, KMS keys separated by trust boundary rather than by service, and the rule written down where the next person will find it. Two lines in a repository README beats a policy document nobody opens.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Arguments that do not survive contact<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>&#8220;Parameter Store is free, so use it for everything.&#8221;<\/strong> The standard tier has no storage charge, which is not the same as free. KMS requests bill, the higher throughput setting bills, advanced parameters bill, and the rotation function you write instead of using a managed one has a real cost in engineering hours and incident risk.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>&#8220;Secrets Manager is expensive.&#8221;<\/strong> Per secret it is small. The bill grows through multiplication, not unit price. Before migrating anything, count secrets across environments and Regions and find out how many replicas exist that nobody asked for. Deleting unused replicas is usually a bigger win than a migration project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>&#8220;Just use Vault and skip the argument.&#8221;<\/strong> HashiCorp Vault is a better answer if you are multi-cloud, need dynamic short-lived credentials, or want secrets engines AWS does not offer. It also hands you a cluster to run, upgrade, seal and unseal, back up and monitor, plus a licensing decision. On a single-cloud AWS estate with a handful of rotating credentials, the AWS services are less capable and less work. Both statements are true at once, and which dominates depends on how much platform team you have.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>&#8220;It is encrypted at rest, so it is secure.&#8221;<\/strong> Encryption at rest protects against someone reading the storage layer, which is not the threat you have. Your threat is an over-permissive role and a compromised workload. That is an IAM policy and a KMS key policy question, and the answer is the same on either service.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>&#8220;We will add rotation later.&#8221;<\/strong> Rotation is not a feature flag, it is a coordination problem between the store, the target system and every consumer&#8217;s caching behaviour. Deciding that a credential will eventually rotate changes how you write the consumer today. Retrofitting it means touching every consumer anyway.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently asked questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Can I migrate a value between the two without downtime?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes, with a dual read. Write the value to the new location, deploy consumers that read the new location and fall back to the old one, then use CloudTrail to confirm nothing still reads the old path before deleting it. Do not skip the CloudTrail step; the consumer you forgot is always a job that runs monthly. If the value passed through a local file during the move, erase that file properly rather than with <code>rm<\/code>, using <code>shred<\/code> on Linux or a secure deletion tool such as those from O&amp;O Software on Windows.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does Parameter Store support rotation?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not as a built-in feature. You write a function and invoke it on a schedule, typically with an EventBridge rule. You also inherit everything managed rotation handles for you: verifying the new credential works before committing to it, rolling back cleanly when it does not, and giving consumers an overlap window.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Which one should I use for third-party API keys?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It depends on whether you rotate them. Most vendor keys get rotated manually and rarely, in which case an encrypted parameter under a customer managed key is enough. If the provider supports programmatic key rotation and you want that automated, Secrets Manager&#8217;s version staging is what makes the swap safe.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can workloads outside AWS read from either service?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Both, over the API, with AWS credentials. That means a long-lived access key or a federated identity, and you should federate wherever the platform supports it. If part of your estate runs on VPS hosts at a provider like Contabo or InterServer, this is the boundary to think hardest about, because you have just placed an AWS credential on a machine whose network you do not control. Scope the role narrowly, apply condition keys where the network path allows, and treat that credential as the one most likely to leak.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What happens if I delete something by accident?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Secrets Manager lets you restore during the recovery window, which is the single best argument for putting genuinely important credentials there. Parameter Store has no equivalent. Once the parameter is gone your options are whatever exists in state files, backups or someone&#8217;s terminal history, and none of those is a plan.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should ECS or EKS workloads pull secrets differently?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">ECS can inject values from either service directly into a task&#8217;s environment, which removes SDK code from the container but reads the value at task start, so a rotation does not reach a running task. On EKS you have both the Secrets Store CSI driver with the AWS provider, which mounts values as files, and the agent sidecar pattern, which serves them over localhost and can refresh without restarting the pod. Choose based on whether your application can reload a credential mid-life. If it cannot, mounting and injection are equivalent, and rotation means a rollout.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The one thing worth remembering<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The <strong>AWS Secrets Manager vs Parameter Store<\/strong> decision is a lifecycle decision wearing a pricing costume. What separates the two is not what they store, it is what they do when the value changes, when it gets deleted, when a Region falls over, and when ten thousand containers ask for it at once.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Decide per value, not per project. Configuration and rarely-changing keys belong in Parameter Store. Database credentials that rotate on a schedule belong in Secrets Manager. Put a customer managed key in front of both so the second gate does real work, cache reads so you are not fighting a quota, and make sure whoever wrote the caching understands what happens the next time a rotation runs. If you cannot explain why a given value lives where it does, that is the value that will surprise you.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Need a second pair of eyes on your secrets setup?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Most of the work here is not choosing a service, it is untangling what already exists. Things I can help with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Auditing an AWS account for where secrets actually live, which roles can decrypt them, and which values are duplicated across environments or replicated into Regions nobody uses<\/li>\n\n\n\n<li>Designing a naming hierarchy and path-scoped IAM so one policy covers a service instead of one policy per value<\/li>\n\n\n\n<li>Setting up managed rotation for RDS and Aurora credentials, including the alternating users pattern when the application caches and cannot be changed<\/li>\n\n\n\n<li>Writing and testing custom rotation functions for non-database secrets, with the rollback path actually exercised rather than assumed<\/li>\n\n\n\n<li>Moving values between the two stores with a dual-read cutover and CloudTrail verification that nothing is left reading the old path<\/li>\n\n\n\n<li>Working out whether a growing Secrets Manager line item is secret count, replication or retrieval frequency, and fixing the one actually responsible<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Send me a redacted IAM policy, a CloudTrail query result, or the output of listing your parameters by path, and I will tell you what I would change first and why.<\/p>\n\n\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/www.upwork.com\/freelancers\/~01f15a912ad84a6620\" target=\"_blank\" rel=\"noreferrer noopener\">Work with me on Upwork<\/a><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Most teams pick between AWS Secrets Manager and SSM Parameter Store on price, then get bitten months later by rotation semantics, a shared throughput quota, or a recovery window that blocks a redeploy. Here are the four levers that actually decide it, per value, plus a decision procedure you can run against a real inventory.<\/p>\n","protected":false},"author":1,"featured_media":1215,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25,612,24],"tags":[421,472,93,283,186,624,103,480,187,265,99,91,622,613,625,230,261,88],"class_list":["post-442","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cloud-computing","category-cloud-security","category-devops","tag-amazon-ecs","tag-amazon-rds","tag-aws","tag-aws-kms","tag-aws-lambda","tag-aws-secrets-manager","tag-cloud-security","tag-cloudtrail","tag-cost-optimization","tag-hashicorp-vault","tag-iam","tag-infrastructure-as-code","tag-key-rotation","tag-least-privilege","tag-parameter-store","tag-rate-limiting","tag-secrets-management","tag-terraform","entry","has-media"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>AWS Secrets Manager vs Parameter Store: How to Choose<\/title>\n<meta name=\"description\" content=\"AWS Secrets Manager vs Parameter Store, decided by rotation, key gating, throughput and lifecycle instead of price, plus the failure modes that bite.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"AWS Secrets Manager vs Parameter Store: How to Choose\" \/>\n<meta property=\"og:description\" content=\"AWS Secrets Manager vs Parameter Store, decided by rotation, key gating, throughput and lifecycle instead of price, plus the failure modes that bite.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/\" \/>\n<meta property=\"og:site_name\" content=\"John Nessime\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/J.Nessime\" \/>\n<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/J.Nessime\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-03T07:06:02+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/john-nessime.com\/blog\/wp-content\/uploads\/2026\/09\/aws-secrets-manager-vs-parameter-store.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1536\" \/>\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"John Nessime\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"John Nessime\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"15 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/\"},\"author\":{\"name\":\"John Nessime\",\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/#\\\/schema\\\/person\\\/ede0b56d0c808f123f57d5d796902105\"},\"headline\":\"AWS Secrets Manager vs Parameter Store: Stop Deciding on Price\",\"datePublished\":\"2026-11-03T07:06:02+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/\"},\"wordCount\":3382,\"publisher\":{\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/#\\\/schema\\\/person\\\/ede0b56d0c808f123f57d5d796902105\"},\"image\":{\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/aws-secrets-manager-vs-parameter-store.png\",\"keywords\":[\"Amazon ECS\",\"Amazon RDS\",\"AWS\",\"AWS KMS\",\"AWS Lambda\",\"AWS Secrets Manager\",\"Cloud Security\",\"CloudTrail\",\"Cost Optimization\",\"HashiCorp Vault\",\"IAM\",\"Infrastructure as Code\",\"Key Rotation\",\"Least Privilege\",\"Parameter Store\",\"Rate Limiting\",\"Secrets Management\",\"Terraform\"],\"articleSection\":[\"Cloud Computing\",\"Cloud Security\",\"DevOps\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/\",\"url\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/\",\"name\":\"AWS Secrets Manager vs Parameter Store: How to Choose\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/aws-secrets-manager-vs-parameter-store.png\",\"datePublished\":\"2026-11-03T07:06:02+00:00\",\"description\":\"AWS Secrets Manager vs Parameter Store, decided by rotation, key gating, throughput and lifecycle instead of price, plus the failure modes that bite.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/#primaryimage\",\"url\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/aws-secrets-manager-vs-parameter-store.png\",\"contentUrl\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/aws-secrets-manager-vs-parameter-store.png\",\"width\":1536,\"height\":1024,\"caption\":\"AWS Secrets Manager vs Parameter Store comparison showing credential rotation, throughput limits, cost models, and configuration use cases.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/devops\\\/aws-secrets-manager-vs-parameter-store\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"AWS Secrets Manager vs Parameter Store: Stop Deciding on Price\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/\",\"name\":\"John Nessime\",\"description\":\"Cloud, DevOps, Data &amp; AI \u2014 Built, Tested, Explained\",\"publisher\":{\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/#\\\/schema\\\/person\\\/ede0b56d0c808f123f57d5d796902105\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/#\\\/schema\\\/person\\\/ede0b56d0c808f123f57d5d796902105\",\"name\":\"John Nessime\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/cropped-jn.png\",\"url\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/cropped-jn.png\",\"contentUrl\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/cropped-jn.png\",\"width\":512,\"height\":512,\"caption\":\"John Nessime\"},\"logo\":{\"@id\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/cropped-jn.png\"},\"description\":\"AWS Certified Solutions Architect helping businesses build reliable cloud, data, reporting, and automation solutions. I help startups, agencies, and growing businesses replace manual processes and disconnected data with practical AWS architectures, clean data pipelines, useful dashboards, and maintainable automation.\",\"sameAs\":[\"https:\\\/\\\/john-nessime.com\\\/blog\",\"https:\\\/\\\/www.facebook.com\\\/J.Nessime\",\"https:\\\/\\\/www.linkedin.com\\\/in\\\/john-m-nessime\"],\"url\":\"https:\\\/\\\/john-nessime.com\\\/blog\\\/author\\\/johnnessime\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"AWS Secrets Manager vs Parameter Store: How to Choose","description":"AWS Secrets Manager vs Parameter Store, decided by rotation, key gating, throughput and lifecycle instead of price, plus the failure modes that bite.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/","og_locale":"en_US","og_type":"article","og_title":"AWS Secrets Manager vs Parameter Store: How to Choose","og_description":"AWS Secrets Manager vs Parameter Store, decided by rotation, key gating, throughput and lifecycle instead of price, plus the failure modes that bite.","og_url":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/","og_site_name":"John Nessime","article_publisher":"https:\/\/www.facebook.com\/J.Nessime","article_author":"https:\/\/www.facebook.com\/J.Nessime","article_published_time":"2026-11-03T07:06:02+00:00","og_image":[{"width":1536,"height":1024,"url":"https:\/\/john-nessime.com\/blog\/wp-content\/uploads\/2026\/09\/aws-secrets-manager-vs-parameter-store.png","type":"image\/png"}],"author":"John Nessime","twitter_card":"summary_large_image","twitter_misc":{"Written by":"John Nessime","Est. reading time":"15 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/#article","isPartOf":{"@id":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/"},"author":{"name":"John Nessime","@id":"https:\/\/john-nessime.com\/blog\/#\/schema\/person\/ede0b56d0c808f123f57d5d796902105"},"headline":"AWS Secrets Manager vs Parameter Store: Stop Deciding on Price","datePublished":"2026-11-03T07:06:02+00:00","mainEntityOfPage":{"@id":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/"},"wordCount":3382,"publisher":{"@id":"https:\/\/john-nessime.com\/blog\/#\/schema\/person\/ede0b56d0c808f123f57d5d796902105"},"image":{"@id":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/#primaryimage"},"thumbnailUrl":"https:\/\/john-nessime.com\/blog\/wp-content\/uploads\/2026\/09\/aws-secrets-manager-vs-parameter-store.png","keywords":["Amazon ECS","Amazon RDS","AWS","AWS KMS","AWS Lambda","AWS Secrets Manager","Cloud Security","CloudTrail","Cost Optimization","HashiCorp Vault","IAM","Infrastructure as Code","Key Rotation","Least Privilege","Parameter Store","Rate Limiting","Secrets Management","Terraform"],"articleSection":["Cloud Computing","Cloud Security","DevOps"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/","url":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/","name":"AWS Secrets Manager vs Parameter Store: How to Choose","isPartOf":{"@id":"https:\/\/john-nessime.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/#primaryimage"},"image":{"@id":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/#primaryimage"},"thumbnailUrl":"https:\/\/john-nessime.com\/blog\/wp-content\/uploads\/2026\/09\/aws-secrets-manager-vs-parameter-store.png","datePublished":"2026-11-03T07:06:02+00:00","description":"AWS Secrets Manager vs Parameter Store, decided by rotation, key gating, throughput and lifecycle instead of price, plus the failure modes that bite.","breadcrumb":{"@id":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/#primaryimage","url":"https:\/\/john-nessime.com\/blog\/wp-content\/uploads\/2026\/09\/aws-secrets-manager-vs-parameter-store.png","contentUrl":"https:\/\/john-nessime.com\/blog\/wp-content\/uploads\/2026\/09\/aws-secrets-manager-vs-parameter-store.png","width":1536,"height":1024,"caption":"AWS Secrets Manager vs Parameter Store comparison showing credential rotation, throughput limits, cost models, and configuration use cases."},{"@type":"BreadcrumbList","@id":"https:\/\/john-nessime.com\/blog\/devops\/aws-secrets-manager-vs-parameter-store\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/john-nessime.com\/blog\/"},{"@type":"ListItem","position":2,"name":"AWS Secrets Manager vs Parameter Store: Stop Deciding on Price"}]},{"@type":"WebSite","@id":"https:\/\/john-nessime.com\/blog\/#website","url":"https:\/\/john-nessime.com\/blog\/","name":"John Nessime","description":"Cloud, DevOps, Data &amp; AI \u2014 Built, Tested, Explained","publisher":{"@id":"https:\/\/john-nessime.com\/blog\/#\/schema\/person\/ede0b56d0c808f123f57d5d796902105"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/john-nessime.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/john-nessime.com\/blog\/#\/schema\/person\/ede0b56d0c808f123f57d5d796902105","name":"John Nessime","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/john-nessime.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-jn.png","url":"https:\/\/john-nessime.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-jn.png","contentUrl":"https:\/\/john-nessime.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-jn.png","width":512,"height":512,"caption":"John Nessime"},"logo":{"@id":"https:\/\/john-nessime.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-jn.png"},"description":"AWS Certified Solutions Architect helping businesses build reliable cloud, data, reporting, and automation solutions. I help startups, agencies, and growing businesses replace manual processes and disconnected data with practical AWS architectures, clean data pipelines, useful dashboards, and maintainable automation.","sameAs":["https:\/\/john-nessime.com\/blog","https:\/\/www.facebook.com\/J.Nessime","https:\/\/www.linkedin.com\/in\/john-m-nessime"],"url":"https:\/\/john-nessime.com\/blog\/author\/johnnessime\/"}]}},"_links":{"self":[{"href":"https:\/\/john-nessime.com\/blog\/wp-json\/wp\/v2\/posts\/442","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/john-nessime.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/john-nessime.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/john-nessime.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/john-nessime.com\/blog\/wp-json\/wp\/v2\/comments?post=442"}],"version-history":[{"count":1,"href":"https:\/\/john-nessime.com\/blog\/wp-json\/wp\/v2\/posts\/442\/revisions"}],"predecessor-version":[{"id":482,"href":"https:\/\/john-nessime.com\/blog\/wp-json\/wp\/v2\/posts\/442\/revisions\/482"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/john-nessime.com\/blog\/wp-json\/wp\/v2\/media\/1215"}],"wp:attachment":[{"href":"https:\/\/john-nessime.com\/blog\/wp-json\/wp\/v2\/media?parent=442"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/john-nessime.com\/blog\/wp-json\/wp\/v2\/categories?post=442"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/john-nessime.com\/blog\/wp-json\/wp\/v2\/tags?post=442"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}