Hybrid public/private cloud

Seamless

Big Cleanup

If you want to remove the extension, you have to remove the nodes from the cluster with an API call:

curl -X PUT 10.0.2.25:9200/_cluster/settings -H 'Content-Type: application/json' -d '{"transient" : {"cluster.routing.allocation.exclude._ip":"10.100.68.139" } }'

This command blocks further assignments and causes the cluster to move all shards away from this node. After the action, no more shards are assigned, and you can simply switch off the node.

Conclusion

The hybrid cloud thrives, because admins can transfer scripts and Playbooks seamlessly from their environment to the cloud world. Although higher quality cloud services exist than those covered in this article (AWS also has Elasticsearch as a Service), these services typically have only limited suitability for direct docking. To use them, you would have to take into account configuring the peculiarities of the respective cloud provider. With VMs in Microsoft Azure, however, the example shown here would work directly, so the user would only have to replace the CloudFormation part with an Azure template.

Infos

AWS: https://aws.amazon.com/
Azure: https://azure.microsoft.com
Google Cloud: https://cloud.google.com
Ansible: https://www.ansible.com
"Data security in the AWS Cloud" by Konstantin Agouros, Linux Magazine , issue 229, December 2019, pg. 34, http://www.linux-magazine.com/Issues/2019/229/Data-Security-in-AWS
LUKS: https://gitlab.com/cryptsetup
Listings for this article: ftp://ftp.linux-magazine.com/pub/listings/admin-magazine.com/55/
Fortinet's script template: https://github.com/fortinet/aws-cloudformation-templates/tree/master/HA/6.0

The Author

Konstantin Agouros is Head of Open Source Projects at matrix technology AG, where he and his team advise customers on open source and cloud topics. His latest book Software Defined Networking: SDN-Praxis mit Controllern und OpenFlow [Practical Applications with Controllers and OpenFlow ] (in German) is published by de Gruyter.

« Previous 1 2 3 4