Replacing Awssome's managed integration with the AWS open-source reference. Read this before you decide.
Your listing is live. Your revenue is flowing. This guide covers exactly what changes — technically and operationally — if you swap Awssome's managed integration for the AWS open-source Serverless SaaS Integration reference.
March 2026 | Version 1.0
You are live on AWS Marketplace with your own seller account and your own SaaS listing. Awssome provides the technical integration layer that powers your listing: subscriber registration, entitlement management, metering, and lifecycle event processing.
This guide covers what happens if you replace Awssome's managed integration with the AWS open-source Serverless SaaS Integration reference, which you would deploy and operate yourself.
Whether Awssome or you manage it, the Marketplace integration handles four things:
| Component | What It Does |
|---|---|
| Subscriber Registration | Buyer subscribes → redirected to landing page → token resolved → subscriber record created. |
| Entitlement Management | For contracts, checks and stores what each customer is entitled to. |
| Lifecycle Events | AWS sends SNS notifications on subscribe, unsubscribe, renew, or entitlement changes. |
| Metering | For usage-based listings, collects usage records and reports them to AWS's BatchMeterUsage API every hour. |
This is the section that matters. Read every item. If any of these makes you uncomfortable, stay with managed.
The AWS infrastructure cost is effectively zero. That is not the issue.
ISVs who self-service consistently underestimate total cost by 5–10x. Here is why.
| Resource | Cost |
|---|---|
| Lambda (6–8 functions) | $0.00 |
| API Gateway | $0.00 |
| DynamoDB (on-demand) | $0.00–$0.01 |
| SQS + SNS + EventBridge | $0.00 |
| CloudFront + S3 | $0.01 |
| CloudWatch Logs | $0.01–$0.03 |
| Total Infrastructure | < $1 / month |
| Item | Estimate |
|---|---|
| AWS infrastructure | < $1/month |
| Monitoring & maintenance | €200–600/mo |
| Incident response | €400–1,200/incident |
| Knowledge ramp-up | €2,000–5,000 |
| Year 1 Total | €5,000–€15,000 |
Most ISVs who self-service underestimate the human cost by 5–10x because they only look at the AWS bill. The AWS bill is irrelevant. The engineering time is what costs money.
If you've read everything above and still want to self-service, here's the deployment guide.
Repository: github.com/aws-samples/aws-marketplace-serverless-saas-integration
| Feature | Details |
|---|---|
| AWS-maintained | Built by the AWS Marketplace team. |
| Serverless | Lambda, API Gateway, DynamoDB, SQS, SNS. No servers. |
| SAM-based | One command deploys everything. |
| All pricing models | Contracts, subscriptions, contracts-with-subscription. |
| It's what Awssome extends | Same core mechanics. |
Follow these in order. Each step includes what you configure and what breaks if you skip it.
Log into your AWS Marketplace Management Portal. Go to AMMP → Products → Your SaaS Listing.
| Parameter | Where |
|---|---|
| ProductId | Product summary page |
| TypeOfSaaSListing | Pricing tab (contracts / subscriptions / contracts_with_subscription) |
| MarketplaceTechAdminEmail | Your ops email — receives lifecycle notifications |
| MarketplaceSellerEmail | SES-verified email — must be in SES production mode |
| WebsiteS3BucketName | Globally unique name — only if using built-in landing page |
git clone https://github.com/aws-samples/aws-marketplace-serverless-saas-integration.git cd aws-marketplace-serverless-saas-integration sam build sam deploy --guided --capabilities CAPABILITY_NAMED_IAM
When prompted, provide your values:
| Parameter | Your Value |
|---|---|
| Stack Name | my-marketplace-integration |
| AWS Region | eu-west-1 |
| ProductId | prod-abc123def456 |
| TypeOfSaaSListing | contracts_with_subscription |
| MarketplaceTechAdminEmail | ops@yourcompany.com |
| MarketplaceSellerEmail | marketplace@yourcompany.com |
| WebsiteS3BucketName | my-company-mp-registration |
Wait for the stack to complete (3–5 minutes).
Check the inbox of your MarketplaceTechAdminEmail for an email from AWS Notifications. Click "Confirm subscription".
aws cloudformation describe-stacks \ --stack-name YOUR_STACK_NAME \ --query "Stacks[0].Outputs"
You can also find these in CloudFormation → Stacks → Outputs. Save the MarketplaceFulfillmentUrl and RedirectUrl.
If using the built-in page (CreateRegistrationWebPage = true):
web/script.js: Replace baseUrl with RedirectUrl from Step 4.RedirectUrl environment variable.If using your own custom page: Update your page to POST to the new /subscriber API Gateway endpoint.
Do this BEFORE telling Awssome to decommission.
| # | Test | Verify | How |
|---|---|---|---|
| 1 | Subscribe | Buyer can subscribe | Use separate AWS account |
| 2 | Registration | Token resolves correctly | Complete registration form |
| 3 | DynamoDB | Subscriber record created | Check AWSMarketplaceSubscribers table |
| 4 | Notification | Admin email received | Check inbox + spam |
| 5 | Entitlement | Correct data returned | Call Entitlement API |
| 6 | Metering | Record processes | Insert record, trigger Lambda |
| 7 | Cancellation | Handled correctly | Cancel from buyer console |
The reference does NOT include monitoring. Without these, failures are silent.
aws cloudformation delete-stack --stack-name YOUR_STACK_NAME
Do not go live without completing every item.
sam build + sam deploy completedNot sure? That's a sign you should stay with managed.
