Scnapper takes scheduled backups of your EC2 instances and EBS volumes, keeps them under a retention policy you set, and starts and stops EC2 instances on a schedule to reduce cost.
Scnapper is a backup, recovery and runtime scheduling appliance that runs as one EC2 instance in your own AWS account. It takes snapshots of your EBS volumes and images of your EC2 instances on hourly, daily, weekly, monthly or yearly schedules, keeps them under a retention policy per group, and lets you recover from any of them in the web interface. Its runtime scheduler starts and stops EC2 instances on a schedule, so development, test and office-hours workloads are not billed around the clock. Every scheduled event publishes an SNS notification.
Version 4.0.0 is a rebuild on Ubuntu 24.04 LTS with MySQL 8.0, PHP 8.3 and OpenJDK 21. It is launched from a CloudFormation template that creates the IAM role, the security group and a data volume that survives the instance, so upgrades reattach your data. You log in with a username and password chosen at first-time setup; no AWS access keys are entered or stored, and every password and key is generated on your own instance. Schedules can be edited in place. Scnapper 3.x installations migrate with a one-time export and import.
Documentation: user guide, Getting Started guide and release notes are linked under Additional resources.
Highlights
Reduces your AWS cost by managing your snapshots and the runtime of your EC2 instances. It runs in your AWS account.
Easy to use UI to manage your snapshots during recovery/restore and scheduling START/STOP of your EC2 Instances
Email/SMS notifications ensure that your backups are occurring on schedule
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.
You pay by the hour based on the type of EC2 instance you run the software on. Each dimension maps to a specific instance type, such as compute-optimized (c-family), general purpose (m-family), storage-optimized (i-family), or burstable (t-family) options. Larger and newer instance families carry their own hourly rate. This is usage-based pricing tied to runtime, not to the number of resources you back up or schedule. You select the instance type that fits your workload, and billing follows the hours that instance runs the software.
Top-of-mind questions for buyers
What does the hourly charge cover, and is it based on how many resources I back up?
The hourly charge covers running the software on one EC2 instance. Pricing is usage-based and tied to instance runtime, not the number of EBS volumes or EC2 instances you back up or schedule. You pay for each hour the chosen instance runs the software.
Am I charged when the instance running the software is stopped?
The software charge meters running time on the selected instance. When that instance is stopped, software hours stop accruing. Note that stored backups and snapshots may still incur separate underlying AWS storage fees, which are billed by AWS and not part of this software's hourly rate.
How do I choose between the different instance-type dimensions?
Each dimension maps to one EC2 instance type across compute-optimized (c-family), general purpose (m-family), storage-optimized (i-family), and burstable (t-family) options. You pick the instance type that fits your workload. Only the type you run the software on generates charges; you are not billed for the others.
www.28-right.com
Helpful?
Vendor refund policy
We do not currently support refunds, but you can cancel at any time.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
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.
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
SCNAPPER 4.0.0 - RELEASE NOTES
Scnapper 4.0.0 is a rebuild of the Scnapper appliance on a current, supported
platform. It takes scheduled backups of your EC2 instances and EBS volumes,
keeps them under your retention policies, and starts and stops EC2 instances
on a runtime schedule, as before. Everything in this release ships in one
image; there is no partial adoption.
NEW IN 4.0.0
New platform. Ubuntu 24.04 LTS replaces Ubuntu 14.04. The appliance runs
MySQL 8.0, PHP 8.3, Apache 2.4 and OpenJDK 21, all as Ubuntu packages that
unattended-upgrades keeps patched.
Launch from a CloudFormation template. The template published with the AMI
creates the security group, the IAM role the instance runs with, an
encrypted root volume that is deleted with the instance, and an encrypted
data volume (/dev/sdb, mounted at /files) that holds your database,
configuration, logs and TLS material and survives the stack. You no longer
create a role or a policy by hand.
Username and password login. You log in with a username and password
chosen at first-time setup. The setup form asks for a setup token, which is
the instance ID; Scnapper reads its own instance ID and accepts the setup
only when they match. AWS access keys are no longer entered or stored; the
instance acts through its IAM role.
Edit a schedule in place. Click Edit on a schedule's row in Manage
Schedules, or Edit Schedule on its detail page. The form opens pre-filled
with the schedule, its start and end dates, the retention policy and the
reboot flags, in your configured time zone. Previously a schedule had to be
deleted and created again.
Upgrades that keep your data. From 4.0.0 onwards an upgrade launches the
new version's template with ExistingDataVolumeId set to your data volume.
First boot applies any database changes and comes up with your users,
groups and schedules. No export or import is needed.
Export and import. The Profile page has an Export / Import function that
moves every group, schedule, retention policy and backup history between
instances as one file. It is how a Scnapper 3.x installation moves to
4.0.0 (see UPGRADING FROM SCNAPPER 3.x).
Notifications. The SNS topic name is configurable in Properties
Configuration (default Scnapper-28Right). Scnapper creates the topic
itself the first time it publishes in a region; you only add
subscriptions. Every scheduled event publishes a message saying whether it
succeeded or failed.
Clearer status. Manage Groups and Manage Schedules show when a change is
still pending with the scheduler and when a schedule could not be applied.
GovCloud. Scnapper 4.0.0 is available in AWS GovCloud (US-West and
US-East) as well as in the commercial regions.
SECURITY
4.0.0 closes the security findings of the 3.x code base:
Every password, encryption key and TLS key pair is generated on your own
instance at first boot. The image carries no secret, no default password
and no key shared with any other customer.
The login and session handling are rewritten: no authentication bypass, no
empty credentials accepted, and CSRF protection on every form.
All input is validated and all output escaped; the SQL injection and
cross-site scripting findings are fixed.
The instance role grants only the actions Scnapper uses. The instance
requires IMDSv2. The scheduler runs sandboxed under systemd with no
capabilities.
Port 80 only redirects to HTTPS. The self-signed certificate is generated
on the instance and can be replaced with your own.
No GPL-only JavaScript ships in the web interface; every third-party
component is MIT licensed.
BUG FIXES
Notifications never arrived: SNS messages were published to a topic that
could not exist. Notifications now reach the configured topic in every
region, including GovCloud.
Scheduler resilience: a database error no longer stops the scheduler, a
failed schedule no longer deletes your rows, and a restart no longer fires
every schedule at once. A schedule that cannot be applied is shown as an
error instead of being retried silently.
AMI backups: the wait for an AMI to become available is bounded, and
deregistering an AMI under a retention policy now deletes its snapshots as
well.
Schedule times: start and end dates are converted to UTC with the offset in
force on that date, so a date on the other side of a daylight-saving change
is no longer an hour off.
UPGRADING FROM SCNAPPER 3.x
A 3.x data volume cannot be attached to a 4.0.0 instance: 4.0.0 runs MySQL 8,
which cannot open the 3.x database. If one is attached anyway, nothing is
destroyed; the old database is set aside on the volume and a banner asks you
to import. The supported path is a one-time export and import:
Take a snapshot of the 3.x data volume.
Install the Scnapper export patch on the 3.x instance (download and
checksum are in the listing) and export from Profile.
Launch 4.0.0 from the CloudFormation template with a new data volume and
complete first-time setup.
Import the file on the Profile page under Export / Import, verify your
groups and schedules, then retire the 3.x instance.
OTHER CHANGES
The Middle East (Bahrain) region is not offered in 4.0.0; it returns in a
later template update.
Only current-generation instance types are offered: t3.small, t3.medium,
t3.large, t3a.small, t3a.medium, t3a.large, m6i.large, m6a.large and
c6i.large. t3.medium is the recommended size.
The instance is reachable over SSH as snapusr with the key pair chosen at
launch.
KNOWN ISSUES
If some backups miss their schedule or snapshots and AMIs are not retained
as configured, you may be hitting the AWS API request limit. The scheduler
log (/files/logs/scnapper-backend.log) shows "RequestLimitExceeded" when
this happens. Workaround: lower the Number of threads in Properties
Configuration, or spread schedules over different minutes.
If you launch the AMI directly instead of the CloudFormation template, you must attach an IAM instance profile with the EC2 snapshot, image, volume, instance and tag actions plus SNS publish, attach a second EBS volume as /dev/sdb for the data, and open 443 (and 22 from your address). The CloudFormation delivery option does all of this for you. Launch with the CloudFormation template (recommended): it creates the IAM role, the security group and the data volume the appliance needs. When the stack is complete, open https://<public IP>/tool/ (the URL output), accept the self-signed certificate once, and complete the first-time setup: the setup token is the instance ID (the InstanceId output), then choose a username and password. Log in with those. SSH as snapusr with the key pair chosen at launch. Getting Started guide: https://scnapper-getting-started.s3.amazonaws.com/Scnapper%20Getting%20Started-4.0.0.pdf ; user guide: https://scnapper-getting-started.s3.amazonaws.com/Scnapper%20User%20Guide-4.0.0.pdf
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.
SimpleBackups offers automated, secure, and reliable cloud backup and recovery solutions designed for businesses of all sizes. Our platform ensures seamless data protection with features like automated backups, easy recovery, and robust encryption. Simplify your cloud data management with SimpleBackups.
Automated backup and instant recovery for SaaS applications: GitHub, GitLab, Jira, Confluence, Trello, Notion, and Shopify. Setup in minutes with no scripting. Daily automated backups, 256-bit AES encryption, data residency options (US/UK/EU/AU). ISO 27001, SOC2, GDPR & HIPAA compliant. Built on AWS.
A ready-to-run Python container for Amazon ECS and EKS that automates multi-region AWS cost optimizations.This utility is designed to identify and manage multiple cost optimizations, such as deleting unattached disks, removing idle ALBs, and cleaning up unused Elastic IPs across all AWS regions. Operating within a containerized environment, the tool can either display a list of resources for manual review or proceed with their deletion, based on your configuration. The application is developed in Python and is easy to deploy on Amazon ECS or EKS
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.