.ebextensions not included in AWS source bundle - amazon-web-services

I have a .net core application which was earlier hosted on aws with ssl and load balancer. But in order to avoid load balancer I found that ssl will also not work without load balancer. As an alternative for SSL certificate I created a folder in root folder - .ebextensions and a config file inside it.
The problem is when I am publishing it to aws via elasticbeanstalk then the .ebextensions is not included in the source bundle and therefore ssl certificate is not working. Is there any way I can include this folder or any alternative way to get ssl certificate without load balancer. Please advice.

This is a very small thing which I ignored. Just change the Build Action of config file from None to Content will allow the folder and file to be copied. Empty folder not included while publishing. Thanks #Marcin and #Sridhar Raju for all the help

Related

GCP load balancer to point to index.html in /bucket/folder1/folder2/index.html

I have a bucket bucketName and couple of folders inside it (folder1/folder2/..
Folder2 is index.html file, js/* and css/* folders. I would like to create a domain mapping using GCP load balancer (domain.com) to point to LB IP.
I have already tried with Advanced settings in host and path rule but not working. Can someone guide me.
I solved this by below structure:
created a LB.
In the path mapping section, go to advanced settings and click on host and path rewite.
In the path rewrite, define the folder path.
You may have to wait for some time to get it reflected.

How to add a configuration file to a AWS application load balancer?

I've been looking into how to route HTTP traffic to https for my Elastic Beanstalk environment. AWS has documentation on this that recommends using configuration files. I'm just not sure where I should paste this configuration? I'm quite now to AWS, so I'm love some newbie friendly advice.
I'm using an Application Load Balancer.
Thanks
The files in the docs cited, alb-http-to-https-redirection-full.config and alb-http-to-https-redirection.config are to be placed (after your modifications if needed; HTTPs requires SSL certificate) in your .ebextensions folder.
So in your zip package would have files .ebextensions/alb-http-to-https-redirection-full.config and/or alb-http-to-https-redirection.config along side your application.

Connecting AWS instance and godaddy domain name - issue with folder

I have XAMPP set up in an EC2 AWS instance and am trying to connect up my godaddy domain name. I can see xampp is working on the IP address and my site works under when I use IPADDRESS/FOLDER/index.php
How do I get my domain name to read the index.php file in the folder? All the tutorials I have followed allowed me to access an index file directly in the htdocs file (IPADDRESS/index.php) but I seem to be having trouble with the additional folder. The folder is important because it is managed with Git.
The folder I have saved in within my EC2 instance is /opt/lampp/htdocs/
Thank you!
Gemma
You can't point a domain name to a folder. You need to edit your web server configuration on the EC2 server (Apache httpd?) to use the folder as the server root location.

Dynamic Apache site with route 53 and cloud front not working

I am beginner with AWS and need some help for my first project .Below is the architecture of my environment and the code runs great on Godaddy .I am trying to move it on AWS. Please try to understand things are working but not in a way that I want.
Setup
Two private subnet AWS linux servers(like one in Associate practise lab)
One S3 bucket mapped to /var/www/html sync aws s3 sync cronjob
Route53 domain name registered sample.com
Cloudfront created https://sample.cloufront.net
Application load balancer internet facing --ssl (80,443 listener ports )
ACM -SSL certificate issued *.sample.com ,WWW.sample.com
RDS instance with everything configured for SG etc
Issues
Below are the Issues
As soon as I use http -https redirection from httpd.conf as suggested by Amazon guys I get a bad gateway using this documentation
Images are not getting delivered by Cloudfront. I tried to redirect in .htaccess getting access denied although I created identity and updated bucket policy .
Load Balancer DNS name gets exposed even when route53 mapped to load balancer
httpd.conf "All" has been used for override
S3 Sync with /var/www/html is changing the permission on linux when any new file is uploaded .

.ebextensions conf file not getting detected

I am running a single instance machine behind a load balancer and I am able to setup the secure port domain to work for https://www.example.com.
I am trying to redirect both http://www.example.com to https://www.example.com
I am running Tomcat 8 on the instance behind the load balancer
I was toying around with AWS extensions to make the redirect work and I used the following links for my reference to create a .ebextensions directory.
Redirect Http Url to Https in Elastic beanstalk loadbalancer
I dont see the .ebextensions directory after deployment in the tomcat root folder
The content on elasticbeanstalk.conf doesnt include the rewrite rules and module reloads that I added to make the redirect work .It still seems to contain the default values the file had before deployment. Seems the .ebextensions didnt get executed at all
I have installed an AWS certificate manager on my load balancer.
I am able to manually access https://www.example.com
Cant figure out if I am missing something? Can someone in the community help me resolve the issues.