It would appear that instances do not have arns. Is this an IAM thing?

````
fetch:odorm jane$ node build-node.js
{ InstanceId: 'i-aa8c1241',
  ImageId: 'ami-020bc76a',
  State: { Code: 16, Name: 'running' },
  PrivateDnsName: 'ip-10-224-222-162.ec2.internal',
  PublicDnsName: null,
  StateTransitionReason: null,
  KeyName: 'jane-fetch-aws-root',
  AmiLaunchIndex: 0,
  ProductCodes: [],
  InstanceType: 't1.micro',
  LaunchTime: Mon Sep 22 2014 10:23:28 GMT-0400 (EDT),
  Placement:
   { AvailabilityZone: 'us-east-1a',
     GroupName: null,
     Tenancy: 'default' },
  KernelId: 'aki-919dcaf8',
  Monitoring: { State: 'disabled' },
  SubnetId: 'subnet-bd4d85ca',
  VpcId: 'vpc-c03d95a5',
  PrivateIpAddress: '10.224.222.162',
  PublicIpAddress: '54.86.62.136',
  Architecture: 'x86_64',
  RootDeviceType: 'ebs',
  RootDeviceName: '/dev/sda1',
  BlockDeviceMappings:
   [ { DeviceName: '/dev/sda1', Ebs: [Object] },
     { DeviceName: '/dev/sdk', Ebs: [Object] } ],
  VirtualizationType: 'paravirtual',
  ClientToken: null,
  Tags: [],
  SecurityGroups:
   [ { GroupName: 'gsa-ssh-inbound', GroupId: 'sg-d5f1a7b0' },
     { GroupName: 'jane_personal_ssh', GroupId: 'sg-5ca8f939' } ],
  SourceDestCheck: true,
  Hypervisor: 'xen',
  NetworkInterfaces:
   [ { NetworkInterfaceId: 'eni-de038ea8',
       SubnetId: 'subnet-bd4d85ca',
       VpcId: 'vpc-c03d95a5',
       Description: 'sendak-subnode-7937-public',
       OwnerId: '144433228153',
       Status: 'in-use',
       PrivateIpAddress: '10.224.222.162',
       SourceDestCheck: true,
       Groups: [Object],
       Attachment: [Object],
       Association: [Object],
       PrivateIpAddresses: [Object] } ],
  EbsOptimized: false }
fetch:odorm jane$ j
````
my own case inconsistency and underlines vs dashes is kicking my own ass frankly
oh amazons
hey look some shit that ACTUALLY works!