AWS AppSync解析器中$ctx与$context的差异及使用疑问

Great question! This is one of those tiny, confusing quirks in AppSync that trips up a lot of folks—especially when coming from Lambda where you have full control over parameter naming. Let me break down why both variables exist and why you’ll see them mixed together:

• Historical Aliasing & Backward Compatibility
  Early on, AppSync only exposed the context object via the full $context variable. As developers started writing more resolvers, AWS added $ctx as a shorthand alias to make code shorter and cleaner. Since thousands of existing resolvers already relied on $context, AWS kept both to avoid breaking working setups. They’re 100% interchangeable—pointing to the exact same underlying object. For example:

  # These two lines do the exact same thing
  $context.args.userId
  $ctx.args.userId
  

• Amplify CLI’s Generated Code Quirks
  The Amplify CLI’s resolver generator is built from multiple modular components, and over different versions, some parts of the tooling adopted the shorthand $ctx while others stuck with the more explicit $context. It’s not a bug—just a minor inconsistency in how the code is generated behind the scenes. You can safely replace one with the other in your generated resolvers without any impact on functionality.

• Documentation Inconsistencies
  AWS’s documentation is maintained by different teams, and updates don’t always sync perfectly across all pages. Some docs use $context for clarity, others prefer $ctx for brevity. The good news is AWS officially supports both—there’s no "right" or "wrong" choice, just personal preference.

At the end of the day, pick whichever you find more readable. Whether you stick with $context for explicitness or $ctx for conciseness, your resolvers will work exactly the same way.

内容的提问来源于stack exchange，提问作者user3376065