How does OCNORA authenticate with Amazon CloudFront?

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 Amazon CloudFront?

3 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Amazon CloudFront operation I need is not listed?

Where Amazon CloudFront 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 Amazon CloudFront?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Amazon CloudFront 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.

Amazon CloudFront

Amazon Web ServicesAPI keyConnection test available

Manage CloudFront distributions and invalidations (SigV4).

OCNORA ships 3 typed Amazon CloudFront 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.

Ask about Amazon CloudFront

Before you connect Amazon CloudFront

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 Amazon CloudFront

Operations, grouped by what they do to your data.

Read and search 2

Other operations 1

Invalidate Cache

A sample Amazon CloudFront workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon CloudFront trigger is needed.
2
Get Distributioncloudfront.get_distribution
Read one distribution's status and domain.
3
Invalidate Cachecloudfront.create_invalidation
Invalidate cached paths at the edge.

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 3