Table of contents
- AWS Seller Registration: Common Blockers
- AWS Public Profile Requirements
- Website & Support Information Expectations
- Private Offers and Agreement-Based Offers (ABO)
- Miscellaneous and best practices
Vendor Assessment
AWS Seller Registration: Common Blockers
Why can AWS Marketplace seller registration be rejected or delayed?
AWS may reject or delay seller registration if required information is missing, inconsistent, or cannot be validated during review. Common blockers include:
Incomplete or unapproved AWS Marketplace public profile
Missing or unclear support/contact information on the company website
Website not clearly reflecting the seller’s business or offerings
Website accessibility or trust issues (e.g., broken links, non-public URLs)
Mismatches between legal, tax, or business information across AWS systems
AWS typically requires these issues to be resolved before allowing sellers to publish listings or proceed with approvals.
AWS Public Profile Requirements
What information must be completed in the AWS Marketplace public profile?
Before a seller can publish or move forward in AWS Marketplace, the public profile must be fully completed and approved. This includes:
Legal company name and display name
Company website URL
Company description
Logo and branding details
Public contact or support information
If the public profile is incomplete or fails AWS review, seller registration and listing publication may be blocked until updates are made and re-approved.
Website & Support Information Expectations
What does AWS expect to see on a seller’s official website?
AWS uses the seller’s website to validate legitimacy and buyer readiness. At a minimum, the website should:
Be publicly accessible and functional
Clearly identify the company and its products or services
Include visible support or contact information (e.g., support email, contact form, or support page)
Is public pricing required on the website?
No. AWS does not require pricing to be publicly available unless the seller explicitly offers public pricing.
If pricing is public, it should be clear and consistent.
If pricing is private, custom, or handled via Private Offers or sales-led motions, AWS only expects clear product or service descriptions, not price lists.
📒 Key clarification: Lack of public pricing alone is not a blocker. Missing support/contact information or unclear business details can be.
Marketplace Listings
How does Labra ensure progress in the Marketplace listing process?
Labra supports sellers throughout the AWS Marketplace listing process by coordinating required setup steps, assisting with listing configuration, and helping validate that AWS requirements are met prior to submission. This includes guidance during listing creation and support through AWS review and testing.
Do product requirements and prerequisites for listing differ by cloud marketplace?
Yes. Each cloud marketplace defines its own prerequisites and technical requirements that must be met for a product to be eligible for listing. Sellers must ensure their product complies with the specific requirements of the marketplace where they intend to publish.
How does Labra for Marketplace help with meeting requirements?
Labra provides guided support to help sellers identify and address AWS Marketplace requirements during listing creation. If gaps or missing requirements are identified, sellers are supported in resolving them prior to submission for AWS review.
How does the onboarding process for Labra for Marketplace work?
The onboarding process allows sellers to submit their listing information and begin the AWS Marketplace listing process through a guided workflow. This enables sellers to provide required details upfront and proceed through listing creation and review with AWS.
Can my other team members help in creating the listing?
Yes. Sellers can collaborate with multiple team members during listing creation. Access can be granted to relevant stakeholders so they can contribute required information as part of the listing process.
Will Labra need access to my Marketplace account?
Yes. Sellers are required to configure appropriate access and permissions in their AWS Marketplace seller account so listings can be managed and submitted for AWS review.
What products can Labra for Marketplace support?
Labra for Marketplace supports the following product types:
SaaS
Container
Professional Services
Note: Support for product types may vary by cloud marketplace.
What are the requirements for an AWS Marketplace SaaS listing?
To list a SaaS product on AWS Marketplace, sellers must meet several core requirements, including:
An active AWS account
A SaaS application that meets AWS technical requirements
A defined pricing model supported by AWS Marketplace
Customer support availability (for example, a support website or contact method)
Compliance with applicable legal, security, and data privacy requirements
Integration with required AWS Marketplace APIs for entitlements and metering
Complete product content, including descriptions, logos, and usage information
An End User License Agreement (EULA)
Requirements may vary based on product architecture. Sellers should refer to AWS Marketplace documentation for the most up-to-date guidance.
How long does it take to get listed on AWS Marketplace?
Once all required listing information is provided, AWS Marketplace listing timelines typically range from 2 to 6 weeks. Actual timelines depend on listing complexity, completeness of submitted information, and AWS review availability.
How soon will my listing get approved?
AWS review and approval timelines vary. In many cases, approval can take 2 to 4 weeks, depending on AWS testing availability and the complexity of the product. These timelines are estimates and may vary.
What is the process for AWS testing the listing?
After a listing is submitted, AWS reviews and tests the purchase and subscription flow, including entitlement validation. Sellers may be asked to confirm testing readiness or provide additional updates before final approval. Once testing is complete, sellers can review and approve the listing for publication.
What are allowlisted AWS accounts?
Allowlisting allows sellers to restrict access to their AWS Marketplace listing to specific AWS accounts. Only approved accounts can view, subscribe to, or purchase the product. This is commonly used for limited availability, previews, or controlled releases.
How quickly can I migrate an existing AWS Marketplace listing to Labra?
Migrating an existing AWS Marketplace listing to Labra is a self-service process and typically takes up to two weeks, depending on the seller’s readiness and AWS review timelines.
The process does not require engineering effort and does not cause listing downtime.
Can I update my Marketplace listing page myself?
Yes. Sellers can make updates to their Marketplace listing directly through the Labra platform without requiring assistance from the Labra team.
Changes are submitted to AWS for review where applicable.
Can I customize my SaaS buyer registration page?
Yes. Sellers can customize their SaaS buyer registration page to align with company branding directly on Labra.
Customization is self-service
Updates can be made at any time
-
By default, the page is hosted on Labra’s domain, with support for custom domains if required
Pricing Dimensions
Can I publish an AWS Marketplace listing without showing pricing?
No. AWS requires all listings to include public pricing dimensions in order to pass review and testing. At the time of submission, sellers must provide public pricing so the listing can be approved by AWS.
What types of pricing dimensions are supported for SaaS products in AWS Marketplace?
AWS Marketplace supports multiple pricing dimension types for SaaS products. These dimensions define how customers are charged and what unit of value is being measured. Common pricing dimension types include:
Contract-based pricing
Used for fixed-term agreements where customers pay a predefined amount for a subscription period.
Monthly or annual subscription fees
Flat-rate pricing for a defined term
Often used for enterprise or bundled offerings
Usage-based pricing
Used when charges are based on actual product consumption.
Charges are metered and reported to AWS
-
Common units include:
Number of users
API calls
Data volume processed or stored
Compute hours or resource usage
Allows customers to pay only for what they use
Tiered pricing
Used when pricing varies based on usage thresholds or volume bands.
Different price points apply as usage increases
Often combined with usage-based dimensions
Helps incentivize higher consumption with volume discounts
Free or trial dimensions
Used to offer limited access or evaluation periods.
Free trials for a defined duration
Free usage up to a capped limit
Commonly paired with paid dimensions for conversion after trial
How many pricing dimensions can a SaaS product have?
AWS Marketplace allows sellers to define multiple pricing dimensions for a single SaaS product. This enables flexible pricing models such as:
Base subscription fee + usage-based overages
Multiple feature-based dimensions
Bundled plans with optional add-ons
Each pricing dimension must be clearly defined, measurable, and aligned with the product’s value model.
When can I hide public pricing and use only “Request Private Offer”?
AWS allows sellers to hide public pricing and display only a “Request Private Offer” option after the listing has been approved and is live.
At that point, sellers may choose to:
Keep public pricing visible and also allow private offers, or
Hide public pricing and rely solely on private offers
Availability of this option is determined by AWS Marketplace policies and seller eligibility.
If I enable private offers later, what happens to the pricing I originally submitted?
The pricing submitted during listing creation is required for AWS approval and does not limit or override private offers.
After private offers are enabled:
Sellers can negotiate custom pricing privately with customers
Public pricing can remain visible or be hidden, depending on configuration
Private offers operate independently from the original public pricing.
Deployed on AWS
What is the “Deployed on AWS” badge?
The Deployed on AWS badge indicates that AWS has validated your product as running on AWS infrastructure. This confirms that your application meets AWS requirements for being hosted on AWS and can be offered through AWS Marketplace as an AWS-deployed solution.
What does “Not deployed on AWS” mean on my listing?
The “Not deployed on AWS” label indicates that AWS has not yet validated your application as fully running on their infrastructure. To display the “Deployed on AWS” badge, your architecture must be reviewed and approved by AWS.
How do I get the “Deployed on AWS” badge?
You can enable the badge by submitting your architecture diagram and some details about your application’s hosting pattern and application plane. AWS reviews this information to confirm that your product runs on their platform. The diagram is shared privately through your AMMP account and is not public.
Architecture diagram submission requirements:
Format: .png or .jpg
Size: Less than 5MB
Dimensions: Between 780×439 and 7000×7000 pixels
Information AWS requires with the diagram:
-
AWS Hosting Pattern – Does your product:
Run entirely on AWS (application plane + control plane)?
Replicate/migrate data/workloads only to AWS?
Run only the application plane on AWS (control plane outside)?
None of the above?
-
Application Plane Location – Does it run:
Entirely/mostly in your seller AWS account?
Entirely/mostly in the buyer AWS account?
Not applicable?
Once AWS validates your architecture, your listing will display the “Deployed on AWS” badge.
🚀 Click here for full AWS SaaS Architecture guidelines.
Why is the “Deployed on AWS” badge important?
The Deployed on AWS badge helps customers understand that your solution runs on AWS and is eligible to be purchased through AWS Marketplace.
It also enables customers to apply their AWS spend commitment when buying your product through Marketplace.
🚀 For more details, see the AWS Spend Commitment section below.
AWS Spend Commitment
Can an AWS Partner apply its spend commitment toward purchases made through the AWS Marketplace?
Yes. AWS customers can apply their AWS spend commitment toward purchasing your product through AWS Marketplace, as long as:
The purchase is made directly through AWS Marketplace, and
Your listing displays the “Deployed on AWS” badge, confirming it runs on AWS infrastructure.
There are no additional requirements beyond these.
What is an AWS spend commitment?
An AWS spend commitment is an agreement between AWS and a customer in which the customer commits to spending a minimum amount on AWS services over a defined period (typically one to three years).
Purchases made through AWS Marketplace count toward this commitment, making listings with the “Deployed on AWS” badge more attractive to buyers who have existing spend commitments with AWS.
Why is this important for sellers?
Ensuring your listing has the “Deployed on AWS” badge helps customers apply their AWS spend commitment toward your product purchase, which can simplify procurement and accelerate deal approvals.
Labra User Roles
What types of roles can be assigned to Labra users?
Labra supports two primary user roles for managing AWS Marketplace listings and offers:
Owner/Admin (user)
Staff (viewer)
Each role has defined permissions to ensure appropriate access and control.
What can Owner/Admin users do?
Owner/Admin users have full access to the Labra account and can:
Add and manage users
Update account-level settings
Create and manage Marketplace listings
Create and manage Private Offers and Agreement-Based Offers (ABOs)
Edit existing Marketplace listings
What can Staff users do?
Staff users can:
View Marketplace listings and offers
Track the status of Private Offers and agreements
Staff users cannot:
Modify account-level settings
Add or remove users
Make changes to listings or offers
Who should be assigned as an Owner/Admin?
Owner/Admin roles should be assigned to primary business or technical contacts responsible for Marketplace strategy, account configuration, and user management.
Who should be assigned as Staff?
Staff roles are well-suited for sales, operations, or support team members who need visibility into Marketplace activity but do not require administrative access.
Private Offers and Agreement-Based Offers (ABO)
Can I create private offers without accessing the AWS Marketplace portal?
Yes. Sellers can create, manage, and cancel private offers directly from the Labra platform without logging into the AWS Marketplace Management Portal.
What types of Marketplace offers are supported?
Labra supports the following AWS Marketplace offer types:
Private Offers
Agreement-Based Offers (ABOs)
Future-dated offers
Channel Partner Private Offers (CPPOs)
Availability may vary depending on product type and AWS Marketplace policies.
Can I track the lifecycle of a private offer?
Yes. Sellers can track private offer status as it progresses through key stages, such as:
Sent
Viewed
Accepted
What’s the difference between an ABO and a Private Offer?
Private Offer (PO): Creates a new contract for a customer who does not have an active subscription for the product.
Agreement-Based Offer (ABO): Updates an existing contract for a customer who already has an active subscription for the product.
When should I use a Private Offer?
Use a Private Offer when:
The customer has no active subscription for the product
You are selling the product to the customer for the first time
When should I use an Agreement-Based Offer (ABO)?
Use an ABO when:
The customer already has an active subscription
You need to add Professional Services
You are upselling, changing scope, or adjusting pricing
You are modifying terms of an existing agreement
📒 Note: ABOs cannot be used to change billing frequency or payment schedules once an agreement has been accepted.
Why can’t I create a new Private Offer for an existing customer?
AWS Marketplace allows only one active subscription per buyer per product. When a subscription already exists, AWS requires changes to be handled through an ABO, not a new Private Offer.
Why does AWS say my previous offer was “replaced” after submitting an ABO?
This is expected behavior. AWS Marketplace only allows one active subscription per buyer per product. When you submit an Agreement-Based Offer (ABO), AWS technically marks the previous offer as replaced, but the subscription itself is not canceled or removed.
Does this mean my original SaaS offer no longer exists?
No. The original SaaS subscription remains active. The ABO updates the existing agreement rather than creating a new, parallel contract.
What does an ABO actually do?
An Agreement-Based Offer amends the current active contract. It is used to:
Add Professional Services
Increase scope or usage
Adjust pricing or terms
Upsell or modify an existing agreement
All changes are applied under the same product and customer subscription.
Why can’t I create a second Private Offer for the same customer?
AWS Marketplace enforces a one-subscription-per-product-per-customer rule. If a customer already has an active subscription for a product, AWS will block the creation of a new Private Offer. Any commercial changes must be handled via an ABO.
When should I use a Private Offer vs. an ABO?
Private Offer: Used when there is no active subscription for the product
Agreement-Based Offer (ABO): Used when a customer already has an active subscription and you need to modify it
Can billing terms be changed after a Private Offer is accepted?
No. Once a Private Offer is accepted in AWS Marketplace, the payment schedule is locked and cannot be changed via an Agreement-Based Offer (ABO), even if the customer has not yet been billed.
AWS Marketplace does not allow amendments to modify billing structure (for example, changing from upfront payment to annual installments) after acceptance.
What should I do if billing terms need to change before the customer is billed?
If the customer has not yet been billed, AWS Marketplace recommends a cancel and replace approach:
The buyer cancels the existing agreement in the AWS Marketplace console
The seller creates a new Private Offer with the correct billing structure
The buyer accepts the new offer
This ensures the agreement is created with the correct payment terms from the start.
Can an Agreement-Based Offer (ABO) be used to change billing frequency or payment schedule?
No. Agreement-Based Offers cannot be used to change payment schedules.
ABOs can be used to:
Add or remove dimensions
Increase quantities or scope
Extend the contract end date
Adjust pricing or add Professional Services
Billing structure (upfront vs. installments) cannot be changed once an agreement is accepted.
Where are active AWS Marketplace agreements canceled?
Active AWS Marketplace agreements can only be canceled directly by the buyer through the AWS Marketplace Management Portal (console).
They cannot be canceled via an amendment or outside of the console.
Will the customer see multiple contracts?
No. The customer continues to see one contract with updated terms reflecting the ABO.
Usage Metering
How can I submit usage metering through Labra for Marketplace?
Sellers can submit usage metering directly from the Labra platform. Once logged in, sellers can:
Navigate to the product listing
Select the relevant contract for the buyer
Enter usage values for the applicable dimensions
Submit the usage for reporting
Labra submits the metering data to AWS Marketplace on the seller’s behalf.
How do I define a metering plan?
A metering plan is defined by specifying:
The unit of measure (for example, users, API calls, or data volume)
Pricing associated with each unit
The metrics used to track consumption
The metering plan forms the basis for usage tracking and billing in AWS Marketplace.
What metrics can be used for usage metering?
Metrics vary based on the nature of the SaaS product. Common metrics include:
Number of users or seats
Data volume processed or stored
API calls or transactions
Compute or runtime usage
Metrics must be measurable, consistent, and aligned with the product’s value model.
How frequently should usage data be reported?
Usage data is typically reported on a recurring basis, such as daily or monthly. The reporting frequency depends on the pricing model and AWS Marketplace requirements.
Can I update my metering plan after it is defined?
Yes. Sellers can update their metering plans to reflect changes in pricing models, metrics, or product structure, subject to AWS Marketplace review and approval where required.
What is the AWS Marketplace Metering Service API used for?
The AWS Marketplace Metering Service API is used to submit usage data to AWS Marketplace. It enables automated reporting of customer consumption and supports usage-based billing.
Can customers view their usage and billing information?
Yes. Customers can view usage and billing information through their AWS Management Console, providing transparency into consumption and charges.
What are the benefits of usage metering in AWS Marketplace?
Usage metering enables:
Flexible pricing based on actual consumption
Greater transparency for buyers
Alignment between product value and cost
Support for scalable, consumption-based SaaS models
Can customers set up budgets and alerts for AWS Marketplace usage?
Yes. Customers can use AWS budgeting and alerting tools to monitor Marketplace usage and spending.
Are there any restrictions on the types of software that can use usage metering?
Most SaaS products can use usage metering, provided they comply with AWS Marketplace guidelines. Sellers should review AWS documentation to confirm eligibility for their specific product type.
What happens if a customer exceeds their subscribed usage limits?
Sellers can define overage behavior as part of their pricing and metering model. This may include additional charges or usage caps, depending on how the product is configured.
Is AWS Marketplace usage metering available in all AWS regions?
AWS Marketplace usage metering is available in multiple regions. Availability may vary depending on the product type and region configuration.
Usage dimensions vs. contract dimensions: what’s the difference?
Usage dimensions and contract dimensions serve different purposes:
Usage dimensions
Track actual product consumption
Used for usage-based pricing and reporting
Optional but recommended for visibility and optimization
Contract dimensions
Define financial commitments and subscription terms
Used for billing, forecasting, and compliance
Required for contract-based pricing models
Using both provides a complete view of usage and commercial commitments.
How do API identifiers work?
API identifiers are internal names used by AWS to track pricing dimensions.
Maximum length: 15 characters
Case-sensitive
Must use underscores instead of spaces
Example:
Product name: Cloud Marketplace Management (Contract)
API identifier:
flyout_mgmt_contract
Revenue Insights
How do I set up data feeds in Labra for Marketplace?
Setting up data feeds allows Labra to retrieve billing and disbursement data from AWS Marketplace for reporting purposes.
To configure data feeds:
Sign in to the AWS Marketplace Management Portal using an account with admin access
Log in to the Labra platform
Navigate to Settings → App settings
Select the Labra FlyOut tab and locate the Cloud settings section
In the Data Feeds step, launch the AWS CloudFormation stack
-
Create the stack by providing:
Stack name
S3 bucket name
SNS topic name
Wait for the stack status to reach CREATE_COMPLETE
Copy the output values from the CloudFormation stack
Paste the values into the corresponding fields in Labra and save
Note: Once data feeds are configured, it can take up to 24 hours for revenue and disbursement data to appear, as AWS updates this data once per day.
[Insert figure – outdated]
How can I access Revenue Insights?
Revenue Insights is available from the seller interface within the Labra platform. Navigate to the Revenue Insights section to view financial and usage-related reporting.
What data is included in the financial performance graphs?
Revenue Insights includes AWS Marketplace financial data such as:
Revenue
Disbursements
Usage-related financial metrics
The data is sourced from AWS Marketplace reporting feeds.
Can I customize the time range for reports?
Yes. Sellers can customize reporting periods to view data by specific time ranges, such as daily, weekly, or monthly.
How does Revenue Insights support pricing and forecasting decisions?
Revenue Insights provides visibility into revenue and usage trends, helping sellers:
Understand product performance over time
Forecast revenue and disbursements
Evaluate the impact of pricing models and usage patterns
Can I download reports for further analysis?
Yes. Sellers can download detailed reports for offline analysis and record keeping.
How frequently is Revenue Insights data updated?
Revenue Insights uses the same underlying data source as AWS Marketplace financial reporting. Updates from AWS may be delayed by up to 48 hours.
Can I report on invoices, collections, and disbursements?
Yes. Revenue Insights provides visibility into:
Invoices raised
Disbursed and undistributed amounts
Payment status by customer and date
Reports can be downloaded for further analysis.
Can I view expected and collected cash by customer?
Yes. Sellers can view collected and expected cash amounts by customer over time, supporting forecasting and financial planning.
Can I track contract end dates for renewal planning?
Yes. Revenue Insights allows sellers to view active contracts along with their end dates. This helps sellers plan renewals and monitor upcoming expirations.
Events and Notifications
Who on my team will receive email notifications for Marketplace events?
Sellers can configure which team members receive email notifications for Marketplace-related events. Multiple stakeholders can be selected, and notification recipients can vary depending on the event type.
Many sellers use shared distribution lists to ensure visibility across teams.
Which Slack channels can receive notifications?
Sellers can choose one or more Slack channels within their workspace to receive Marketplace event notifications, provided Slack integration is configured.
Are there additional events for which notifications can be enabled?
AWS Marketplace only provides a defined set of events to sellers. Notifications are limited to the events AWS makes available.
What happens if the webhook experiences downtime?
If a webhook experiences temporary downtime, Labra retries event delivery for a limited period. Events are retained during retry attempts to reduce the risk of missed notifications.
I received a “Payment failure for an AWS Marketplace agreement” email, but the agreement ID does not match any of our records. Why?
Payment failure notifications are sent by AWS when a buyer’s payment method cannot be processed. In these cases:
The agreement is not active
The buyer must update their payment method and re-accept the offer
Common reasons for payment failures include:
Missing, invalid, or unsupported payment methods
Payment declined by the buyer
Account restrictions related to specific AWS billing entities
Invoicing requirements not met for scheduled payments
Once the buyer resolves the payment issue, the agreement can proceed.
Will I be notified when a private offer is accepted?
Yes. Sellers receive notifications when a private offer is accepted. Notifications can be delivered via email and Slack, depending on configuration.
Can I receive notifications before a contract expires?
Yes. Sellers can receive notifications ahead of contract expiration dates, as well as notifications when a contract has expired.
This helps ensure timely renewal and follow-up actions.
Propensity to Buy
What’s the best way to upload my Prospects list for Propensity to Buy?
We recommend using the Sample file available in the Labra UI—it’s preformatted and must be uploaded in .csv format to ensure smooth processing.
Is there anything specific I should keep in mind while formatting the file?
Yes, please ensure the column containing your prospects is titled "prospect" (all lowercase). Also, avoid including any duplicate entries—either within the same list or across previously uploaded lists—to maintain clean and accurate results.
Miscellaneous and best practices
How can I grant EventBridge access for AWS Marketplace events?
AWS uses Amazon EventBridge to communicate Marketplace buyer and agreement events to sellers.
To enable this, sellers must deploy the required AWS CloudFormation template in their AWS account. This grants permission for AWS Marketplace to send supported events.
This setup allows Marketplace events to be received reliably and supports notification workflows.
Why do I need to add mp-notification@labra.io to my AWS Marketplace notification settings?
Adding this email address ensures that certain Marketplace events—such as offer acceptance—can be captured when AWS does not emit a corresponding event immediately.
This helps ensure:
Timely status updates
Accurate synchronization of Marketplace activity
If this email is not added, some Marketplace-driven updates may be delayed.
How do I enable “Demo” and “Request a Private Offer” buttons on my AWS listing?
AWS Marketplace allows sellers to enable “Request a Demo” and “Request a Private Offer” buttons on eligible listings.
When enabled:
Buyers can submit requests directly from the listing page
AWS routes the request to the seller for follow-up
These buttons help streamline buyer engagement and procurement.
[Insert figure – outdated]
Where can I see the status of my AWS Marketplace listing?
Sellers can check listing status in two places:
Labra platform – to track listing progress prior to and during AWS review
AWS Marketplace Management Portal – once the listing is submitted to AWS
AWS Marketplace provides real-time status updates as listings move through review and approval.
[Insert figure – outdated]
How long does it take for an AWS Marketplace listing to be approved?
After listing creation is complete, the process typically follows two stages:
Pre-submission validation to ensure AWS requirements are met
AWS review and testing, which occurs based on AWS queue availability
AWS does not provide a fixed SLA. Based on typical experience, full approval can take several weeks, depending on listing complexity and testing requirements.
How can I raise a support request with AWS Marketplace?
If you need assistance from AWS Marketplace, you can submit a support request through the AWS Marketplace Management Portal:
Sign in to the AWS Marketplace Management Portal
Select Contact Us
Complete the support request form with relevant details
Providing request IDs, product IDs, or error messages helps AWS resolve issues more efficiently.
How do I add or remove users after onboarding?
To manage users:
Go to Settings
Select User Management
Add users by entering their email address and assigning a role
Remove users by selecting the user and choosing Delete
Changes take effect immediately.
[Insert figure – outdated]
How do I cancel an ongoing AWS Marketplace subscription?
Subscription management is handled directly in AWS Marketplace.
Canceling a SaaS subscription
Open the AWS Marketplace console
Navigate to Manage subscriptions
Select SaaS as the delivery method
Choose the subscription
Under Actions, select Cancel subscription
Confirm the cancellation
Canceling auto-renewal
Open the subscription’s product detail page
Select Continue
Go to Modify renewal
Choose Cancel renewal