amazon-elb

We like to enable HSTS to our IIS deployed web application. We have SSL terminating ELB Application load balancer. We have enabled the URL rewrite module in IIS and configured the x-Forward-Proto tag to decide and enable HSTS header in the response. Presently, ALB does not appear to pass custom headers from IIS to the ALB, to the end-user. We wanted to see if there is a way to enable HSTS either at ALB level where it can accept custom headers or if it can be set at IIS level and ALB can pass through the HSTS headers to the browser? HSTS is a policy that is controlled by the backend and not by

I'm trying to add an .ebextensions folder to the root level of my jar to be deployed to AWS elastic beanstalk. My folder structure is: main: --src --resources --.ebextensions When I build the jar my .ebextensions gets placed on the classpath of my target and therefore is not picked up by Elastic Beanstalk on deploy. Pom.xml <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <configuration> <fork>true</fork> <addResources>false</addResources> </configuration> </plugin> How can I build so that ebextensions is picked up by ELB? This works for me

I'm pretty stuck with this thing for couple of hours. No way I could make it working. I tried everything I can think of and/or found online. So, my application is pointed to ELB (web). ELB listens to 80 and 443 and sends traffic to 80 (SSL is terminated here) to member instance(s) which is nginx. Nginx proxies app requests to another ELB (app) in front of multiple instances. These instances run puma. Everything works fine except when I try visiting an URL (where I used force_ssl for that controller) with https scheme, I get a redirection loop. Here is my nginx configs look like location @{{app

AWS clearly states here and in the Q&A that one can connect to an MS SQL server using a PHP instance on the Elastic Beanstalk. However, there seems to be no way to install the MSSQL drivers. For example, installing yum php-mssql from the ELB command line, generates errors stating that the versions of the dependencies needed are too high. Here's a classic error report: --> Running transaction check ---> Package php-common.x86_64 0:5.3.29-1.8.amzn1 will be installed --> Processing Conflict: php54-common-5.4.45-1.75.amzn1.x86_64 conflicts php-common < 5.4.45-1.75.amzn1 --> Processing Conflict:

I'm trying to deploy an ASP.NET MVC web application, which uses individual user accounts, to an AWS server, which is using an elastic load balancer (ELB). I've deployed the site to IIS on the AWS app server, connected it to my AWS SQL server, and it works as expected on the server (and indeed when I run it in Visual Studio or deploy to an internal server). The problem comes when accessing it remotely, which of course goes via the ELB. If I try and access https://www.example.com/ it doesn't work - it will redirect me to http://www.example.com/Account/Login?ReturnUrl=%2F , which hangs and I then