I installed airflow and started it on EC2 Ubuntu:
airflow webserver
But I cannot get access to admin panel in the browser. I tried:
ec2-XX-XXX-XXX-XX.eu-west-2.compute.amazonaws.com:8080
But I got message:
This site can’t be reached
It needed to tune Inbound Rules in Security Group for the instance with Ubuntu.
Image Description here
Exposing the Airflow UI to the world is not a great idea. I faced this problem few years ago and created this page Airflow on AWS EC2
For added security, creating a user & password to login is advisable.
Also check out Airflow 2.0
Or simply use Airflow on AWS using Amazon MWAA, more on this here
Related
I deployed a web app on an ec2 instance AWS.
I am unable to view my site on a web browser. The site does not load at all, just shows an empty screen.
Please see my inbound rules, perhaps there is something I did not add. I'll appreciate any help.
After running netstat, I get the following response:
This is not an AWS issue.
Your React App has a problem:
So I am starting up a new neo4j instance in aws ec2 using neo4j community edition from the aws marketplace: https://aws.amazon.com/marketplace/pp/B071P26C9D
The machine comes up and I set up an elastic public IP. However, when I try logging in with the default credentials neo4j/neo4j through the web neo4j browser, I get an invalid credential error.
Anyone know if the creds are different when using the marketplace ami?
Well, this is kinda embarrassing. But I just realized that there is a tab labeled usage instructions under the ec2 instance. The text under the tab instructs me to use the instance id of the ec2 instance as the default password and that worked.
I have been trying to install Pivotal Cloud Foundry on AWS and I have troubles with it.
In the section upload-cert mentioned that I need to create SSL Certificates for:
*.system.example.com
*.login.system.example.com
*.uaa.system.example.com
*.apps.example.com
So, I've created domain xxxxx.com on AWS Route53 and created a certificate on AWS ACM for domain and subdomains.
So, my questions are:
do I need to create subdomains (system, login, uaa, apps) in AWS Route53
do I need to bound my domain and subdomain somehow to PCF? Or the installation process had to do it for me?
for now, if I open http://login.xxxxx.com/ it responses with 503. what can be the reason?
what is the correct url to open the PCF UI?
I have such error in Ops Manager. What can be the reason of such error?
The same about logs. When I tried to download logs for failed services it failed too. What can be the reason?
Thank you for the help!
do I need to create subdomains (system, login, uaa, apps) in AWS Route53
do I need to bound my domain and subdomain somehow to PCF? Or the installation process had to do it for me?
You can create a wildcard subdomain (*.xxxxx.com) and alias using the instructions here: https://docs.pivotal.io/pivotalcf/1-10/customizing/cloudform-er-config.html#cname
what is the correct url to open the PCF UI?
If you mean Ops Manager, it is whatever DNS entry you created and pointed to the Ops Manager public IP address in this step: https://docs.pivotal.io/pivotalcf/1-10/customizing/cloudform-om-deploy.html#create-dns
For the ERT UI, there is the Pivotal Apps Manager https://docs.pivotal.io/pivotalcf/1-10/console/index.html
which is usually apps.system.xxxx.com
You can see what system apps are deployed by connecting to Cloud Foundry using the CLI and seeing which apps are in the system org, and what their routes are.
for now, if I open http://login.xxxxx.com/ it responses with 503. what can be the reason?
If the DNS has not been set up, I'm surprised you're getting any response whatsoever. Usually you get 503s when the routers connected to the load balancers are failing for some reason (http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/ts-elb-error-message.html#ts-elb-errorcodes-http503)
I have such error in Ops Manager. What can be the reason of such error?
This would explain the 503s if the router is unhealthy. I would SSH into those machines and see what the logs say (in /var/vcap/sys/logs), which should tell you what is going wrong.
The reason of the red instances on the Status page was that my AWS account had limit on number of instances and it failed to create VMs for this nodes.
To find more information open Changelog (https://ops_manager_host/change_log) and the open log of the FAILED setup.
I have installed PencilBlue on AWS EC2 instance. i have started PB by using the command pbctrl start
Now, how can I access the PencilBlue login page?
Just like you run any other web server on EC2, you start the service, open the port in the Security Group, and then open the website in your browser.
I just started using Locust, installed on a AWS instance and it is working fine. But I am unable to get to the web interface. Port 8089 is open in the AWS security group.
http://ec2-XX-XX-XX-XX.eu-west-1.compute.amazonaws.com:8089 is not working for me.
Any advice?
The best way to run Locust on AWS is Elastic Beanstalk, follow these steps: https://blogs.aws.amazon.com/application-management/post/Tx351HCZ9D1RQ84/Using-Locust-on-AWS-Elastic-Beanstalk-for-Distributed-Load-Generation-and-Testin