Sold by: Melrose Labs
Deployed on AWS
SMPP load balancer for high availability, reliability and capacity. Proxies SMPP traffic onto your SMS platforms using customer credentials.
Overview
The SMPP Load Balancer Proxy (SLBP) proxies SMPP submit_sm requests to your platforms. SMPP binds are made from the SLBP to your platforms using the customer's SMPP credentials, and only SMS traffic sent by that customer is routed to your platforms using their credentials. Delivery receipts and MO SMS are routed back to the customer as though they had directly connected to your platforms. No customer accounts need to be configured in the SLBP unless routing based on customer system ID. Only the host and port for each of your platforms are required to be configured in the SLBP.
Highlights
- Load balance SMS traffic from SMPP connections across multiple SMS gateways and SMSCs
- Up to 2000 SMS/sec throughput
- Monitoring via Prometheus/Grafana support
Details
Sold by
Categories
Delivery method
Delivery option
64-bit (x86) Amazon Machine Image (AMI)
Latest version
Operating system
AmazonLinux Amazon Linux 2023
Deployed on AWS
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Cost/hour |
|---|---|
t3.small Recommended | $0.30 |
Dimensions summary
You pay for the SMPP Load Balancer Proxy by the hour, based on running a t3.small instance. This is usage-based pricing tied to compute time rather than message volume or a fixed subscription. You are billed for each hour the instance runs. The single dimension covers one instance size, so your cost scales with how long you keep the instance active. Running more instances or longer hours increases your total charge accordingly.
Top-of-mind questions for buyers
You run one t3.small compute instance billed per hour. This configuration supports up to 1000 SMS per second and connects to as many as 50 upstream SMPP servers. TLS is optionally supported. You pay only for the hours the instance runs.
Hourly software charges apply only while the t3.small instance runs. If you stop the instance, the hourly software charge stops. Underlying AWS storage or other resource fees may still apply while the instance is stopped. Billing tracks running time, not message volume.
No. Your charge is based on instance-hours, not on how many messages you send. The t3.small instance supports up to 1000 SMS per second. Sending fewer or more messages within that limit does not change your hourly rate.
melroselabs.com
Helpful?
Vendor refund policy
Hourly subscriptions are not eligible for refunds, but you can cancel at any time.
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Updates between v1 and v2:
- Audit log and other logging enhancements
- Route by source address (regex or exact match)
- Regex modification of message content
- SAR ref number 16-bit to 8-bit
- Dynamic configuration changes
- IP whitelist file
- Bug fixes
Additional details
Usage instructions
The following example adds two target SMPP servers (smsc1.smpp.org and smsc2.smpp.org) to where each customer's SMS traffic will be load balanced.
- SSH to your SLBP instance (or use AWS EC2 Instance Connect from your browser) as user ec2-user.
- Add first target SMPP server: ./ec2MLSMPPLoadBalancer targetAdd smsc1 smsc1.smpp.org
- Add second target SMPP server: ./ec2MLSMPPLoadBalancer targetAdd smsc2 smsc2.smpp.org
- Restart the SLBP: sudo systemctl restart mlslbp
Your customers can now connect using SMPP to port 2775 on your SLBP instance.
Login to the SLBP configuration portal (GUI) at http://SLBHOST/portal . SLBHOST is the SLBP instance hostname. The credentials for using the GUI and API default to "slbpuser" for the client ID and the AWS EC2 instance ID for the password (e.g. i-092bxxe40xxc1f2xx).
Go to quickstart at https://melroselabs.scrollhelp.site/slbp/quick-start for further information.
Resources
Vendor resources
Support
Vendor support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
SMPP SMSC simulator to test SMS messaging applications.
Customer reviews
No customer reviews yet
Be the first to review this product . We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.