Unifi controller hosted on AWS no Internet interface - amazon-lightsail

I successfully installed Unifi Controller on AWS Lightsail instance.
Version Network 7.2.92
I am able to adopt my Unifi AP successfully and I can see it.
However I canĀ“s see any internet interface
It is simply blank.
How is that? How should I configure Internet interface?
Thank you
network interface

Related

Using an AWS S3 File Gateway in EC2, why does it only work in a public subnet and not a private subnet?

Whether I try to create an AWS S3 File Gateway (EC2) in the management console or with Terraform, I get the same problem below...
If I launch the EC2 instance in a public subnet, the gateway is created. If I try to launch the gateway in a private subnet (with NAT, all ports open in and out), it wont work. I get...
HTTP ERROR 500
I am running a VPN and able to ping the instance's private IP if I use the Management console. This is the same error code in terraform on a cloud 9 instance, which is also able to ping the instance.
Since I am intending to share the S3 bucket with NFS, its important that the instance reside in a private subnet. I'm new to trying out the AWS S3 File Gateway, I have read over the documentation, but nothing clearly states how to do this and why a private subnet would be different, so if you have any pointers I could look into, I'd love to know!
For any further reference (not really needed) my testing in terraform is mostly based on this github repository:
https://github.com/davebuildscloud/terraform_file_gateway/tree/master/terraform
I was unable to get the AWS console test to work, but I realised my Terraform test was poorly done - I mistakenly was skipping over a dependency that was establishing the VPC peering connection to the Cloud 9 Instance. once I fixed that it worked. Still I would love to know what would be required to get this to work through the Management Console too...

Cannot access ASP.NET Core Web API from Windows-based Amazon virtual machine

I've been searching Google and StackOverflow about this for several hours now, and nothing seems to work.
I created a Web API server in ASP.NET Core and verified it works locally.
I created a new EC2 VM to host the Web API. I copied all the binaries for the API up to EC2, and started the server from the command line.
I have made sure that the required EC2 security group exists and that the correct TCP port is open for Input in the security group.
I have added an appropriate firewall rule to Windows firewall.
NETSTAT -Q shows that the server is working and that the port is in LISTENING mode.
I get the public IP address for my EC2 VM and go back to my local machine.
I use POSTMAN to submit POST requests to the EC2-based server.
POSTMAN returns an error: "There was an error connecting to ...."
So I'm at a loss as to what to do next. Have I missed some EC2 configuration? Is there something else I have to do to the ASP.NET Core WebAPI code?

Freshly Installed Apache-Tomcat on the AWS server, how can I access from outside world

I have installed an App with Apache tomcat on AWS ec2 instance. I am able to access the tomcat url (which is server_name:8080/BOE/BI) from the AWS instance on Win2016. Also I installed IIS on the server.
Now what are the configurations I need to do to on AWS ec2 instance to access the URL from outside the AWS instance like from my personal PC.
I also tried disabling the firewalls, it did not helped.
You need to look at security groups. This will allow you to open up ports on your EC2 instance from the outside world.

Static Webpage hosted in a EC2 instance

I followed cloud guru's course to create a ec2 instance in aws. I installed apache webserver and created a static page. When I login to the ec2 instance and run the curl command (from within ec2 instance) using "Public DNS (IPv4)" address , I am able to view the page in browser. However when I try to open it in my browser, I am unable to view. I did not make any changes to outbound rules in my security group.
I am unable to access the page using the public ipv4 ipaddress both from within ec2 and outside.
I can't comment due to new user. This seems "security group" inbound rule issues. Did you open port 80 in security group "inbound"?
When you use "public IP" even from EC2 box, that will be considered as traffic from internet and if your security group is not configured to accept (inbound) traffic from internet, you can't access the website available on port.
NOTE: Suggest to open port to "MyIP" instead of "whole world".

Bitnami WildFly 10.0.1 on Google Compute Engine can't access management interface

I have recently launched the Bitnami Wildfly on Google Compute Engine. I have done all the configuration and everythings is working fine except for the management interface which give an error message:
The management interface could not be loaded.
Authentication required.
I know i have to create a tunnel via SSH with Putty, I did that and I am able to access the server terminal. The Tunnel i created is to allow connections via localhost:9999 from the remote port 9990.
I have also tried editing standalone.xml and changed the interface to accept connection on , that too did not work.
Kindly assist.
Solved: It appears that when configuring the tunnel use 127.0.0.1:9990 instead of localhost:9990, I guess this is because the standalone.xml is configured to accept connections on 127.0.0.1.