CNCoreNova Docs

AWS Marketplace onboarding

Purchase the API and create your credential

Billing is handled through AWS Marketplace. After subscribing, AWS redirects you to CoreNova to associate the subscription with an API credential.

Credential distinction: the generated CoreNova API key is a bearer credential for api.corenovacloud.com. It is not an AWS access key, secret access key, IAM role, or AWS CLI credential.

Before you subscribe

Limited release: while the listing has Limited visibility, the AWS account must be on the allowed-account list and must use the product link supplied by CoreNova. Public discoverability will be enabled only after the Limited buyer flow is validated.

1. Subscribe in AWS Marketplace

Sign in to the intended buyer AWS account and open the product detail page.
Choose View purchase options.
Review the usage price and legal terms, then choose Subscribe.
Wait for AWS Marketplace to confirm the subscription.

The price and agreement displayed by AWS Marketplace are authoritative. Viewing documentation, querying task state, and downloading a result do not consume a conversion unit.

2. Set up the account

After subscribing, choose Set Up Your Account.
AWS sends a short-lived registration token directly to the CoreNova registration endpoint.
Enter a business email address. Do not place the registration token into email or a support ticket.
CoreNova resolves the token against AWS Marketplace and creates an API key for the associated AWS account and license.

If you leave before setup is complete, open Your Marketplace Software in AWS Marketplace and return to the product's account-setup link.

3. Copy the one-time API key

A successful registration displays a key beginning with loua_. Copy it before leaving the page. CoreNova stores only a SHA-256 hash and cannot display the original value later.

Do not expose the key: never place it in client-side browser code, mobile app bundles, public source repositories, screenshots, URLs, support email, or application logs.

4. Configure local development

Set the credential in the shell that runs your test client. Avoid adding the value to a committed .env file.

export CORENOVA_API_KEY='loua_REPLACE_WITH_YOUR_KEY'

curl --request POST 'https://api.corenovacloud.com/v1/conversions' \
  --header "Authorization: Bearer ${CORENOVA_API_KEY}" \
  --form '[email protected]'

5. Configure production

Store the key in a server-side secret manager and inject it at runtime. For AWS workloads, use AWS Secrets Manager or an encrypted Systems Manager Parameter Store parameter, then grant only the calling workload permission to read that secret.

# Application configuration
CORENOVA_API_BASE_URL=https://api.corenovacloud.com
CORENOVA_API_KEY=<load from your secret manager at runtime>

Do not grant CoreNova access to your AWS account. The client only sends the bearer credential and one file to the CoreNova API.

Recover or rotate a key

The original value cannot be recovered. To replace a lost or exposed key:

  1. Return to the product under Your Marketplace Software.
  2. Open the account-setup link again.
  3. Complete registration and copy the newly generated key.
  4. Update the production secret and restart or refresh dependent workloads.
  5. Confirm that the new key works.
Rotation behavior: completing registration again immediately invalidates the previous API key for that Marketplace license. Coordinate the secret update to avoid an outage.

Activation and access errors

SymptomMeaningAction
Registration token missingThe registration endpoint was opened directly.Return to AWS Marketplace and choose Set Up Your Account.
Registration token invalid or expiredThe AWS token is no longer usable.Restart account setup from AWS Marketplace.
subscription_pending_or_inactiveThe license event has not activated access, or the agreement is inactive.Wait briefly and retry; then check the Marketplace agreement.
invalid_api_keyThe key is mistyped, unknown, or was rotated.Check the injected secret or create a new key.

Canceling the subscription

Manage cancellation from AWS Marketplace. After the license becomes inactive, API calls are rejected and no new conversion work is accepted. Temporary input and output retention continues to follow the documented deletion policy.