Elasticsearch Cross Cluster Replication (CCR) on Amazon AWS and MS Azure - amazon-web-services

I am wondering if there is a support for elastic search cross cluster replication on AWS and Azure?
I see AWS announcement where said that they are going to support cross cluster search (don't sure that is tis related to my query though).
Could you please advice if it is supported or are there any news pointing that it might be supported in the nearest future?
Highly appreciate any help.

AWS Elasticsearch doesn't have CCR(Cross Cluster Replication).
However you can achieve (depends on your RTO & RPO) the same by taking manual snapshots into your own S3 there by replicating the data into new Domain.
For more info on manual snapshots , you can go through here

At last Amazon releases new opensearch service for elasticsearch cross cluster replication. Here is announce - https://aws.amazon.com/about-aws/whats-new/2021/10/amazon-opensearch-service-amazon-elasticsearch-service-cross-cluster-replication/

Related

Is there a current solution for Amazon AWS Connect Voicemail?

My company is currently looking to build a power dialer using AWS Amazon Connect but I haven't been able to find support for agent extensions or voicemail. I'm, I going crazy? Someone please point me in the right direction.
We faced similar challenges and after several attempts discovered https://amazonconnectvoicemail.com . It was easy to integrate into our current Amazon Connect instance.
AWS has recently released Voicemail for Amazon Connect, which is deployed using a CloudFormation template.
You only pay for the standard AWS charges that the solution uses, there's no additional platform/service charges.
https://aws.amazon.com/solutions/voicemail-for-amazon-connect/

AWS Document DB MultiRegion replication

I know that the AWS DocumentDB doesnot support multiregion replication even the snapshot cannot be shared across regions.
Please suggest how we can manually do the replication
Sam,
AWS released cross-region snapshot copy today (7/10/20), so that should get you what you need. Good luck.
https://aws.amazon.com/about-aws/whats-new/2020/07/amazon-documentdb-support-cross-region-snapshot-copy/
Thank you for the feedback, Sam. A couple of options are to use change streams + Lambda/worker to replicate the data or to take take backups to S3 with mongodump and utilize S3's cross-region replication capabilities.
Amazon DocumentDB now supports global clusters. The primary cluster supports writes and read-scaling, up to 5 regions can be added as read-only, see https://aws.amazon.com/documentdb/global-clusters/

Can you use Amazon's MSK on EKS?

I'm looking at the possibly of replacing/moving our existing Apache Kafka set up (version 2.1.0) to Amazon's MSK and for it work on EKS.
I've been looking around to see if this is actually possible and if someone has done this or attempted it but so far I've only seen reference to using Apache Kafka on EKS. Does anyone know if it is possible/makes sense to use MSK on EKS?
Many thanks.
Amazon MSK provides fully-managed Kafka clusters, which means that from your side, you do not have to operate the cluster at all. Broker and Zookeeper nodes are packaged, deployed, created, updated and patched for you.
This step-by-step tutorial illustrates the creation of a cluster.
The answer is not, MSK is a fully managed service provided by AWS, you cannot install managed service :-) but you can run your own Kafka cluster on top of Kubernetes cluster in AWS, eg. on EKS service while installing a Kafka Operator:
https://banzaicloud.com/docs/supertubes/kafka-operator/
I haven’t done it for MSK before but surely done it for AWS Aurora Postgres. Not sure why you can’t define your external persistence (in this case MSK) as a service with no selector then manually register an Endpoint object pointing to the MSK host.
https://kubernetes.io/docs/concepts/services-networking/service/#services-without-selectors

neo4j cluster on Amazon AWS

This might sound like a newbie question but I have a neo4j instance running on Amazon cloud. The instance is set to Autoscale at 80% usage. That means Amazon one the usage is reaches 80%, Amazon will create another instance on Neo4j with the same configuration and will keep adding more once this one reaches 80%..
My questions are -
1) Does this setup on Amazon means we have a cluster of neo4j in place?
2) Do I need to do anything else in order to have neo4j cluster, what I have read is that you need some tool like zookeeper to maintain the cluster..
3) Does this current setup on Amazon will have both instances as Master or will it be more like master/slave setup..
Any help, feedback, suggestions would be helpful.
Thanks in advance,
Ravi
Yes, if you are using Auto Scaling group for Neo4j you need to set a cluster. As #stefan-armbruster mentioned, you need to Neo4j Enterprise edition for that. In that case it's master/slave setup.
Neo4j has its own solution for Cluster management, instead of Zookeeper.
But with AWS and EC2 there are few open question, how to properly deploy Neo4j with Auto Scaling group.
From configuration file perspective
* You need to maintain unique clusterId for each machine in cluster.
* You need to know ip addresses/hostnames of other machines in cluster.
Neo4j Enterprise edition features clustering, see the docs on this. With some well written scripts around that to configure the new instances properly I don't see a reason why AWS autoscale should not work.

How to Install LAMP on AWS EC2

Amazon 7*24 online support has been so good that why Amazon EC2 has been selected as one of the most common website hosting service, like Magento store.
But AWS EC2 is not as easy as cPanel! That's why I maintain and share my updated experiences in here!
We use Amazon Lunix because we believe we can get a better support from Amazon
This Tutorial has been always updated by Amazon and very helpful
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/install-LAMP.html
Here is just a summary of all steps, for details for above Amazon on-line tutorial
https://github.com/johnjyin/Install-LAMP-Magento-on-AWS-EC2/blob/master/Install%20LAMP%20on%20AWS%20EC2.txt