I have installed 'Mysql Workbench 6.3 CE' on my windows 7 laptop, I have my Hadoop 3 node cluster setup on Amazon EC2 Instance. So the setup is something like this: # Local notebook: Mysql server + Mysql workbench# AWS: EC2 Hadoop instanceAnd you want to EXPORT data from your local notebook to EC2 Hadoop?I assume you want to do this (replace the indicator name with your own) # 1.
![]()
Hi, I want to install windows 7 on Amazon EC2. Is it possible? If possible how to do that? I got this doubt because, i do remember somewhere reading that you can only install windows server 2003 on amazon ec2. Thanks, Sarvesh No, not possible. Carey Frisch.
Export your database table to a file# execute 'mysqldump -u yourdbusername -p yourdbname dbname.sql'# 2. Copy the file to ec2 hadoop instance# ssh copy to remote host 'scp dbname.sql ubuntu@yourhadoopip -i yourhapooppemkey'# 3. Ssh to yourhadoopip and do the import.If you intend to connect FROM AWS EC2 to your LOCAL laptop, that is another story.Short answer: Not your way. If you just want to put data to hadoop, use above export and import step.Longer answer: you can create a temporary SSH reverse tunnel to allow the cloud EC2 server connect to your local notebook. It is tedious and you need good network knowledge to fix it if it doesn't work.Here is an example:.
This is not as easy because you need to know i. You notebook public IP address ii. Allow inbound for that inbound port inside VPC security group,etc.
![]()
What is the current way of installing Docker on an AWS EC2 instance running the AMI?There has been and now I want to know if anything has changed.Until now, I have been using yum install docker and do get a Docker versioned at 1.12.6, build 7392c3b/1.12.6 right now (3/3/2017). However, tells me that there are already newer releases.I remember the official Docker (package) repository having a package named docker-engine replacing docker some time ago and now they seem to split the package up into docker-ce and docker-ee, where e.g. 'Docker Community Edition (Docker CE) is not supported on Red Hat Enterprise Linux.' So is or will it still be correct to use the above to get the latest stable Docker version on EC2 instances running the AMI or do I need to pull the package from somewhere else (and if so which one, CE or EE)? The question is whether I can continue to do it like this. As already mentioned it'll install me Docker versioned at 1.12 which is already one if not more minor version updates behind the latest stable release (1.13, before CE/EE) and I wonder if this is due to the usual repository update delay or because the guide and package simply being outdated which requires some replacement work done by me (e.g.
Somehow getting Docker from their own repository?). Also concerning the latest EE announcement which might change something.–Mar 5 '17 at 4:27. To get Docker running on the AWS AMI you should follow the steps below (these are all assuming you have ssh'd on to the EC2 instance).Update the packages on your instanceec2-user $ sudo yum update -y.Install Dockerec2-user $ sudo yum install docker -y.Start the Docker Serviceec2-user $ sudo service docker start.Add the ec2-user to the docker group so you can execute Docker commands without using sudo.ec2-user $ sudo usermod -a -G docker ec2-userYou should then be able to run all of the docker commands without requiring sudo. After running the 4th command I did need to logout and log back in for the change to take effect. Like I already mentioned in the question, this indeed works, but installs an outdated version of Docker (still version 1.12.6 on ).
While I myself have switched to the Ubuntu image for my EC2 instances, the real thing I wanted to know is how to install one of the current versions of Docker on an AMI image. Because there (at least at the time of the question) was no obvious way to either get an up-to-date Docker CE or a Docker EE installation. That is what this question was about in the first place and that's the reason why I cannot accept it without hesitation. Thank you anyways!–May 27 '17 at 23:52.
The hardest part to figure all of this out was the container-selinux requirement. Just find the latest version in and install that first. In addition EC2 instances may not have a proper entropy generator so haveged may need to be installed.The rest is taken from with the addition of haveged and firewalld. All these have to be done as root so sudo appropriately. In addition to my previous answer. If you use Terraform, I have also created a Terraform module that can be used to create a Docker SwarmThe difference between the approach I had done previously vs the approach I am presently doing with the terraform module is to utilize the AWS provided Docker packages. This does not include the full docker-compose and what not, but you don't require those packages normally in a server.Because I am using the one Amazon had provided, it is no longer the latest 18.09 version but the 18.06 version.
![]()
However, the set up is simpler and I don't have to play catch up to container-selinux.The only external dependency I use is EPEL to get haveged because you still need a good random source for some applications.I also relied on the AWS security groups rather than explicitly setting up firewalld and used the SELinux setting that is defaulted in the AMI image.
![]() Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |