You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Stephan Erb (JIRA)" <ji...@apache.org> on 2016/02/12 21:13:18 UTC

[jira] [Commented] (AURORA-1618) Deploying Aurora on AWS

    [ https://issues.apache.org/jira/browse/AURORA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145214#comment-15145214 ] 

Stephan Erb commented on AURORA-1618:
-------------------------------------

Maybe one of our existing AWS users can help us here /cc [~tonydong3] [~benley] [~SteveNiemitz]

> Deploying Aurora on AWS
> -----------------------
>
>                 Key: AURORA-1618
>                 URL: https://issues.apache.org/jira/browse/AURORA-1618
>             Project: Aurora
>          Issue Type: Story
>          Components: Documentation
>            Reporter: Stephan Erb
>              Labels: documentation
>
> AWS tends to be one of the more popular deployment targets these days. Especially for new adopters of Aurora (and Mesos), this can be quite tricky. 
> We should provide a high level guide covering the basic ground necessary for a solid deployment.
> Potential issues/questions that should probably be covered:
> * recommended instance type?
> * mapping of components onto regions and availability zones?
> * do I need EBS for my master and scheduler nodes?
> * recommended way how to bind ip/hostnames of the different components, so that they can reliably talk to each other
> * ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)