For High Availability file system cluster, is it a good idea to use amazon load balancer to manage the ec2-instances where i have setup the gluster cluster.
If i can use a aws load balancer is it possible to create a init script where i can specify the instance type,gluster installation steps in the load balancer.
Thanks.
I don't think it's a good idea.
Why don't you want to use Amazon S3 as your data storage?
It's redundant and highly available by design.
You can also set up cross-region replication replication in order to have ultimate high-availability.
Related
My applications run on ElasticBeanstalk and communicate purely with internal services like Kinesis and DynamoDB. There is no web traffic needed? Do I need an ElasticLoadBalancer in order to scale my instances up and down. I want to add and remove instances purely based on some cloudwatch metrics? Do I need the ELB to do managed updates etc.?
If there is no traffic to the service then there is no need to have a load balancer.
In fact the load balancer is primarily to distribute inbound traffic such as web requests.
Autoscaling can still be accomplished without a load balancer with scaling based on the CloudWatch metric that you want to use. In fact this is generally how consumer based applications tend to work.
To create this without a load balancer you would want to configure you environment as a worker environment.
#Chris already anwsered, but I would like to complement his answer for the following:
There is no web traffic needed?
Even if you communicate with Kinesis and DynamoDB only, your instances still need to be able to access internet to communicate with the AWS services. So the web traffic is required from your instances. The direct inbound traffic to your instances is not needed.
To fully separate your EB env from the internet you should have a look at the following:
Using Elastic Beanstalk with Amazon VPC
The document describes what you can do and want can't be done when using private subnets.
I am planning to set up a Kubernetes cluster in AWS without using EKS. Since EKS provides Amazon VPC CNI for managing networking at pod level, which provides better networking, I am planning to use the same.
I need to know, whether it is possible my Kubernetes cluster with Amazon VPC CNI, if yes, can somebody provide me the document or how to perform it.
I assume you can.
Download manifest - https://github.com/aws/amazon-vpc-cni-k8s/blob/master/config/v1.5/aws-k8s-cni.yaml
And run kubectl apply -f aws-k8s-cni.yaml
Did you check https://github.com/aws/amazon-vpc-cni-k8s ?
You definitely can, but you shouldn't. The AWS VPC CNI is limited to the network interfaces of an EC2 instance, which means you can not have more pods than network interfaces! This is a huge cost driver and therefore better look for another CNI from the start.
I am trying to create a High availability Kubernetes cluster for my CI/CD pipeline for deploying my Spring Boot microservices.
I am following the following kubernetes official document for exploring:
https://kubernetes.io/docs/setup/independent/high-availability/
My confusion is that - when reading, I found that need to create Load Balancer for kube-api server for forming the HA cluster. Actually I am planning to use AWS Ec2 machines for forming the cluster. So I will get Elastic Load Balancer from AWS. So do I need to create separate Load balancer as described in document or can I use the ELB for the same ?
You can use only ELB for this purpose.
Hopefully these Kubernetes and ELBs, The Hard Way instructions will be useful for you.
I am tying to deploy galera cluster on aws. Is it a good idea to use VPC or making a cluster with 2-3 open ec2 instances. What are pros and cons.
Also, Is there any extra billing for VPC? Any help will be great!!
I am not sure of the variation of the installation of the GALERA on AWS VPC with EC2 instances.
One suggestion which I would add is the consideration of the RDS - Database as a service from AWS; I don't whether that would solve your need to use GALERA.
Regarding the pricing for the VPC, it is free; you only pay for the underlying EC2 instances running, Elastic IP - Data Transfer, Out Bandwidth etc. If you are going to connect your local data center to VPC using VPC/VPN gateway - that would be charged
No there is no extra cost for a VPC [but only for the resources used in it]
With Galera you can have a multi-master architecture [I have not implemented it] but with RDS you cannot. I have setup a Disaster Recovery plan with RDS where a multi-master architecture would be eliminating the downtime , but instead set it up with the use of Read Replica which would be promoted in a master. That's the way AWS RDS works.
Our app has independent clusters of boxes running on Amazon Web Services. I need to send http requests to different clusters based on the URL. For example, http://api.mydomain.com/foo should go to the "foo" cluster, and http://api.mydomain.com/bar should go to the "bar" cluster.
I don't see anything in the elastic load balancer or Route 53 that will do it.
(The obvious thing is to have separate subdomains, but that's difficult for this app. We want to stick with just the "api" subdomain because the cluster configuration may change in the future.)
What's the best approach?
That is not supported by the load balancer. Using subdomains does work if you want to use the existing load balancer.
If you need more features, you could configure your own using a software load balancer running on top of an ec2 instance. Not likely to be as cost effective however.
It is not possible using ELB. Use Netscaler EC2 or HAProxy EC2 in your AWS environment to achieve this. NetScaler is available in AWS marketplace.