Otdfbt

How can powerful telekinesis avoid violating Newton's 3rd Law?

Should I list a completely different profession in my technical resume?

Makefile for a simple Debian Repo

That's not my X, its Y is too Z

How do I type a hyphen in iOS 12?

DateTime.addMonths skips a month (from feb to mar)

Am I allowed to determine tenets of my contract as a warlock?

Why do (or did, until very recently) aircraft transponders wait to be interrogated before broadcasting beacon signals?

Was planting UN flag on Moon ever discussed?

Was self-modifying code possible using BASIC?

C++ logging library

How does AFV select the winning videos?

Linked novellas where humans are engineered to adapt to a variety of environments

What do you call the action of "describing events as they happen" like sports anchors do?

Course development: can I pay someone to make slides for the course?

When to use и or а as “and”?

Why would a home insurer offer a discount based on credit score?

How to use the word seem

Convert GE Load Center to main breaker

In The Incredibles 2, why does Screenslaver's name use a pun on something that doesn't exist in the 1950s pastiche?

Suppose leased car is totalled: what are financial implications?

What exactly "triggers an additional time" in the interaction between Afterlife and Teysa Karlov?

Dedicated bike GPS computer over smartphone

If absolute velocity does not exist, how can we say a rocket accelerates in empty space?

Elastic Beanstalk - WordPress and Laravel using common RDS instance, is this ok?

Open ports between Elastic Beanstalk and one EC2 instance on AWSWhat are the pros and cons of AWS Elastic Beanstalk compared with other deployment strategies?How to associate an existing RDS instance to an Elastic Beanstalk environment?Amazon RDS instance and hostname resolutionPermissions for EC2 created by Elastic Beanstalk connecting to external RDSAccessing large app files using Elastic Beanstalk and Flask?High Memory Use on RDS Instance for Wordpress EnvironmentWordPress Docker container on Elastic Beanstalk not connecting to MariaDB containerCan't add RDS database to Elastic Beanstalk environmentWordPress admin pages timeout, or take 30s to load on Elastic Beanstalk, PHP 5.6, Apache, RDS, and CloudFlare

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

I'm working on a project that utilizes WordPress' admin front end to manage data, and a Laravel API that accesses the WP database (via Corcel) to return JSON/HTML/whatever.

I'd like to run these as separate apps within the same Elastic Beanstalk environment, connecting to the common RDS instance which sits outside of EB.

There are no problems at all getting the WP and Laravel apps up and running separately - following the AWS tutorials, I can get WP installed no problem, and I can get Laravel installed and the migrations to run.

I'm just struggling to figure out the "correct" way to hook them up to the common RDS instance I've already created. I can't seem to get the WordPress install to talk to RDS if I set up Laravel first, and vice versa. I've researched and tinkered with Security Groups but just can't get them to co-exist.

Without getting into the micro details, is what I've described workable, or is it crazy at a basic level? Should I just drop the idea of running them as separate apps and just have them running together? If anyone has a suggestion on a better/best approach to what I'm trying to do, I'd be extremely grateful.

amazon-web-services amazon-ec2 wordpress elastic-beanstalk amazon-rds

share|improve this question

asked May 28 at 7:40

Adam CramptonAdam Crampton

32

add a comment | 

0

I'm working on a project that utilizes WordPress' admin front end to manage data, and a Laravel API that accesses the WP database (via Corcel) to return JSON/HTML/whatever.

I'd like to run these as separate apps within the same Elastic Beanstalk environment, connecting to the common RDS instance which sits outside of EB.

There are no problems at all getting the WP and Laravel apps up and running separately - following the AWS tutorials, I can get WP installed no problem, and I can get Laravel installed and the migrations to run.

I'm just struggling to figure out the "correct" way to hook them up to the common RDS instance I've already created. I can't seem to get the WordPress install to talk to RDS if I set up Laravel first, and vice versa. I've researched and tinkered with Security Groups but just can't get them to co-exist.

Without getting into the micro details, is what I've described workable, or is it crazy at a basic level? Should I just drop the idea of running them as separate apps and just have them running together? If anyone has a suggestion on a better/best approach to what I'm trying to do, I'd be extremely grateful.

