You may be interested in trying out the bosh-bootloader project,
https://github.com/cloudfoundry/bosh-bootloader, that the CF Infrastructure
team has been developing in part as a replacement for the `bosh aws create`
command. Currently, you can configure it with access to an AWS account and
then run `bbl up` to create a new CloudFormation stack to support BOSH, CF,
and Concourse, deploy a BOSH director with bosh-init, and configure it with
a cloud config corresponding to the networking and other resources in that
CloudFormation stack. If usage isn't clear from the CLI and the GitHub
repo, I expect the CF Infrastructure team would be happy to answer
questions about it on the cf-bosh or cf-dev mailing lists and in the
#infrastructure channel on the CF OSS Slack.

Best,
Eric, CF Runtime Diego PM

On Thu, Oct 27, 2016 at 7:54 PM, xiaoshan fang <tech_fang(a)hotmail.com>
wrote:

Thank you very much sean. I am new to bosh and cloudfoundry, could you pls
give more detail docs about deploying cloudfoundry with bosh-init (not
using bosh aws create)?

I am following the http://docs.cloudfoundry.org/deploying/aws/index.html#
prereqs. It use bosh aws create to prepare the aws environment, and the
use bosh-init to deploy bosh.