Migrate, Clone or Transfer sites to AWS in 4 simple steps. Once migrated this software allows you to easily manage AWS Hosting via your WordPress interface. View your site on AWS today absolutely FREE! No AWS Cloud expertise required.
Get Free Licence Key Simply Click Here to get a licence key to use the plugin today. Clone any site now to see your site in AWS for Free! No license fees or AWS usage charges will apply. Trial instances stay active for 6 hours after launch.
AWS Trial User Guide Link to AWS Labs
AWS User Guide Link to Self Managed User Guide
YOUR WORDPRESS AWS MANAGEMENT ASSISTANT
What does it do?
WP on AWS provides an AWS data transfer & architecture build solution through a simple to navigate interface and a control panel to easily manage the site’s AWS infrastructure once transferred. No AWS Cloud Knowledge Required
Who is this plugin for?
This plugin is primarily aimed at WordPress Webmasters (Site Owners), Developers & Agencies
v.2.3.* v.2 Self-Managed Solution release: Nov 30, 2020 Link to Self Managed Tutorial
v.3.2.* v.3 Self-Managed Solution release: Jun 02, 2022 WCEU 22
v.4.1.* v.4 Self-Managed Solution extended functionality release: Oct 14, 2022
v.5.0.* v.5 Self-Managed Solution upgraded media transfer release: Jun 08, 2023 WCEU 23
To install this plugin:
- Upload the entire ‘wp-migrate-2-aws’ folder to the ‘/wp-content/plugins/’ directory
- Activate the plugin through the ‘Plugins’ menu in WordPress
அடிக்கடி கேட்கப்படும் கேள்விகள்
Do I need my own AWS Account?
You do not need an AWS account to run a trial clone. A self-manage licence however requires an AWS account as this is where the instance will be built. Seahorse offers an account creation service for users if required.
Where are Trial clones created?
Trial instances are created in our Seahorse / AWS environment.
Why is there no option to select another Region?
Trials are restricted to the eu-west-1 (Ireland) region only. Users have the option to select any of the Lightsail regions however when using a production licence
Does your software support multisite networks?
No, the software does not currently allow migration or management of WordPress multisite. Multisite support is part of our development roadmap however and will be delivered later in 2021.
For how long are trial clones active?
Trial instances are active for 6 hours after launch.
Can I log into the Trial clone instance and make changes?
No, the trial instance is for front-end review only and access to the WordPress admin of the site is restricted.
What plan level is the Trial instance running on?
Trial instances are launched on the $10 Lightsail plan. More information on plan types can be found here: https://aws.amazon.com/lightsail/pricing/. On production licenses the initial migration is also launched on the $10 plan but users are free from there to scale up/down as they wish
பங்களிப்பாளர்கள் & உருவாக்குனர்கள்
“WP on AWS” is open source software. The following people have contributed to this plugin.பங்களிப்பாளர்கள்
Translate “WP on AWS” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
- feature – #74 updated default launch instance size
- feature – #58 updates to “create staging” functionality
- feature – #59 added user specific links to interface
- bugfix – #67 patched Coderatio library and improved db-prefix compatibility
- feature – #56 updated functionality to identify & isolate large database tables and uploads
- feature – #50 added new functionality to allow for instance size selection at launch
- feature – #54 added new functionality to support ‘clone’, ‘staging’, and ‘upgrade’. Including new user interface, menus and navigation pages
- bugfix – #51 error handling on licence validation check
- fix – #39 updated error handling on remote API calls
- feature – #43 include global constants for URLs
- feature – #44 added “restart” button and relocated existing “reset all” button
- feature – #45 include option to run process over http
- feature – #32 updated launch-success view layout & contents
- bugfix – #35 switch-off multi-site support
- feature – #36 updated configuration for remote manage API
- fix – #37 removed check for amazon polly plugin conflict
- testing – #38 tested to WordPress version 5.9
- fix – #41 updates to text, image, and external links on launch screen
- Added SNS Alert if Remote Connection Fails
- updated configuration for remote migration API
- updated configuration for remote manage API
- fixed error message display for the buckets not found
- added instance launch time & removed ip from final screen
- error output bug fix
- include tables dir by default
- No functional changes
- No functional changes
- bug fix – add empty required directory
- notice for self managed user about instance size
- License version displayed in welcomePanel
- major release: moving code to remote API
- ls naming conventions bug fix
- Add bucket name sanitization (trial users)
- Conflict alert when ‘AWS for WordPress’ 4.3.1 enabled (temporary)
- further automation of the trial management process
- if get_object_vars() disabled alternative
- bug fix at clone (post release)
- wp 5.7 test minor release
- S3 Management inc. bucket exists check
- Update to text related to self-managed process
- closing region selection on trial
- major release: self managed model
- after launch process edit
- run DB process as a background process
- menu display debug (permissions – isolated case)
- release from beta
- interface styling upgrade (part 2)
- plugin interface styling upgrade
- minor bug fix – incompatibility with plugins
- minor bug fix (Key Pair creation)
- introducing remote logging
- wp-5.5 compatibility testing
- initial license management
- activating large file isolation
- large file bypass and vendor conflict fix applied
- patch applied to guest login issue
- major release: upgraded migration process & management dashboard (beta)
- minor edits and introduction of SNS logging
- promoting admin migration process as default
- manual extract method added (admin)
- expansion of managed migration service
- dynamic process display
- improvement in the handling of process failures
- Update to transfer process to allow for interruptions to PHP