Security proxy
Zscaler brokers and enforces secure access.
AWS Marketplace private offer guide
Close the deal without turning procurement into a science project.
If a direct purchase path is not the fastest option, SecureDynamics can help route the transaction through AWS Marketplace using a private offer or CPPO-style motion. The customer simply creates or uses an AWS account, reviews the offer, and accepts it.
Why this exists
Sometimes the deal is ready before the paperwork is.
Direct billing, partner credit limits, and new-partner onboarding can slow down an otherwise clean opportunity. AWS Marketplace gives the customer, partner, and SecureDynamics a structured transaction path that is familiar to procurement teams, auditable, and simple to execute.
The trusted proxy model
One analogy, kept useful.
Think of AWS Marketplace as the procurement checkpoint. The customer validates the offer, accepts the agreed terms, and the purchase is recorded through a recognized marketplace workflow.
Transaction proxy
AWS Marketplace brokers the purchase workflow.
SecureDynamics role
SecureDynamics coordinates the offer, partner motion, and customer success.
For customers
Benefits for the customer
No AWS workload required
The AWS account is used for procurement. The customer does not need to migrate applications or become an AWS cloud project.
Simple private offer acceptance
The offer is prepared for the customer’s AWS account. Procurement reviews the negotiated price, terms, billing details, and accepts.
Cleaner governance
AWS Marketplace provides a known purchase path with offer IDs, agreement details, billing information, and subscription records.
Custom terms and pricing
Private offers can reflect negotiated pricing, term length, and agreed commercial structure.
Support from SecureDynamics
SecureDynamics distribution and sales experts can assist the customer and partner through the process.
For reseller partners
Benefits for the reseller partner
Keep the opportunity moving
When direct credit or billing setup could delay the deal, the marketplace path gives the opportunity another route.
Protect the customer relationship
The partner stays involved while SecureDynamics helps coordinate the private-offer process.
Cleaner transaction mechanics
The offer, acceptance, and subscription workflow happen through AWS Marketplace rather than a one-off manual workaround.
Better for larger opportunities
Marketplace private offers and CPPO-style motions can help support larger or more complex transactions with structured terms.
SecureDynamics backup
If the customer has questions, SecureDynamics can join the call and walk procurement through the steps.
Before starting
What the customer needs before accepting the offer
- A business AWS account, or the ability to create one.
- A secure corporate email or distribution list for the AWS root account owner.
- Company legal name, business address, and billing contact.
- Valid payment method or AWS billing arrangement.
- Phone access for AWS account verification.
- Tax exemption or tax registration details, if applicable.
- The AWS Account ID that should receive the private offer.
- A user or role with AWS Marketplace subscription permissions.
- Purchase order number, if the customer requires one.
- Agreement from finance/procurement on payment timing, currency, and invoice handling.
Customer instructions
Step-by-step customer instructions
1
Create or identify the AWS account
If the customer already has AWS, use the account procurement wants associated with the purchase. If not, create a new business AWS account.
- Go to AWS account sign-up, opens in a new tab.
- Enter a corporate email address and AWS account name.
- Verify the email code.
- Create the root-user password.
- Choose Business account.
- Enter company information.
- Accept the AWS Customer Agreement.
- Add payment method.
- Complete phone verification.
- Select the appropriate AWS Support plan.
- Wait for activation confirmation.
2
Send SecureDynamics the AWS Account ID
SecureDynamics needs the AWS Account ID so the private offer can be extended to the correct buyer account.
- AWS Account ID
- Customer legal entity name
- Procurement contact
- Billing contact
- Desired currency, if applicable
- PO number, if required
- Any special billing or tax notes
3
SecureDynamics prepares the private offer
SecureDynamics coordinates the private offer / CPPO-style motion with the appropriate seller/channel structure. The customer receives either a seller-provided link or sees the offer in the AWS Marketplace Private Offers page, opens in a new tab.
4
Customer reviews the offer
The customer signs into the correct AWS account, opens the private offer, and reviews product, seller of record, price, term, payment schedule, EULA/terms, tax estimate, and any PO details.
5
Customer accepts
For SaaS-style offers, the customer usually chooses Subscribe after reviewing the offer. AWS Marketplace then shows a confirmation summary. If required, the customer completes the seller setup step after acceptance.
6
Fulfillment begins
After acceptance, SecureDynamics and the partner coordinate next steps for delivery, onboarding, or service activation.
Common blockers
Common blockers and how to fix them
I clicked the private offer link and got a 404.
Sign out, sign back into the correct AWS account, and try again. Private offers are visible only to the AWS account that received the offer.
I do not see the private offer.
Confirm the AWS Account ID. Confirm the offer has not expired. Confirm the user has Marketplace permissions. Confirm whether the customer uses AWS Organizations, a payer account, linked account, or Private Marketplace controls.
Procurement says they are not an AWS customer.
They do not need to deploy workloads on AWS. They only need an AWS account to use AWS Marketplace as the procurement rail for this transaction.
The wrong person owns the AWS account.
Use a corporate distribution list and assign appropriate administrative and Marketplace subscription access. Avoid tying the account to one employee.
The customer has a Private Marketplace.
The product may need to be approved or allow-listed by the customer’s Private Marketplace administrator.
Payment, currency, or tax is not ready.
Have procurement verify billing setup, preferred currency, payment method, and tax settings before accepting the offer.
One-page ultra-simple version
The whole process in one minute
- Customer creates or uses an AWS account.
- Customer sends SecureDynamics the AWS Account ID.
- SecureDynamics creates the private offer.
- Customer signs into AWS Marketplace.
- Customer reviews price and terms.
- Customer clicks Subscribe / Accept.
- SecureDynamics and partner proceed with delivery.
That is it. No cloud migration side quest required.
Need help?
SecureDynamics can walk through it with you.
Most customers can complete this without a call. If procurement, finance, or IT wants support, SecureDynamics distribution and sales experts can join the customer and partner to walk through account setup, account ID confirmation, private-offer access, and acceptance.
Email: [SecureDynamics Marketplace Help Email]
Phone: [SecureDynamics Marketplace Help Phone]
FAQ
Questions procurement, partners, and sales teams usually ask
Do we have to move to AWS?
No. For this use case, AWS Marketplace is being used as a procurement path.
Why does SecureDynamics need our AWS Account ID?
The private offer must be extended to the correct AWS buyer account. If the wrong account is used, procurement may not see the offer.
Who should create the AWS account?
The customer’s procurement, finance, IT, or cloud operations team should decide. For business continuity, use a secure corporate distribution list for the account owner email.
Can a partner still be involved?
Yes. The marketplace route is meant to keep the partner motion intact while reducing transaction friction.
What should we review before accepting?
Product, seller of record, price, contract term, payment schedule, EULA/terms, tax estimate, PO details, and the AWS account receiving the offer.
What permissions are needed?
The AWS user or role must have permissions to view and subscribe to AWS Marketplace private offers. Common AWS managed policies include AWSMarketplaceRead-only for viewing and AWSMarketplaceManageSubscriptions or AWSMarketplaceFullAccess for subscription management.
What if we use AWS Organizations?
Confirm whether the offer should go to the payer/management account or a member account. The customer’s AWS admin should make that decision.
What if the offer expires?
SecureDynamics can coordinate a refreshed offer.