Deploying a grpc service on AWS was pretty straight forward thanks to the built in support in their load balancer, but as far as I can tell they don't have a built in solution for grpc-web?
What would be the easiest way to add support for grpc-web for a low volume service running in ECS?
Related
I have tried to search relevant info but couldn't find anything relevant. Please point me to some links on this.
I would like to know what is the best way to:
Connect to on-premise SOAP services from AWS cloud
on-premise Java RMI services
on-premise FTP to exchange files
Thanks
Connecting to SOAP, Java RMI or FTP service on-premise is something that will part of your application logic implementation. Which infrastructure you choose to deploy your application is a matter of choice depending on factors like what knowledge you have, what other application requirements you have and so on. Provided that you have configured your on-premise servers so that they are available on the public internet, you can choose to deploy your application using any server hosting option. For AWS specifically, EC2, Elastic Beanstalk and container options EKS and ECS comes to mind in addition to Lambda.
I don't want to get into a discussion about AWS vs Azure but I am trying to figure out how to set up the equivalent of an Azure Service Fabric Cluster on AWS.
I currently set up an environment in Azure by creating a Service Fabric Cluster which creates the virtual machines/nodes, load balancer and anything else that is needed. I then have a visual studio project with a fabric project and a service project which i deploy to the cluster. I'd like to write my services in Visual Studio utilizing C#.
If I wanted to migrate this to AWS or set up a similar environment in AWS what do I create? There seems to be a lot of different options but am confused as to whether i need to create the EC2 virtual machines myself and then the cluster and load balancer manually?
I am not sure if Elastic Beanstalk is needed or the easiest steps to create a microservice environment that I can deploy .NET apps from VS.
Thanks for any help/clarification.
If you wanted to keep the same application and deployment model, there is a doc from Microsoft that outlines the necessary steps for deploying Service Fabric on AWS.
Using AWS to run kubernetes cluster which installed by kops.
Using alb-ingress-controller to realize application load balancer(ALB) on AWS.
Deployed a websocket application into the kubernetes cluster. When try to access the application from ALB DNS, because of it's using load balancer, so sometimes can't catch the response. It's went to the target group one by one.
Maybe the default proxy-mode of kube-proxy is iptables, so thinking about change iptable to userspace, here is a related question:
What does userspace mode means in kube-proxy's proxy mode?
But is it the right way? To make sure the websocket application can run correctly on AWS using ALB?
If it's the right way, then how to change kube-proxy's proxy-mode to userspace?
Here is another article about running socket.io application on kubernetes:
Running Socket.IO Applications on Kubernetes
But it's using ELB. And the method seems a little complex.
Finding a good way.
I am just finishing up C# web API and am wondering on the best way to deploy it on AWS. I am aware I could boot up a VM in the cloud and host it in IIS , is this the only way?
Spinning up one or more Ec2 instances is one way, and there is nothing wrong with that approach.
Two other options:
employ elastic beanstalk to automate the deployment for you -
but it still ends up running on EC2 instances.
convert your WebAPI to API Gateway & C#/Lambda functions instead and
run it 'serverless'. Depending on the requirements of your
application this may or may not be a viable option for you.
Hi We have built a java based web services project with using jboss server. How do I host this application with Amazon cloud? This web services act as back end for a mobile android app.
I am looking for PaaS option of Jboss server and Postgres database. I could create a postgres database. But could not find Jboss server.
My understanding is in PaaS, Jboss and Postgres should be able to scale up itself as per demand.
Another option provided by Amazon is EC2 as far as I have understood. But if I go with EC2, I will have install and set up jboss and postgres on my own. Then does it scale up by itself as per demand?
Please guide.
If you want to deploy your web application to AWS and ensure its scalability, you have basically two options:
EC2 instance [IaaS] - The disadvantage is, as you mentioned in your question, that you have to configure everything manually. Some external mechanism for scaling has to be used. Amazon provides its AutoScaling service which can be configured to launch new EC2 instances based on utilization or some other metric.
Elastic Beanstalk [PaaS] - This service has the auto-scaling already built in and manages the EC2 instances with your application on its own (it takes care about launching them, deploying the app etc). The disadvantage is that JBoss server is not support at the moment (you would have to switch to Tomcat).
There is a way, how to make JBoss work on Elastic Beanstalk, however. ELB has newly added the support for Docker so if you make your JBoss API run in Docker, you can deploy it to ELB and scale it without much effort and configuration.
As for the database, mentioned in your question, Amazon has plenty of choices, Postgres included, in their RDS service.