I got AWS running an instance of the AMI service using this ami-80347097 from the Realm website. So I have the EC2 instance up now, but I don't know what to do next. Sorry I'm completely new to this sort of thing.
What would be the server URL for the AWS Instance? And would the admin access token for the Object Server still be the same? Or would I have to do something specific in the EC2 Instance?
TT.TT
EDIT:
Ok so I got the Object dashboard to actually work and I am able to log in.
Thank you very much for helping me with that. My last step is actually getting connected to the Object Server. What would the Server URL for the Object Server be?
I tried using the realm://public URL:9080 for the server URL and got this error Realm Sync Error
Server Connection Problem
Assuming that you have successfully initiated the ami-80347097 instance with realm-object-server service running. At this point make sure you have enabled the 9080 port in your inbound rules section. This is necessary because you are going to access the realm object dashboard with the port enabled.
Steps:
Goto EC2 Dashboard
Select "Securit Group" under "Network & Security"
Click on the security group you have been using for the ami-80347097 instance
Once you have clicked the security group a configuration tab "Description", "Inbound", "Outbound", "Tags" will appear at the bottom of the screen
Add the port 9080 in your Inbound section as a Custom TCP Rule
Once you are done doing this,
Open a new browser window and go to http://localhost:9080. The login page for the Realm Dashboard will be displayed. Remember to replace localhost with the IP address of your server.
Related
I have a Spring boot project which I want to host on an AWS-EC2 instance. I was able to create its image using Git-hub, Jenkin and docker. I was also able to successfully pull and run this image in the Linux console of my AWS-EC2 instance.
According the tutorial I was following I should have been able to open the project now using the public IPv4 DNS but the response I got was that it refuse to connect.
I know that this usually has to do with Inbound rules so I added a rule to allow all traffic but it didn't help.
For anyone who wants to know:
Git-hub repository: https://github.com/SalahuddinShayan/telecom
Docker-Hub repository: https://hub.docker.com/repository/docker/salahuddinshayan/telecom
Command I used to run the image in AWS:
docker run -p8081:8081 --name final-app --link docker-mysql:mysql salahuddinshayan/telecom
Security Groups:
Networking Details:
Here is the Error:
I am completely stumped by it. Does anyone an idea on what to do to fix this?
Please check if your client is calling the right protocol, e.g. http vs https.
You are transmitting on port 8081. http://3.110.29.193:8081/ works fine from the EC2 side. 404 status is raised, so this is a client side error, not a server side error.
It means that no firewall is blocking traffic and a process (your app) was found that listens on IP:Port that you require. The problem is that the process it encountered (your app) is sending only a WhiteLabel Error Page, which is a generic Spring Boot error page that is displayed when no custom error page is present. So the issue is with the Spring app itself and not with EC2 or with connection. In other words: the traffic can reach your Spring app, but your Spring app has nothing to say in response.
As a side note, after deploying your app I would advise to refine the inbound traffic rules to allow only the traffic you want. There is no need of allowing all traffic on all ports.
I have table plus app and I create eb then deploy my project then connect to database and all thing is good and cool!
I need to connect to database(MYSQL) to import some data to the AWS database so I do these steps:
open new workspace in table plus
take endpoint and username of database and the password and the name of database like so:
press Test button and after wait some times I got this error:
I change the port to also 5432 and got same first error
I change the port to 3306 and got this error:
where is the problem ?
Ok the way i did it was by following this video:
https://www.youtube.com/watch?v=saX75fTwh0M&ab_channel=AdobeinaMinute
In short you need to get the details of your instance and set up an ssh connection to it using its hostname (ie that of the instance not the db), your ec2 username (usually ec2-user) and your pem file. Then you get the connection details for the db and enter them. See the screenshot.
I think that your problem is that the configuration you created is set to a Redshift connection. It expects some network communications that are different from a MySQL connection.
Can you try to create a MySQL connection instead?
I had the same issue but my problem was with the security rules in aws. perhaps, this may help.
Navigate to the console
edit inbound rules of your rds instance
add a new security rule
where: type: 'all traffic', source: anywhere
This video gives a google explanation: aws rds setup
I am new to sails. I have created an app with Sails. I have deployed the app to AWS. App works with localDiskDb. When I try connecting to RDS, I get the following error. I have set up connection URL in sails.config.datastores.js. When I see my error message, my feeling is that Sails still trying to connect to localhost. But I did not find any other place to replace that settings. I hope it's enough to change only connection URL. I am running Sails app with developmenet environment locally.
adapter: require('sails-mysql'),
url: 'mysql://USERNAME:PASSWORD#.................amazonaws.com:3306/DATABASE_NAME'
Error message
You have to open the 3306 port in your EC2 instance.
Do this in Security Groups by editing the Inbound Rules and adding a new TCP rule for the 3306 port AND specify your IP (where the app connects from) in order to not allow everyone access this service.
I fixed this issue. I had used a '#' in my password. It ruined this all.
Whenever I tried to access to my deployed application on an EC2 instance of AWS using the public IP, I get the following messages on Chrome: "This site can’t be reached
ec2-54-194-153-202.eu-west-1.compute.amazonaws.com took too long to respond."
then, What changes shall I apply in order to grant access to the application properly ?,
Thank you,
The first thing to check in this case is The Security-Group inbound rules attached to your Ec2.
If your application is running behind a webserver like Nginx or Apache, check that your security_group is open in inbound for the public range (0.0.0.0/0) on the http port (80).
You can get this info on the Ec2 panel, click on your instance and check the attached security_group, click on it and check the inbound rules.
Here is a guide for you.
Notice : If nothing is running on your Ec2 it will never respond, be sure your app is served by a Nginx/Apache/Tomcat daemon.
Hope it helps !
I've launched a new EC2 instance, Parse Server powered by Bitnami (HVM)
After installation, The "Analytics" and "App Settings" are missing.
Also, there is no login screen. Anyone who has the IP address can just access the console and change everything.
What have I done wrong? It is a new App, so I don't have the need to migrate an old Parse DB.
You have 2 options here.
Either setup a server side password protection from apache side check this guide. https://www.digitalocean.com/community/tutorials/how-to-set-up-password-authentication-with-apache-on-ubuntu-14-04
Second option is in security group for your EC2 instance for just set this below rule so only you can check the dashboard from your local machine with your IP address also make sure HTTP is not having a rule 0.0.0.0/32 in the security group.
For setting Analytics and App Setting check this guide https://wiki.bitnami.com/Applications/Bitnami_Parse_Server