Hi, Rafal,

I answered some related questions about deploying Diego alongside CF on AWS
on the cf-dev mailing list at
https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/thread/F74QF6KSWDVBD2B2A3X2NEYA6UW4NLA3/,
which you may find helpful. It's tailored for Diego 0.1442.0, but I don't
think there's much difference between that and the IaaS settings expected
for Diego 0.1437.0. In terms of additional AWS infrastructure, you should
need only some extra subnets for the Diego VMs, and optionally an ELB to
balance traffic across the Diego SSH proxies. (You could also use your CF
subnets as long as you coordinate the network settings between your CF and
Diego manifests so as not to have them collide over IP allocations, but for
a first attempt it'd be much easier just to provision separate Diego
subnets.)

You're correct that the BOSH-Lite iaas-settings.yml file is significantly
different in its values from one usable for AWS. That's a natural
consequence of containing all of those IaaS-level differences in a single,
tightly scoped stub. That containment should mean, however, that the other
stubs are free of IaaS-specific details.

I also mentioned on the cf-dev thread that the Diego team will soon be
providing some more supported information about deploying Diego to AWS, and
in the longer term we look forward to using and integrating with the
tooling that will come at some point from the CF Infrastructure and CF
Release Integration teams.

Best,
Eric, CF Runtime Diego PM

On Tue, Jan 19, 2016 at 7:20 AM, Rafal Radecki <radecki.rafal(a)gmail.com>
wrote:

Is there anywhere a list of things which are needed to add diego to cf on
infrastructural level? Which manifest should be used for iaas-settings.yml:
the one from diego-release or the one from
https://github.com/cloudfoundry-incubator/diego-release/issues/71 ?