redirect sub subdomain to subdomain in cloudflare - kubernetes-ingress

I am trying to redirect app.test.dev.mydomain.io to another origin app.dev.mydomain.io because there is an IOS app which uses this origin, but I got the error of ERR_SSL_VERSION_OR_CIPHER_MISMATCH
and the app is running on kubernetes cluster with ingress controller to access it.
do you have any suggestions to doing that?

Related

CloudFront signed URL returns a 504

I've got a chatbot backend which is talking to a service (service 3) which talks to another and sending a CloudFront signed URL for an image.
Then from the Chatbot browser (client) requests to CloudFront which talks to Service 1 and Service 2 for serving the image.
All the services are deployed in AWS Elastic Beanstalk. But now its reurning HTTP 504 when requesting for the image from CloudFront.
As a way of resolving this, I tried updating Route 53 CNAME entry manually with Service 1 load balancer URL assuming this has caused by CloudFront not being able to reach public DNS entry for Service 1. But it did not resolve the issue.

How to redirect HTTP to HTTPS from Classic Load Balancer in AWS

We have a web application developed in Asp.NET MVC Core 3.1. Deployed it using Elastic Beanstalk.
Configured Classic load balancer for this with AWS issued certificate listener. Our classic load balancer's listeners configured as below.
Using this setting, its not redirecting from Http to Https. However if we try to access website individually with Https and Http its working fine.
We don't want to change Load Balancer Type from Classic to Application as the environment is already setup in Route S3 too.
Can you please help if anything missing in this?

Express backend & React frontend under the same domain

I have a backend in Express.js deployed on Elastic Beanstalk and a frontend built with React.js deployed on Amplify and I would like to make HTTP (using axios) requests from the frontend to the backend via relative paths.
I'm quite new to AWS but I figured I could use Cloudfront to set the backend as a behaviour?
I have a domain (mydomain.com) for the frontend where the DNS are pointing to Amplify cloudfront (which I think I can't access...) and Elastic Beanstalk has its own aws domain (http://app-name.region.elasticbeanstalk.com/).
The frontend seems to be working fine as if I go to mydomain.com I can see it. Also the backend seems to be working as if I go to http://app-name.region.elasticbeanstalk.com/api/user it would return the expected json data.
The idea would be though that mydomain.com serves my React application which internally would make calls to, for example, mydomain.com/api/user where my express backend would serve the user.
I got lost in the docs and on the internet didn't really find anything.
Is using Cloudfront the right approach? If so, how do I connect Amplify and Elastic Beanstalk?
Any suggestion would be very appreciated!

Node JS Deploying API to client without any Front End

If i created api in nodejs like login,registration,delete,add,update user like system and i want to give it to my client how can i deploy it??
Like we run our API's on POstman so how client will use it! I don't want to add any front End to it.
You have a few options... you can go for heroku or a virtual private server. For vps you have options like aws ec2, google cloud platform etc. You can host your app in a vps with a static ip. You can use pm2 to host the app. Https is better. Use an nginx reverse proxy for security. Proffesional api servers do the above...

POint domain to ec2 ip with page name

I have a domain in bigrock and Ihave ec2 instance running on aws with elastic ip.
Over there I have instantiated tomcat server and it has my website files in its htdocs folder.
I have managed DNS of bigrock to this ec2 ip.
So when I browse for my domain name in browser it launches tomcat home home page insteade of index.html file
So how can I load index.html file by default?
You can't point a domain name to a specific web page. A domain name points to a server. You have already configured your domain name correctly.
You have a few options:
Configure Tomcat to serve your application as the root context.
Place a reverse proxy like Nginx in front of Tomcat, and configure it to route requests to your Tomcat app.