Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 7 of 7 total |
Connecting to EDB server on AWS EC2 Instance |
Wed, Oct 10 2018 12:36 PM | Permanent Link |
Charles Bainbridge | I have an EDB server up and running on an AWS EC2 Windows server instance, and can run my application on the EC2 server instance accessing the EDB service via the instance host name - in an RDP remote desktop session in the same server.
However, I cannot connect to the EDB server across the internet using EDB Manager. I get error 10060 on attempting to connect. I have inbound rules on the server firewall to allow ports 12010 and 12011 through (I have two EDB services installed). This works for 'normal' domain-based implementations of the application. I have opened the rules up to allow inbound connection from anywhere (I think), but still error 10060. Any ideas for me? |
Wed, Oct 10 2018 1:48 PM | Permanent Link |
Raul Team Elevate | On 10/10/2018 12:36 PM, Charles Bainbridge wrote:
> I have inbound rules on the server firewall to allow ports 12010 and 12011 through (I have two EDB services installed). This works for 'normal' domain-based implementations of the application. I have opened the rules up to allow inbound connection from anywhere (I think), but still error 10060. > > Any ideas for me? yes - you also have to allow firewall on EC2 control panel. There are basically 2 sets of firewalls at play - ec2 ones and host ones (host is the windows firewall you did allow already). Look for "Network and Security" and "Security Groups" on AWS EC2 console Raul |
Thu, Oct 11 2018 5:00 AM | Permanent Link |
Matthew Jones | And also, be very careful about security - making a raw database accessible on the internet is generally not a good thing to do...
-- Matthew Jones |
Thu, Oct 11 2018 5:25 AM | Permanent Link |
Charles Bainbridge | "Raul" wrote:- Look for "Network and Security" and "Security Groups" on AWS EC2 console. Oh, thanks! "Matthew Jones" wrote:- And also, be very careful about security - making a raw database accessible on the internet is generally not a good thing to do... A very good point. TBH, it was more an academic exercise, having only started fiddling with AWS a few hours beforehand. |
Tue, Oct 16 2018 1:52 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Matthew,
<< And also, be very careful about security - making a raw database accessible on the internet is generally not a good thing to do... >> It will be a lot easier to manage this once I get TLS support included in EDB. It's in EWB 3 at the socket layer, so I will be moving it over to EDB soon. Surprisingly enough, I can't see much of a performance difference between TLS and non-TLS connections. Tim Young Elevate Software www.elevatesoft.com |
Thu, Feb 16 2023 10:22 PM | Permanent Link |
Ian Branch | Hi Charles,
I am curious how this all went. One of my Customers is making overtures to AWS and wants me to consider moving his Apps and Databases to AWS. Thoughts/comments/experiences if you would. Regards & TIA, Ian |
Fri, Feb 17 2023 11:55 AM | Permanent Link |
Adam Brett Orixa Systems | Hi Charles Bainbridge
I use EDB on AWS. It is not that hard to do. Raul is right, you have to set up Network Security settings on the AWS control panel. You also need to link your "instance" to an AWS Elastic IP Address (ie an IP address like 134.123.56.255) You then use this IP Address on the client side. Quite a while ago I wrote up a document about how to do this. I don't have time to re-write it for you ... but I think most things you need to set up to make the Instance work are in this document somewhere Attachments: 7. Amazon Server Creation.pdf |
This web page was last updated on Friday, April 19, 2024 at 07:09 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |