AWS Payment Cryptography Control Plane
Read list keys, list aliases, get alias from Payment Cryptography (SigV4).
OCNORA ships 4 typed AWS Payment Cryptography Control Plane operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect AWS Payment Cryptography Control Plane
- Authentication
- API key
- Credential
- {"access_key_id", "secret_access_key"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with AWS Payment Cryptography Control Plane
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample AWS Payment Cryptography Control Plane workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Payment Cryptography Control Plane trigger is needed.
- 2Get Aliaspayment_cryptography.get_aliasGets the Amazon Web Services Payment Cryptography key associated with the alias.
- 3Write Actionpayment_cryptography.callRun one of 20 write actions on Payment Cryptography.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 4
- Write ActionRun one of 20 write actions on Payment Cryptography.payment_cryptography.call
- Get AliasGets the Amazon Web Services Payment Cryptography key associated with the alias.payment_cryptography.get_alias
- List AliasesLists the aliases for all keys in the caller's Amazon Web Services account and Amazon Web Services Region. You can filter the aliases by keyARN.payment_cryptography.list_aliases
- List KeysLists the keys in the caller's Amazon Web Services account and Amazon Web Services Region.payment_cryptography.list_keys
AWS Payment Cryptography Control Plane questions
- How does OCNORA authenticate with AWS Payment Cryptography Control Plane?
- With a stored API key credential, shaped {"access_key_id", "secret_access_key"}. A connection test can check it when you add it.
- What can I automate with AWS Payment Cryptography Control Plane?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS Payment Cryptography Control Plane operation I need is not listed?
- Where AWS Payment Cryptography Control Plane has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use AWS Payment Cryptography Control Plane?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS Payment Cryptography Control Plane calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first AWS Payment Cryptography Control Plane workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.