<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WordPress Migration Archives - Ian Necor</title>
	<atom:link href="https://www.iannecor.com/tag/wordpress-migration/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.iannecor.com/tag/wordpress-migration/</link>
	<description>Web Developer Manila, Philippines</description>
	<lastBuildDate>Wed, 18 Nov 2026 14:20:24 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.5</generator>

<image>
	<url>https://www.iannecor.com/wp-content/uploads/2026/10/ian_necor_site_icon_512-100x100.png</url>
	<title>WordPress Migration Archives - Ian Necor</title>
	<link>https://www.iannecor.com/tag/wordpress-migration/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Migrating a WordPress Website from AWS Lightsail to EC2</title>
		<link>https://www.iannecor.com/case-studies/migrating-a-wordpress-website-from-aws-lightsail-to-ec2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=migrating-a-wordpress-website-from-aws-lightsail-to-ec2</link>
		
		<dc:creator><![CDATA[Ian Necor]]></dc:creator>
		<pubDate>Wed, 18 Nov 2026 14:15:23 +0000</pubDate>
				<category><![CDATA[AWS & Cloud]]></category>
		<category><![CDATA[Blog]]></category>
		<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Amazon CloudFront]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Amazon RDS]]></category>
		<category><![CDATA[AWS Cloud Infrastructure]]></category>
		<category><![CDATA[AWS Lightsail]]></category>
		<category><![CDATA[AWS WAF]]></category>
		<category><![CDATA[Server Management]]></category>
		<category><![CDATA[WordPress hosting]]></category>
		<category><![CDATA[WordPress Migration]]></category>
		<guid isPermaLink="false">https://www.iannecor.com/?p=2381</guid>

					<description><![CDATA[<p>As a WordPress website grows, its hosting infrastructure needs to [&#8230;]</p>
<p>The post <a href="https://www.iannecor.com/case-studies/migrating-a-wordpress-website-from-aws-lightsail-to-ec2/">Migrating a WordPress Website from AWS Lightsail to EC2</a> appeared first on <a href="https://www.iannecor.com">Ian Necor</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">As a WordPress website grows, its hosting infrastructure needs to evolve alongside its traffic, functionality, and operational requirements. What works well for a smaller website may eventually become restrictive when additional websites, plugins, integrations, and server workloads are introduced.</p>



<p class="wp-block-paragraph">This case study documents a migration from Amazon Lightsail to Amazon Elastic Compute Cloud (EC2), moving toward a more flexible AWS infrastructure designed to support growing WordPress hosting requirements.</p>



<p class="wp-block-paragraph">The project involved more than simply transferring website files. It required planning the server environment, preparing the application stack, considering database architecture, configuring network access, and introducing additional AWS services to support delivery, security, and scalability.</p>



<h2 class="wp-block-heading">Project Overview</h2>



<p class="wp-block-paragraph"><strong>Project:</strong> WordPress infrastructure migration</p>



<p class="wp-block-paragraph"><strong>Source environment:</strong> Amazon Lightsail</p>



<p class="wp-block-paragraph"><strong>Destination environment:</strong> Amazon EC2</p>



<p class="wp-block-paragraph"><strong>Application:</strong> WordPress</p>



<p class="wp-block-paragraph"><strong>Infrastructure:</strong> AWS EC2, Amazon RDS, Amazon CloudFront, and AWS WAF</p>



<p class="wp-block-paragraph"><strong>Primary objective:</strong> Establish a more flexible and scalable hosting environment for growing website requirements.</p>



<h2 class="wp-block-heading">1. The Challenge: Outgrowing the Existing Hosting Environment</h2>



<p class="wp-block-paragraph">Amazon Lightsail provides a convenient way to deploy and manage websites without having to configure every aspect of the underlying AWS infrastructure. For smaller WordPress installations, it can be an effective and straightforward hosting solution.</p>



<p class="wp-block-paragraph">However, the hosting requirements began to change as more websites and workloads were introduced into the environment.</p>



<p class="wp-block-paragraph">The existing infrastructure was supporting multiple websites, and adding more installations began creating operational and resource-management challenges. The concern was no longer just whether the websites could run, but whether the environment could accommodate future growth without becoming increasingly difficult to manage.</p>



<p class="wp-block-paragraph">Several considerations influenced the decision to move toward EC2:</p>



<ul class="wp-block-list">
<li><strong>Scalability:</strong> The need for more flexibility when allocating and adjusting computing resources.</li>



<li><strong>Infrastructure control:</strong> Greater control over server configuration, operating system components, and application services.</li>



<li><strong>Multi-site management:</strong> Better options for managing multiple WordPress installations and their individual workloads.</li>



<li><strong>Performance management:</strong> More control over PHP, database, caching, and server-level optimization.</li>



<li><strong>Future expansion:</strong> The ability to introduce additional AWS services as infrastructure requirements evolve.</li>
</ul>



<p class="wp-block-paragraph">The objective was to establish a hosting environment that could support more demanding workloads while providing greater control over the underlying infrastructure.</p>



<h2 class="wp-block-heading">2. Why Amazon EC2?</h2>



<p class="wp-block-paragraph">Amazon EC2 provides virtual server instances with configurable computing, memory, storage, and networking resources. Unlike a simplified hosting environment, EC2 provides more direct control over the server and how applications are deployed.</p>



<p class="wp-block-paragraph">This flexibility was particularly relevant for a WordPress environment that required more than basic website hosting.</p>



<p class="wp-block-paragraph">Moving to EC2 made it possible to manage the server stack more directly, including:</p>



<ul class="wp-block-list">
<li>Operating system and server configuration.</li>



<li>Apache web server and PHP configuration.</li>



<li>PHP-FPM process management.</li>



<li>Database connectivity and optimization.</li>



<li>Storage allocation and management.</li>



<li>Network access and security group configuration.</li>



<li>Integration with other AWS infrastructure services.</li>
</ul>



<p class="wp-block-paragraph">The selected EC2 environment provided a more capable foundation for managing the growing workload and allowed additional infrastructure components to be introduced independently.</p>



<h2 class="wp-block-heading">3. Preparing the Migration</h2>



<p class="wp-block-paragraph">Before moving the WordPress installation, the existing hosting environment needed to be reviewed. A migration without proper preparation can introduce broken links, missing files, database inconsistencies, email problems, or extended downtime.</p>



<p class="wp-block-paragraph">The preparation process focused on identifying the application components and services that needed to be preserved.</p>



<h3 class="wp-block-heading">Website and database assessment</h3>



<ul class="wp-block-list">
<li>Review WordPress core, themes, plugins, and custom code.</li>



<li>Identify website files, uploads, and media directories.</li>



<li>Review database size, tables, users, and database configuration.</li>



<li>Identify scheduled tasks, cron jobs, and background processes.</li>



<li>Review PHP versions and required extensions.</li>



<li>Document domain, DNS, SSL, and email configurations.</li>



<li>Identify external integrations and services that depend on the existing server.</li>
</ul>



<h3 class="wp-block-heading">Backup and recovery planning</h3>



<p class="wp-block-paragraph">A complete backup of the website files and database is essential before migration. The backup provides a recovery point if the new environment encounters problems during deployment or testing.</p>



<p class="wp-block-paragraph">For WordPress installations, this includes the complete application files, uploaded media, configuration files, database contents, and any additional files required by custom functionality.</p>



<h2 class="wp-block-heading">4. Building the New EC2 Environment</h2>



<p class="wp-block-paragraph">After preparing the migration, the next step was to establish the destination server environment.</p>



<p class="wp-block-paragraph">EC2 provided the flexibility to configure the operating system and application stack according to the requirements of the WordPress installation.</p>



<h3 class="wp-block-heading">Server configuration</h3>



<p class="wp-block-paragraph">The server environment was configured around the components required to run WordPress:</p>



<ul class="wp-block-list">
<li><strong>Linux operating system:</strong> Providing the underlying server environment.</li>



<li><strong>Apache:</strong> Handling incoming web requests and serving website content.</li>



<li><strong>PHP:</strong> Executing WordPress and its associated application code.</li>



<li><strong>PHP-FPM:</strong> Managing PHP application processes and resource allocation.</li>



<li><strong>Database connectivity:</strong> Connecting WordPress to its database service.</li>



<li><strong>SSL/TLS:</strong> Supporting encrypted HTTPS connections.</li>
</ul>



<p class="wp-block-paragraph">Server configuration also required attention to PHP limits, process management, file permissions, storage, and network access.</p>



<h3 class="wp-block-heading">PHP-FPM and resource management</h3>



<p class="wp-block-paragraph">PHP-FPM configuration is particularly important for WordPress installations because it controls how PHP processes handle incoming requests.</p>



<p class="wp-block-paragraph">Parameters such as maximum child processes, start servers, and spare servers need to be configured according to available memory, workload, and application requirements.</p>



<p class="wp-block-paragraph">Setting these values too low can limit request processing capacity. Setting them too high can consume excessive memory and contribute to resource contention.</p>



<p class="wp-block-paragraph">The appropriate configuration should be determined through monitoring and workload testing rather than relying on generic values.</p>



<h2 class="wp-block-heading">5. Moving Database Workloads to Amazon RDS</h2>



<p class="wp-block-paragraph">As part of the broader infrastructure architecture, Amazon Relational Database Service (RDS) was introduced to provide a managed database environment separate from the EC2 application server.</p>



<p class="wp-block-paragraph">This approach separates the WordPress application layer from the database layer, making it possible to manage database resources independently of the web server.</p>



<h3 class="wp-block-heading">Benefits of separating the database</h3>



<ul class="wp-block-list">
<li><strong>Independent resource management:</strong> Database resources can be configured separately from the EC2 instance.</li>



<li><strong>Managed database operations:</strong> RDS provides managed capabilities for supported database engines.</li>



<li><strong>Infrastructure separation:</strong> The application server does not need to host the database service locally.</li>



<li><strong>Security controls:</strong> Database access can be restricted through network and security group configuration.</li>



<li><strong>Future flexibility:</strong> Database capacity and configuration can be reviewed independently as workloads change.</li>
</ul>



<p class="wp-block-paragraph">One important consideration is database connectivity. The EC2 instance must be able to communicate with the RDS instance through the appropriate network configuration, and the database should not be exposed unnecessarily to the public internet.</p>



<p class="wp-block-paragraph">Database migration also requires careful validation of character sets, database users, permissions, connection settings, and WordPress configuration.</p>



<h2 class="wp-block-heading">6. Introducing Amazon CloudFront</h2>



<p class="wp-block-paragraph">Another component of the infrastructure was Amazon CloudFront, AWS&#8217;s content delivery network (CDN).</p>



<p class="wp-block-paragraph">CloudFront helps deliver content through a distributed network of edge locations. It can reduce the distance between website visitors and cached content, potentially improving delivery performance for users accessing a website from different geographical locations.</p>



<p class="wp-block-paragraph">For a WordPress website, CloudFront can be configured to deliver suitable static assets such as:</p>



<ul class="wp-block-list">
<li>Images and media files.</li>



<li>CSS stylesheets.</li>



<li>JavaScript files.</li>



<li>Fonts and other static resources.</li>
</ul>



<p class="wp-block-paragraph">CloudFront configuration requires careful consideration of cache policies, origin settings, HTTPS, cookies, query strings, and WordPress administrative paths.</p>



<p class="wp-block-paragraph">Dynamic WordPress pages and authenticated sessions generally require different caching behavior from static resources. Incorrect caching rules can cause outdated content, login issues, or unexpected website behavior.</p>



<h2 class="wp-block-heading">7. Adding AWS WAF for Web Application Protection</h2>



<p class="wp-block-paragraph">As the infrastructure evolved, AWS Web Application Firewall (WAF) was introduced as another layer of protection.</p>



<p class="wp-block-paragraph">AWS WAF helps inspect and control incoming web requests based on configured rules. It can be used to implement protections such as rate limiting, request filtering, and managed rule groups.</p>



<p class="wp-block-paragraph">For a public WordPress website, these capabilities can help address unwanted traffic and reduce exposure to certain common web-based threats.</p>



<h3 class="wp-block-heading">Security considerations</h3>



<ul class="wp-block-list">
<li>Configure rate-based rules to control excessive request volumes.</li>



<li>Review managed rule groups for compatibility with the website.</li>



<li>Monitor blocked and allowed requests before making aggressive rule changes.</li>



<li>Avoid rules that unintentionally block legitimate visitors or search engine crawlers.</li>



<li>Review logs and adjust rules based on actual traffic patterns.</li>
</ul>



<p class="wp-block-paragraph">WAF is not a replacement for WordPress security, server hardening, or application updates. It is one layer within a broader security strategy.</p>



<h2 class="wp-block-heading">8. Migration Validation and Testing</h2>



<p class="wp-block-paragraph">Once the destination environment was prepared, the migration needed to be validated before directing normal website traffic to the new infrastructure.</p>



<p class="wp-block-paragraph">A successful migration is not simply a website loading on a new server. The application, database, integrations, and supporting services must work together correctly.</p>



<h3 class="wp-block-heading">Website functionality</h3>



<ul class="wp-block-list">
<li>Confirm that the homepage and important internal pages load correctly.</li>



<li>Test WordPress administration and user authentication.</li>



<li>Verify images, media files, and downloads.</li>



<li>Test forms, search functionality, and other interactive features.</li>



<li>Review custom code, plugins, and third-party integrations.</li>
</ul>



<h3 class="wp-block-heading">Infrastructure validation</h3>



<ul class="wp-block-list">
<li>Confirm Apache and PHP-FPM are running correctly.</li>



<li>Verify database connectivity and permissions.</li>



<li>Check HTTPS and SSL/TLS certificate configuration.</li>



<li>Review DNS records and the destination server configuration.</li>



<li>Test CloudFront origin connectivity and caching behavior.</li>



<li>Validate AWS WAF rules and ensure legitimate traffic is not blocked.</li>



<li>Monitor server resources and application error logs.</li>
</ul>



<p class="wp-block-paragraph">Testing should also include a review of scheduled tasks, email delivery, and any external service that relies on the website&#8217;s domain or server configuration.</p>



<h2 class="wp-block-heading">9. Challenges Encountered After Migration</h2>



<p class="wp-block-paragraph">Moving to a more flexible infrastructure also introduces additional operational responsibilities. EC2 provides greater control, but that control requires ongoing server administration, monitoring, and security management.</p>



<p class="wp-block-paragraph">Several areas require particular attention in a WordPress environment running on EC2.</p>



<h3 class="wp-block-heading">Resource utilization</h3>



<p class="wp-block-paragraph">High CPU and memory utilization can affect application responsiveness. PHP-FPM and database processes are particularly important to monitor when a website receives concurrent requests or runs resource-intensive plugins.</p>



<h3 class="wp-block-heading">Database performance</h3>



<p class="wp-block-paragraph">Moving the database to a separate service changes how WordPress communicates with its database. Network connectivity, query efficiency, database resources, and connection limits all need to be considered.</p>



<h3 class="wp-block-heading">CloudFront and caching behavior</h3>



<p class="wp-block-paragraph">CDN configuration can introduce unexpected issues when cache policies are not aligned with WordPress behavior. Administrative pages, authenticated sessions, and dynamic content need appropriate handling.</p>



<h3 class="wp-block-heading">Firewall and security rules</h3>



<p class="wp-block-paragraph">Security rules must protect the infrastructure without interfering with normal website functionality. Security groups, WAF rules, and application-level security controls should be reviewed together.</p>



<p class="wp-block-paragraph">These considerations demonstrate why infrastructure migration should be treated as an ongoing engineering and operational process rather than a one-time server transfer.</p>



<h2 class="wp-block-heading">10. The Result: A More Flexible AWS Infrastructure</h2>



<p class="wp-block-paragraph">The migration established a more flexible infrastructure foundation by moving away from the original Lightsail hosting environment and introducing additional AWS services.</p>



<p class="wp-block-paragraph">The resulting architecture separated key responsibilities across the infrastructure:</p>



<ul class="wp-block-list">
<li><strong>Amazon EC2:</strong> Hosting the WordPress application and server environment.</li>



<li><strong>Amazon RDS:</strong> Providing a separate managed database service.</li>



<li><strong>Amazon CloudFront:</strong> Supporting content delivery and caching.</li>



<li><strong>AWS WAF:</strong> Providing an additional layer of request filtering and protection.</li>
</ul>



<p class="wp-block-paragraph">This architecture provides more options for resource allocation, infrastructure management, security controls, and future expansion.</p>



<p class="wp-block-paragraph">Rather than relying on a single hosting environment to handle every responsibility, the infrastructure can be managed as a collection of services with distinct roles.</p>



<p class="wp-block-paragraph">The migration was an infrastructure and scalability improvement. No specific percentage improvement in page speed, uptime, or search rankings is claimed here because those results require comparative measurements before and after the migration.</p>



<h2 class="wp-block-heading">11. Key Lessons from the Migration</h2>



<p class="wp-block-paragraph">There are several important lessons for businesses and developers considering a similar move from Lightsail to EC2.</p>



<h3 class="wp-block-heading">1. Plan the architecture before moving the website</h3>



<p class="wp-block-paragraph">Understand the existing application, its dependencies, resource requirements, and future needs before selecting the destination environment.</p>



<h3 class="wp-block-heading">2. Separate application and database responsibilities when appropriate</h3>



<p class="wp-block-paragraph">A separate database service can provide more flexibility, but it also introduces network, connection, and cost considerations that need to be managed.</p>



<h3 class="wp-block-heading">3. Monitor actual resource usage</h3>



<p class="wp-block-paragraph">CPU, memory, PHP-FPM processes, database performance, and server response times should be monitored regularly. Infrastructure decisions should be based on actual workloads.</p>



<h3 class="wp-block-heading">4. Treat caching as part of the architecture</h3>



<p class="wp-block-paragraph">Page caching, browser caching, and CDN configuration should work together. Incorrect cache settings can be just as problematic as having no caching strategy.</p>



<h3 class="wp-block-heading">5. Security needs multiple layers</h3>



<p class="wp-block-paragraph">Security groups, WAF, HTTPS, operating system updates, WordPress hardening, access controls, and backups all contribute to a more resilient environment.</p>



<h3 class="wp-block-heading">6. Migration does not end when DNS changes</h3>



<p class="wp-block-paragraph">After launch, continue monitoring server health, application errors, database performance, email delivery, and website functionality. Some problems only become visible under normal production traffic.</p>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">Migrating a WordPress website from Amazon Lightsail to EC2 is an opportunity to rethink how the website is hosted, managed, secured, and scaled.</p>



<p class="wp-block-paragraph">For this project, the move provided a foundation for a more flexible AWS architecture incorporating EC2, RDS, CloudFront, and AWS WAF.</p>



<p class="wp-block-paragraph">While EC2 introduces additional server administration responsibilities, it also provides greater control over the infrastructure and more options for managing growing website requirements.</p>



<p class="wp-block-paragraph">The most important takeaway is that hosting should evolve with the application. Choosing the right infrastructure is not just about obtaining more computing resources; it is about building an environment that can be maintained, monitored, secured, and expanded as business requirements change.</p>
<p>The post <a href="https://www.iannecor.com/case-studies/migrating-a-wordpress-website-from-aws-lightsail-to-ec2/">Migrating a WordPress Website from AWS Lightsail to EC2</a> appeared first on <a href="https://www.iannecor.com">Ian Necor</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
