Hosting Wordpress in a EC2 Load Balanced Instance
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Whenever my ec2 instance is stopped or rebooted, a new instance is made with an AMI.
This normally is fine for applications that are managed with a service like puppet but our Wordpress site is not. I have to do a manual restore/upgrade to the latest wordpress from daily backups.
Is there a way to host wordpress on an amazon instance with some kind of persistence storage for the wordpress files?
I know about EBS volumes but I'm not sure how to get /var/app/current to "store there".
amazon-ec2 wordpress
asked 7 hours ago
bobber205bobber205
1761415
add a comment |
Whenever my ec2 instance is stopped or rebooted, a new instance is made with an AMI.
This normally is fine for applications that are managed with a service like puppet but our Wordpress site is not. I have to do a manual restore/upgrade to the latest wordpress from daily backups.
Is there a way to host wordpress on an amazon instance with some kind of persistence storage for the wordpress files?
I know about EBS volumes but I'm not sure how to get /var/app/current to "store there".
amazon-ec2 wordpress
asked 7 hours ago
bobber205bobber205
1761415
add a comment |
Whenever my ec2 instance is stopped or rebooted, a new instance is made with an AMI.
This normally is fine for applications that are managed with a service like puppet but our Wordpress site is not. I have to do a manual restore/upgrade to the latest wordpress from daily backups.
Is there a way to host wordpress on an amazon instance with some kind of persistence storage for the wordpress files?
I know about EBS volumes but I'm not sure how to get /var/app/current to "store there".
amazon-ec2 wordpress
asked 7 hours ago
bobber205bobber205
1761415
Whenever my ec2 instance is stopped or rebooted, a new instance is made with an AMI.
This normally is fine for applications that are managed with a service like puppet but our Wordpress site is not. I have to do a manual restore/upgrade to the latest wordpress from daily backups.
Is there a way to host wordpress on an amazon instance with some kind of persistence storage for the wordpress files?
I know about EBS volumes but I'm not sure how to get /var/app/current to "store there".
amazon-ec2 wordpress
amazon-ec2 wordpress
asked 7 hours ago
bobber205bobber205
1761415
asked 7 hours ago
bobber205bobber205
1761415
edited 7 hours ago
bobber205
asked 7 hours ago
bobber205bobber205
1761415
asked 7 hours ago
bobber205bobber205
1761415
asked 7 hours ago
bobber205bobber205
1761415
1761415
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You should be using EFS volumes for shared storage, like the wp-content folder, and RDS for the database. EBS won't help you for this.
AWS has a good pattern available here. It links to templates and such on Github here.
There's another pattern available here as well that gives you a full deployment guide.
Lightsail
AWS is great for Wordress if you need high availability or have a very high load. AWS Lightsail makes Wordpress easy, though not highly available, and it can be much cheaper than EC2 especially if you use a lot of bandwidth.
answered 6 hours ago
TimTim
18k41949
Thanks so much!!!!!
– bobber205
5 hours ago
add a comment |
Stab in the dark here:
Whenever my ec2 instance is stopped or rebooted, a new instance is made with an AMI.
Most likely your EC2 instance is controlled by Auto Scaling. So when the instance is stopped, Auto Scaling determines that it's "unhealthy", terminates it, then replaces it. That's why you're losing your data.
To avoid this, create a new EC2 instance that's not controlled by Auto Scaling. This way, you can start and stop it without it being replaced. The EBS volume will retain the data through the stops and restarts.
Is there a way to host wordpress on an amazon instance with some kind of persistence storage for the wordpress files?
EBS-backed EC2 instances do provide the persistent storage you're looking for. However, I think the issue is that the act of stopping the EC2 instance is terminating and re-creating the instance.
answered 5 hours ago
Matt HouserMatt Houser
7,7791518
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962097%2fhosting-wordpress-in-a-ec2-load-balanced-instance%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You should be using EFS volumes for shared storage, like the wp-content folder, and RDS for the database. EBS won't help you for this.
AWS has a good pattern available here. It links to templates and such on Github here.
There's another pattern available here as well that gives you a full deployment guide.
Lightsail
AWS is great for Wordress if you need high availability or have a very high load. AWS Lightsail makes Wordpress easy, though not highly available, and it can be much cheaper than EC2 especially if you use a lot of bandwidth.
answered 6 hours ago
TimTim
18k41949
Thanks so much!!!!!
– bobber205
5 hours ago
add a comment |
You should be using EFS volumes for shared storage, like the wp-content folder, and RDS for the database. EBS won't help you for this.
AWS has a good pattern available here. It links to templates and such on Github here.
There's another pattern available here as well that gives you a full deployment guide.
Lightsail
AWS is great for Wordress if you need high availability or have a very high load. AWS Lightsail makes Wordpress easy, though not highly available, and it can be much cheaper than EC2 especially if you use a lot of bandwidth.
answered 6 hours ago
TimTim
18k41949
Thanks so much!!!!!
– bobber205
5 hours ago
add a comment |
You should be using EFS volumes for shared storage, like the wp-content folder, and RDS for the database. EBS won't help you for this.
AWS has a good pattern available here. It links to templates and such on Github here.
There's another pattern available here as well that gives you a full deployment guide.
Lightsail
AWS is great for Wordress if you need high availability or have a very high load. AWS Lightsail makes Wordpress easy, though not highly available, and it can be much cheaper than EC2 especially if you use a lot of bandwidth.
answered 6 hours ago
TimTim
18k41949
You should be using EFS volumes for shared storage, like the wp-content folder, and RDS for the database. EBS won't help you for this.
AWS has a good pattern available here. It links to templates and such on Github here.
There's another pattern available here as well that gives you a full deployment guide.
Lightsail
AWS is great for Wordress if you need high availability or have a very high load. AWS Lightsail makes Wordpress easy, though not highly available, and it can be much cheaper than EC2 especially if you use a lot of bandwidth.
answered 6 hours ago
TimTim
18k41949
answered 6 hours ago
TimTim
18k41949
answered 6 hours ago
TimTim
18k41949
answered 6 hours ago
TimTim
18k41949
18k41949
Thanks so much!!!!!
– bobber205
5 hours ago
add a comment |
Thanks so much!!!!!
– bobber205
5 hours ago
Thanks so much!!!!!
– bobber205
5 hours ago
Thanks so much!!!!!
– bobber205
5 hours ago
add a comment |
Stab in the dark here:
Whenever my ec2 instance is stopped or rebooted, a new instance is made with an AMI.
Most likely your EC2 instance is controlled by Auto Scaling. So when the instance is stopped, Auto Scaling determines that it's "unhealthy", terminates it, then replaces it. That's why you're losing your data.
To avoid this, create a new EC2 instance that's not controlled by Auto Scaling. This way, you can start and stop it without it being replaced. The EBS volume will retain the data through the stops and restarts.
Is there a way to host wordpress on an amazon instance with some kind of persistence storage for the wordpress files?
EBS-backed EC2 instances do provide the persistent storage you're looking for. However, I think the issue is that the act of stopping the EC2 instance is terminating and re-creating the instance.
answered 5 hours ago
Matt HouserMatt Houser
7,7791518
add a comment |
Stab in the dark here:
Whenever my ec2 instance is stopped or rebooted, a new instance is made with an AMI.
Most likely your EC2 instance is controlled by Auto Scaling. So when the instance is stopped, Auto Scaling determines that it's "unhealthy", terminates it, then replaces it. That's why you're losing your data.
To avoid this, create a new EC2 instance that's not controlled by Auto Scaling. This way, you can start and stop it without it being replaced. The EBS volume will retain the data through the stops and restarts.
Is there a way to host wordpress on an amazon instance with some kind of persistence storage for the wordpress files?
EBS-backed EC2 instances do provide the persistent storage you're looking for. However, I think the issue is that the act of stopping the EC2 instance is terminating and re-creating the instance.
answered 5 hours ago
Matt HouserMatt Houser
7,7791518
add a comment |
Stab in the dark here:
Whenever my ec2 instance is stopped or rebooted, a new instance is made with an AMI.
Most likely your EC2 instance is controlled by Auto Scaling. So when the instance is stopped, Auto Scaling determines that it's "unhealthy", terminates it, then replaces it. That's why you're losing your data.
To avoid this, create a new EC2 instance that's not controlled by Auto Scaling. This way, you can start and stop it without it being replaced. The EBS volume will retain the data through the stops and restarts.
Is there a way to host wordpress on an amazon instance with some kind of persistence storage for the wordpress files?
EBS-backed EC2 instances do provide the persistent storage you're looking for. However, I think the issue is that the act of stopping the EC2 instance is terminating and re-creating the instance.
answered 5 hours ago
Matt HouserMatt Houser
7,7791518
Stab in the dark here:
Whenever my ec2 instance is stopped or rebooted, a new instance is made with an AMI.
Most likely your EC2 instance is controlled by Auto Scaling. So when the instance is stopped, Auto Scaling determines that it's "unhealthy", terminates it, then replaces it. That's why you're losing your data.
To avoid this, create a new EC2 instance that's not controlled by Auto Scaling. This way, you can start and stop it without it being replaced. The EBS volume will retain the data through the stops and restarts.
Is there a way to host wordpress on an amazon instance with some kind of persistence storage for the wordpress files?
EBS-backed EC2 instances do provide the persistent storage you're looking for. However, I think the issue is that the act of stopping the EC2 instance is terminating and re-creating the instance.
answered 5 hours ago
Matt HouserMatt Houser
7,7791518
answered 5 hours ago
Matt HouserMatt Houser
7,7791518
answered 5 hours ago
Matt HouserMatt Houser
7,7791518
answered 5 hours ago
Matt HouserMatt Houser
7,7791518
7,7791518
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962097%2fhosting-wordpress-in-a-ec2-load-balanced-instance%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