amazon-web-services amazon-ec2 wordpress elastic-beanstalk amazon-rds

share|improve this question

asked May 28 at 7:40

Adam CramptonAdam Crampton

32

add a comment | 

I'm working on a project that utilizes WordPress' admin front end to manage data, and a Laravel API that accesses the WP database (via Corcel) to return JSON/HTML/whatever.

I'd like to run these as separate apps within the same Elastic Beanstalk environment, connecting to the common RDS instance which sits outside of EB.

There are no problems at all getting the WP and Laravel apps up and running separately - following the AWS tutorials, I can get WP installed no problem, and I can get Laravel installed and the migrations to run.

I'm just struggling to figure out the "correct" way to hook them up to the common RDS instance I've already created. I can't seem to get the WordPress install to talk to RDS if I set up Laravel first, and vice versa. I've researched and tinkered with Security Groups but just can't get them to co-exist.

Without getting into the micro details, is what I've described workable, or is it crazy at a basic level? Should I just drop the idea of running them as separate apps and just have them running together? If anyone has a suggestion on a better/best approach to what I'm trying to do, I'd be extremely grateful.

amazon-web-services amazon-ec2 wordpress elastic-beanstalk amazon-rds

share|improve this question

asked May 28 at 7:40

Adam CramptonAdam Crampton

32

share|improve this question

asked May 28 at 7:40

Adam CramptonAdam Crampton

32

share|improve this question

asked May 28 at 7:40

Adam CramptonAdam Crampton

32

asked May 28 at 7:40

Adam CramptonAdam Crampton

32

asked May 28 at 7:40

Adam CramptonAdam Crampton

32

2 Answers
2

active

oldest

votes

0

Check your route tables. Most likely there is a route from the Elastic Beanstalk subnets to the RDS subnets missing.
From an infrastructure point of view this setup seems pretty standard.
For further debugging I would recommend to ssh to the WP instance and check with ping and MySQL client if the root cause is networking (Security Groups, route tables, NACLs) or something else for example authentication to RDS.

share|improve this answer

edited May 31 at 6:47

answered May 28 at 9:06

Henrik PingelHenrik Pingel

4,70021531

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thank you for the advice and confirming this is a pretty standard setup. I think you're 100% right as I was having trouble getting the WP instance to talk to RDS after SSH'ing in. I ended up scrapping the whole thing and starting again from scratch. Some careful attention to SGs and DB config along the way got me some success in the end, I now have end-to-end working. cheers
  
  – Adam Crampton
  May 31 at 6:09
  

  
  
  
  

add a comment | 

0

For testing. Create security group and add to this SG your EC2 and RDS instances. Add a inbound rule to this SG:
Protocol type:All
Protocol number:All
Ports: All
Source IP: The ID of this security group
It enables associated instances to communicate with each other.

share|improve this answer

answered May 28 at 8:58

PassatizhiPassatizhi

1

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That's a pretty expansive bypass rule you're proposing there - sorta the opposite of Least Privilege firewalling! Maybe there's a smaller exposure possible with a more directed set of rules?
  
  – TristanK
  May 28 at 22:40
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @TristanK I took that rule from aws doc. That suggestion is to verify that everything works. I mean apps work with rds instance. So there is SG issue and have to see into SG rules. Need to carefully make SG rules.
  
  – Passatizhi
  May 29 at 2:34
  

  
  
  
  

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
);



);

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969084%2felastic-beanstalk-wordpress-and-laravel-using-common-rds-instance-is-this-ok%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

0

Check your route tables. Most likely there is a route from the Elastic Beanstalk subnets to the RDS subnets missing.
From an infrastructure point of view this setup seems pretty standard.
For further debugging I would recommend to ssh to the WP instance and check with ping and MySQL client if the root cause is networking (Security Groups, route tables, NACLs) or something else for example authentication to RDS.

share|improve this answer

edited May 31 at 6:47

answered May 28 at 9:06

Henrik PingelHenrik Pingel

