<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Vmware DaaS virtualdesktop to AWS server/database tunnling and how to add DaaS to VPN in Horizon Cloud</title>
    <link>https://communities.vmware.com/t5/Horizon-Cloud/Vmware-DaaS-virtualdesktop-to-AWS-server-database-tunnling-and/m-p/2681258#M145</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If i have servers in AWS , how to connect them without opening 0.0.0.0/0 ports ( i.e allowing DaaS desktop in aws security group)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 1)&amp;nbsp; tunneling to aws servers ?&lt;/P&gt;&lt;P&gt; 2)&amp;nbsp; accessing RDS,remote database from DaaS without opening all ports( secured RDS). Because DaaS doesnt give ip. So how to add DaaS to aws security group.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Feb 2016 07:32:05 GMT</pubDate>
    <dc:creator>sanathdm</dc:creator>
    <dc:date>2016-02-26T07:32:05Z</dc:date>
    <item>
      <title>Vmware DaaS virtualdesktop to AWS server/database tunnling and how to add DaaS to VPN</title>
      <link>https://communities.vmware.com/t5/Horizon-Cloud/Vmware-DaaS-virtualdesktop-to-AWS-server-database-tunnling-and/m-p/2681258#M145</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If i have servers in AWS , how to connect them without opening 0.0.0.0/0 ports ( i.e allowing DaaS desktop in aws security group)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 1)&amp;nbsp; tunneling to aws servers ?&lt;/P&gt;&lt;P&gt; 2)&amp;nbsp; accessing RDS,remote database from DaaS without opening all ports( secured RDS). Because DaaS doesnt give ip. So how to add DaaS to aws security group.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2016 07:32:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Cloud/Vmware-DaaS-virtualdesktop-to-AWS-server-database-tunnling-and/m-p/2681258#M145</guid>
      <dc:creator>sanathdm</dc:creator>
      <dc:date>2016-02-26T07:32:05Z</dc:date>
    </item>
    <item>
      <title>Re: Vmware DaaS virtualdesktop to AWS server/database tunnling and how to add DaaS to VPN</title>
      <link>https://communities.vmware.com/t5/Horizon-Cloud/Vmware-DaaS-virtualdesktop-to-AWS-server-database-tunnling-and/m-p/2681259#M146</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your question sanathdm! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1)&amp;nbsp; &lt;SPAN class="s1"&gt;We would create an IPsec tunnel between your AWS instance and our DaaS environment, but only include whatever networks/hosts you define to traverse that tunnel.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;2)&amp;nbsp; We &lt;SPAN class="s1"&gt;are assuming this “AWS Security Group” was one created as an OU in Active directory. If this is the case, you can manage users/machines in AD just as you would with &lt;/SPAN&gt;&lt;SPAN class="s1"&gt;any other user/machine within the domain – the DaaS desktops will act as an extension of your current desktop environment. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="s1"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="s1"&gt;Can you clarify what you mean by:&amp;nbsp; “DaaS doesn’t give IP”&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="s1"&gt;DHCP can be handled by either side.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let us know if this has resolved your question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;The Horizon Air Team&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2016 17:07:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Cloud/Vmware-DaaS-virtualdesktop-to-AWS-server-database-tunnling-and/m-p/2681259#M146</guid>
      <dc:creator>davidgilon</dc:creator>
      <dc:date>2016-02-26T17:07:21Z</dc:date>
    </item>
  </channel>
</rss>

