I am using AWS Toolkit to deploy the wcf service on amazon elastic beanstalk, after deployment it shows environment is healthy but when i browse the URL then it redirected to the IIS Server Page, i am unable to access the service url , please let me know how to access the hosted service
Thanks in advance
Follow the standard procedure to deploy a ASP.net project. Here is the link for that : Link
But for you WCF service you need a simple html page at project root. E.g. index.html or default.html. Load balancer need this page to check if the instance is available or not. Without this html page load balancer will consider the instance dead and remove it.
Related
My application architecture contains an EC2 and ALB in a non prod VPC
The application involves an angular front end (http://localhost:6674/App/login) and .net backend (http://localhost:6574/App/api) website deployed in IIS in a newly created EC2 instance.
In IIS default website, I have created rewrite rules like all /App/* will go to frontend (http://localhost:6674/App/login)
ALB (http://alb-xxxinternal.com) configured for port 80 (HTTP). Instance health and other security group settings are proper and verified.
Currently, on accessing (http://localhost:6674/App/login) or (http://localhost/App/) I am getting my application home page loaded properly.
Issue
On accessing ALB FQDN, IIS server page is getting loaded, but on (http://alb-xxxinternal.com/App/) it is giving 403/404 status error. The application home page is not loaded.
Why is this issue happening ? Is this because of some firewall setting or a proxy issue?
Is there a way to debug the issue using the browser console/network?
We have a load balancer with a URL map that points to back-end Cloud run services. When we just use cloud run without a load balancer all the assets load as expected. (e.g links to the cloud run service are correct.
When we put the service behind a load balancer we have some weird issues on the links returned from the backend service.
When we hit the load balancer with this path https://custom.domain.com/hello-no-auth we hit the backend service but all the links returned from the service has the wrong paths. The return links from the service miss the URL path we defined in the URL map. For example, icons will come back with his URL
https://custom.domain.com/assets/icon.svg
but we expected they would come back with
https://custom.domain.com/hello-no-auth/assets/icon.svg
Also https://custom.domain.com is not the real domain but just for demonstration
Apologies this was an error with the return links for the assets in the backend service.
To be clear this was not an issue with GCP but the application itself.
Make sure you have not implemented URL rewrite in your project.
I have hosted AWS OpenSearch(ELK) and with that Kibana also get hosted. So I have created a dashboard in Kibana where I get the embedded link and insert it to my HTML code. It ask me to login Everytime.
If I host a EC2 instance and install Nginx in it and is it possible if I configure Nginx.conf and provided the access credentials to it so whenever my website gets loaded Visualization inserted in my website through Kibana Embedded Link it should not ask for authentication.
I have an api server sat behind a load balancer as part of an AWS elastic beanstalk configuration.
I want to ensure that only my web application can talk to the api server (via the load balancer). My web application is hosted in s3. Can somebody please enlighten me as to the best way to go about this?
Thanks in advance.
S3 simply serves your web app's static files to an end-user's web browser. The application runs in each user's web browser. No code is ever running on S3. As such, there is no way to do what you are asking.
You might want to look into something like API keys, or possibly AWS Cognito.
I am using Amazon AWS EC2 to host my web application. My web application is hosted on 2 web servers and having Loadbalancer to manage traffic.
I am using CodeIgniter framework.
My problem is when I try to login to my application, Loadbalancer is routing my request to wrong server and even with correct Login Password I am not able to Login to my application and due to this my session is not started.
Thank you in advance:)
You should be enabling the sticky session feature.
If you are using AWS ELB (Classic Load Balancer), then check out how to configure sticky sessions.