4,70021531

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thank you for the advice and confirming this is a pretty standard setup. I think you're 100% right as I was having trouble getting the WP instance to talk to RDS after SSH'ing in. I ended up scrapping the whole thing and starting again from scratch. Some careful attention to SGs and DB config along the way got me some success in the end, I now have end-to-end working. cheers
  
  – Adam Crampton
  May 31 at 6:09
  

  
  
  
  

add a comment | 

0

Check your route tables. Most likely there is a route from the Elastic Beanstalk subnets to the RDS subnets missing.
From an infrastructure point of view this setup seems pretty standard.
For further debugging I would recommend to ssh to the WP instance and check with ping and MySQL client if the root cause is networking (Security Groups, route tables, NACLs) or something else for example authentication to RDS.

share|improve this answer

edited May 31 at 6:47

answered May 28 at 9:06

Henrik PingelHenrik Pingel

4,70021531

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thank you for the advice and confirming this is a pretty standard setup. I think you're 100% right as I was having trouble getting the WP instance to talk to RDS after SSH'ing in. I ended up scrapping the whole thing and starting again from scratch. Some careful attention to SGs and DB config along the way got me some success in the end, I now have end-to-end working. cheers
  
  – Adam Crampton
  May 31 at 6:09
  

  
  
  
  

add a comment | 

Check your route tables. Most likely there is a route from the Elastic Beanstalk subnets to the RDS subnets missing.
From an infrastructure point of view this setup seems pretty standard.
For further debugging I would recommend to ssh to the WP instance and check with ping and MySQL client if the root cause is networking (Security Groups, route tables, NACLs) or something else for example authentication to RDS.

share|improve this answer

edited May 31 at 6:47

answered May 28 at 9:06

Henrik PingelHenrik Pingel

4,70021531

share|improve this answer

edited May 31 at 6:47

answered May 28 at 9:06

Henrik PingelHenrik Pingel

4,70021531

answered May 28 at 9:06

Henrik PingelHenrik Pingel

4,70021531

answered May 28 at 9:06

Henrik PingelHenrik Pingel

4,70021531

0

For testing. Create security group and add to this SG your EC2 and RDS instances. Add a inbound rule to this SG:
Protocol type:All
Protocol number:All
Ports: All
Source IP: The ID of this security group
It enables associated instances to communicate with each other.

share|improve this answer

answered May 28 at 8:58

PassatizhiPassatizhi

1

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That's a pretty expansive bypass rule you're proposing there - sorta the opposite of Least Privilege firewalling! Maybe there's a smaller exposure possible with a more directed set of rules?
  
  – TristanK
  May 28 at 22:40
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @TristanK I took that rule from aws doc. That suggestion is to verify that everything works. I mean apps work with rds instance. So there is SG issue and have to see into SG rules. Need to carefully make SG rules.
  
  – Passatizhi
  May 29 at 2:34
  

  
  
  
  

add a comment | 

0

For testing. Create security group and add to this SG your EC2 and RDS instances. Add a inbound rule to this SG:
Protocol type:All
Protocol number:All
Ports: All
Source IP: The ID of this security group
It enables associated instances to communicate with each other.

share|improve this answer

answered May 28 at 8:58

PassatizhiPassatizhi

1

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That's a pretty expansive bypass rule you're proposing there - sorta the opposite of Least Privilege firewalling! Maybe there's a smaller exposure possible with a more directed set of rules?
  
  – TristanK
  May 28 at 22:40
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @TristanK I took that rule from aws doc. That suggestion is to verify that everything works. I mean apps work with rds instance. So there is SG issue and have to see into SG rules. Need to carefully make SG rules.
  
  – Passatizhi
  May 29 at 2:34
  

  
  
  
  

add a comment | 

For testing. Create security group and add to this SG your EC2 and RDS instances. Add a inbound rule to this SG:
Protocol type:All
Protocol number:All
Ports: All
Source IP: The ID of this security group
It enables associated instances to communicate with each other.

share|improve this answer

answered May 28 at 8:58

PassatizhiPassatizhi

1

share|improve this answer

answered May 28 at 8:58

PassatizhiPassatizhi

1

answered May 28 at 8:58

PassatizhiPassatizhi

1

answered May 28 at 8:58

PassatizhiPassatizhi

1