Hi Guys,

I am fairly new to Bosh, CF and Vagrant, so most probbably i am doing some newbie mistake. Unfortunately i am unable to resolve it as of now.
My problem is that i am trying to run Bosh lite with AWS provider. After doing all the setup in AWS, setting up environment variables, etc, i run

vagrant up --provider=aws

i was getting problems due to missing AMI ImageID, so i entered there
'ami-8612d3e9' (which i found to be some Ubuntu image for amd64, using ebs)

Now after vagrant completes, it tells me where it created the VM, and indeed it is there and i can ssh to it, but apparently bosh is missing
bosh target... is not working
and on the image there is nothing installed (no monit, no ruby, nothing)

i also tried running the packer script , which worked for quite some time, then it ended with success telling at the end
-----------
==> amazon-ebs: Modifying attributes on AMI (ami-1acf6179)...
amazon-ebs: Modifying: description
==> amazon-ebs: Modifying attributes on AMI (ami-b00f5ed0)...
amazon-ebs: Modifying: description
==> amazon-ebs: Modifying attributes on AMI (ami-1446f274)...
amazon-ebs: Modifying: description
==> amazon-ebs: Modifying attributes on snapshot (snap-bec150af)...
==> amazon-ebs: Modifying attributes on snapshot (snap-f8e8047b)...
==> amazon-ebs: Modifying attributes on snapshot (snap-e987a8c7)...
==> amazon-ebs: Modifying attributes on snapshot (snap-0fa12073608261dac)...
==> amazon-ebs: Modifying attributes on snapshot (snap-343e4006)...
==> amazon-ebs: Modifying attributes on snapshot (snap-f9d55877)...
==> amazon-ebs: Modifying attributes on snapshot (snap-ffecf6c8)...
==> amazon-ebs: Modifying attributes on snapshot (snap-6f10c4ff)...
==> amazon-ebs: Terminating the source AWS instance...
==> amazon-ebs: Cleaning up any extra volumes...
==> amazon-ebs: No volumes to clean up, skipping
==> amazon-ebs: Deleting temporary security group...
==> amazon-ebs: Deleting temporary keypair...
==> amazon-ebs: Running post-processor: vagrant
==> amazon-ebs (vagrant): Creating Vagrant box for 'aws' provider
amazon-ebs (vagrant): Using custom Vagrantfile: templates/vagrant-aws.tpl
amazon-ebs (vagrant): Compressing: Vagrantfile
amazon-ebs (vagrant): Compressing: metadata.json
Build 'amazon-ebs' finished.

==> Builds finished. The artifacts of successful builds are:
--> amazon-ebs: AMIs were created:

ap-northeast-1: ami-26ed8541
ap-southeast-1: ami-1acf6179
ap-southeast-2: ami-acd8e3cf
eu-west-1: ami-0820007b
sa-east-1: ami-b748d0db
us-east-1: ami-8f160398
us-west-1: ami-b00f5ed0
us-west-2: ami-1446f274
--> amazon-ebs: 'aws' provider box: bosh-lite-aws-ubuntu-trusty-ami-8612d3e9.box
ubuntu(a)ip-172-31-31-187:~/bosh-lite/packer$ ls

---------------------

but now i am not sure what to do with this. Tried to add this Box to vagrant, and then modified Vagrantfile to use it's name and box version, but unfortunately - nothing changed.

so now i am a bit at loss, i feel like i miss some small step somewhere but i cannot understand - where

Thanks in advance!

Hi Vladimir!

You are in the right path to solve this, but there is on problem. You
specified an AMI that doesn't contain BOSH installed.

What you can do, is to log in into your AWS console, launch the Ec2 wizard
and when selecting the image, search for BOSH Lite in the community images.
Take note of the most recent one and use that AMI ID in the Vagrant file.

Let me know if you need further help.

Thank you!

JP

turned out i had set region to eu-central-1, even if the documentation said that there are no bosh images, i decided it is outdated... now it works! (with eu-west-1)