AWS CLI to the rescue. It’s really quick and easy. Install AWS CLI, add your keys to the credentials and then fire away.

• AWS CLI Reference (pip install awscli) of course you have Python
• Configuring AWS CLI (~/.aws/credentials) use profiles for qa, dev etc.
• AWS ls command (aws s3 ls s3://mybucket)
• AWS cp command (aws s3 cp s3://mybucket/test.txt .) create all your aliases

Here are some of mine

alias s3ls=’function _s3ls(){ aws s3 ls s3://”$@” ; }; _s3ls’
alias s3get=’function _s3get(){ aws s3 cp s3://”$@” . ; }; _s3get’
alias s3getdir=’function _s3getdir(){ aws s3 cp s3://”$@” . –recursive ; }; _s3getdir’

Pretty straightforward. If you don’t have a samba share here’s How to Create a Network Share Via Samba Via CLI (Command-line interface/Linux Terminal). So now you have a Samba Share on Linux.

Here’s a snippet of my /etc/samba/smb.conf that contains the Linux folder on my VM that I would like to access from the Mac. (In your Mac: it will show up under /Volumes/vm_codebase).
Of course you can ssh into your Linux env, but this is more like mounting onto your Mac.

[vm_codebase]
path = /home/shivdev/codebase
available = yes
valid users = shivdev
read only = no
browseable = yes
public = yes
writable = yes

From your Mac. Open Finder : Go –> Connect to Server… –> smb://vm –> Chose vm_codebase

Now you will see it under /Volumes/vm_codebase and is accessible like a regular folder.

I was trying a simple sed -i on my Mac and was running into

# Does NOT work on Mac
$ sed -i ‘s/^192.168.*vm/192.168.1.12 vm/’ /etc/hosts
sed: 1: “/etc/hosts”: extra characters at the end of h command

A quick google search resulted in stackoverflow getting sed error which has the solution. Apparently, Mac uses BSD sed and Linux uses GNU sed which have different set of arguments. So provide the extra argument in Mac as shown below.

# Adding the extra argument will work on your Mac
$ sed -i ” ‘s/^192.168.*vm/192.168.1.12 vm/’ /etc/hosts