<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Doug Jaworski &#187; MAC</title>
	<atom:link href="http://www.dougjaworski.com/blog/tag/mac/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dougjaworski.com/blog</link>
	<description></description>
	<lastBuildDate>Sun, 25 Jul 2010 17:03:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>How to Install Amazon EC2 Tools on a MAC</title>
		<link>http://www.dougjaworski.com/blog/how-to-install-amazon-ec2-tools-on-a-mac/</link>
		<comments>http://www.dougjaworski.com/blog/how-to-install-amazon-ec2-tools-on-a-mac/#comments</comments>
		<pubDate>Sun, 25 Jul 2010 03:55:55 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[Cloud]]></category>
		<category><![CDATA[Amazon]]></category>
		<category><![CDATA[AWS]]></category>
		<category><![CDATA[EC2]]></category>
		<category><![CDATA[MAC]]></category>

		<guid isPermaLink="false">http://www.dougjaworski.com/blog/?p=201</guid>
		<description><![CDATA[This tutorial is intended to get you started with the Amazon EC2 API Tools on a Mac. I am running this on a PowerBook Pro with Snow Leopard.  The EC2 API Tools are a client interface to EC2 web service and extend the AWS Management Console. Create Directories Create a directory to store your AWS [...]]]></description>
			<content:encoded><![CDATA[<p>This tutorial is intended to get you started with the Amazon EC2 API Tools on a Mac. I am running this on a PowerBook Pro with Snow Leopard.  The EC2 API Tools are a client interface to EC2 web service and extend the AWS Management Console.</p>
<p><strong>Create Directorie</strong>s</p>
<p>Create a directory to store your AWS Keys and Certificates. For this tutorial we will be creating 2 directories.</p>
<p>The first directory is for your AWS Security Credentials and is typically placed in your home directory.</p>
<pre>mkdir ~/.ec2</pre>
<p>We also need a directory to place the EC2 API Tools. This can be placed in any directory location of your liking. As this is on a Mac, we will be placing in our /Applications directory.</p>
<pre>mkdir /Applications/ec2</pre>
<p><strong>Create an AWS Account</strong></p>
<p>You will first need to create an Amazon AWS account and an AWS EC2 account. This will require a credit card however you will only be charged for what you use.</p>
<p>To create an account, you need to go to http://aws.amazon.com and sign up for the service.</p>
<p>After you have created your EC2 account, you will need to create a X.509 certificate. To locate, select the your Account tab and scroll down to Access Credentials section and select <strong>Create a new Access Key</strong>. Once this is completed, you will need to save the private key file and the X.509 certificate.</p>
<p>Download both the &#8220;private Key&#8221; file and the &#8220;X.509 Certificate&#8221; file. Typically this can be in a directory of your liking but for the sake of this tutorial we will place it in your home ~./ec2. The private key file will be names something like ﻿<span style="color: #222222; font-family: sans-serif; font-size: 13px; line-height: 19px;">pk-xxxxxxxxxxxxxxxxxxxxxx.pem and the X.509 Certificate file will be named something like cert-xxxxxxxxxxxxxxxxxxxxxx.pem.</span></p>
<p><strong>Download and Install EC2 API Tools</strong></p>
<p>Download the <a href="http://developer.amazonwebservices.com/connect/entry.jspa?externalID=351&amp;categoryID=88">Amazon EC2 API Tools</a> and make sure you have the most current version. Since this tutorial was targeted for the Mac users, the default location for the the file is in your Downloads directory. Simply copy the contents of this file to you /Applications/ec2 directory.</p>
<pre>cp Downloads/ec2-api-tools-1.3-53907 /Applications/ec2</pre>
<p>A prerequisite for EC2 API Tools is Java, as we are on a Mac, it is already installed and should have JAVA_HOME set. To verify you have JAVA_HOME set, you can simply open up a terminal window and type the following:</p>
<pre>echo $JAVA_HOME</pre>
<p>It should return something like this:</p>
<pre>﻿/System/Library/Frameworks/JavaVM.framework/Home/</pre>
<p>If not, verify that you have java installed and set the JAVA_HOME Variable as defined in the next section.</p>
<p><strong>Define your Enviornment</strong></p>
<p>There are many ways to customize your environment variables with OS X.  I personally like you use .bash_profile however you might elect to use another method, this way just works out nice for me so customize to your liking.</p>
<p>﻿Open or create .bash_profile in your home directory with your favorite text editor and update with the following. Your items will have unique names when generated.</p>
<pre>export JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Home/</pre>
<pre>export EC2_HOME=/Applications/ec2</pre>
<pre>export EC2_PRIVATE_KEY=~/.ec2/pk-xxx.pem</pre>
<pre>export EC2_CERT=~/.ec2/cert-xxx.pem</pre>
<pre>export EC2_ACCNO=0000-0000-0000</pre>
<pre>export ACCESS_KEY=BGIRITQM7O6ZZF3R2ODC</pre>
<pre>export SECRET_KEY=lDgGzXoTKukVmZw7q7Donx/O6Jc/kFQ4P889zQu</pre>
<pre>export PATH=$PATH:$EC2_HOME/bin</pre>
<p> </p>
<div><strong>Environment Definitions</strong></div>
<div>EC2_HOME = Location of EC2 API Tools</div>
<div>EC2_PRIVATE_KEY = AWS Private Key</div>
<div>EC2_CERT = X.509 Certificate</div>
<div>EC2_ACCNO = Your EC2 Account Number which is located on the account page of your AWS account</div>
<div>ACCESS_KEY = Your AWS Access Key located under AWS Access Credentials</div>
<div>SECRET_KEY = Your AWS Secret Access Key located under AWS Access Credentials</div>
<p>After saving this file, you will need to source your .bash_profile so it will export your new variables. From a command prompt run the following command.</p>
<pre>source ~/.bash_profile</pre>
<p><strong>Create an EC2 Keypair</strong></p>
<p>In order to launch an Amazon AMI, you need a named keypair that is yours and yours alone. You can call your keypair anything you like. I called mine my-keypair for the sake of this tutorial. You will then want to move this keypair to ~/.ec2 and secure the file so only you have access to this file. You must keep this key private and secure as it is the keys to the kingdom.</p>
<pre>ec2-add-keypair my-keypair &gt; ~/.ec2/my-keypair.pem</pre>
<p> </p>
<pre>chmod 600 ~/.ec2/my-keypair.pem</pre>
<p> </p>
<p><strong>Testing in Out</strong></p>
<p>To confirm you have it setup correctly, you can simply query publicly available AMI&#8217;s with the following command</p>
<pre>ec2-describe-images -a</pre>
<p>Simple as that. In my next tutorial, I will document how to launch and customize an Ubuntu 10.04 AMI with an EBS Volume for persistant storage.</p>
<p> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.dougjaworski.com/blog/how-to-install-amazon-ec2-tools-on-a-mac/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Use iWork to Cool 15inch MacBook Pro</title>
		<link>http://www.dougjaworski.com/blog/use-iwork-to-cool-15inch-macbook-pro/</link>
		<comments>http://www.dougjaworski.com/blog/use-iwork-to-cool-15inch-macbook-pro/#comments</comments>
		<pubDate>Sat, 22 May 2010 18:26:41 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[HowTo]]></category>
		<category><![CDATA[MAC]]></category>

		<guid isPermaLink="false">http://www.dougjaworski.com/blog/?p=190</guid>
		<description><![CDATA[If you are running a MacBook Pro, you know they run hot. I solved this issue on the cheap by recycling an iWork Retail Eddition box to allow for more airflow under the the MacBook. All you need is to allow a bit of air to flow on the bottom surface and this box happens [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: left;"><a href="http://www.dougjaworski.com/blog/wp-content/uploads/2010/05/iwork.jpg"><img class="aligncenter size-full wp-image-192" title="iwork" src="http://www.dougjaworski.com/blog/wp-content/uploads/2010/05/iwork.jpg" alt="" width="639" height="426" /></a><br />
If you are running a MacBook Pro, you know they run hot. I solved this issue on the cheap by recycling an <a href="http://www.apple.com/iwork/" target="_blank">iWork</a> Retail Eddition box to allow for more airflow under the the MacBook. All you need is to allow a bit of air to flow on the bottom surface and this box happens to be just the right hight to accomplish with ease.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dougjaworski.com/blog/use-iwork-to-cool-15inch-macbook-pro/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Network Connect with OS X 10.6 Snow Leopard</title>
		<link>http://www.dougjaworski.com/blog/network-connect-with-os-x-10-6-snow-leopard/</link>
		<comments>http://www.dougjaworski.com/blog/network-connect-with-os-x-10-6-snow-leopard/#comments</comments>
		<pubDate>Thu, 31 Dec 2009 17:06:46 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[HowTo]]></category>
		<category><![CDATA[MAC]]></category>
		<category><![CDATA[Snow Leopard]]></category>

		<guid isPermaLink="false">http://www.dougjaworski.com/blog/?p=168</guid>
		<description><![CDATA[I recently performed a clean install of OS X Snow Leopard on my PowerMac Pro and ran into issues when trying to connect to my companies SSL VPN. While there are numerous posts found on the web, none seem to pertain to a clean install of Snow Leopard. After debugging the issue furtherI found that [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.dougjaworski.com/blog/wp-content/uploads/2009/12/nc1.jpg"><img class="alignleft size-full wp-image-175" title="nc" src="http://www.dougjaworski.com/blog/wp-content/uploads/2009/12/nc1.jpg" alt="" width="128" height="128" /></a>I recently performed a clean install of OS X Snow Leopard on my PowerMac Pro and ran into issues when trying to connect to my companies SSL VPN. While there are numerous posts found on the web, none seem to pertain to a clean install of Snow Leopard. After debugging the issue furtherI found that Network Connect was still having permission issues when trying to connect via the Network Connect client.</p>
<p><strong>Here is what I did to resolve the problem:</strong></p>
<p>Install <a href="http://www.dougjaworski.com/~doug/software/OSX/NetworkConnect6.1.dmg">NetworkConnect.dmg</a> with the version that your Juniper SSL VPN device supports. In my case, it was <a href="http://www.dougjaworski.com/~doug/software/OSX/NetworkConnect6.1.dmg">6.1</a></p>
<p>Open up Terminal and type the following commands followed by enter after each line. As you will be using sudo, you may be prompted for your password as well:</p>
<pre>sudo chmod 755 /usr/local/juniper/nc/6.1.0/
sudo mkdir '/Applications/Network Connect.app/Contents/Frameworks'</pre>
<p>I original found the above steps at various sites including the Juniper support forums but I was still running into permission issues. After digging further into the log files I found this and determined that there must be some sort of elevated root permission that needs to update some network settings that can only be done as a super user.</p>
<pre>ncproxyd[19016] ncproxyd.info ncproxyd exiting status 1 (ncproxyd.cpp:92)
ncproxyd[19054] ncproxyd.error Failed to gain root privileges: Operation not permitted</pre>
<p>To fix this you must modify the permissions of ncproxyd</p>
<pre>chmod 4711 /usr/local/juniper/nc/6.3.0/ncproxyd</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.dougjaworski.com/blog/network-connect-with-os-x-10-6-snow-leopard/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
