Skip to content

[FLINK-6447] update aws/emr docs#3828

Closed
alpinegizmo wants to merge 2 commits intoapache:masterfrom
alpinegizmo:6447-update-aws-emr-docs
Closed

[FLINK-6447] update aws/emr docs#3828
alpinegizmo wants to merge 2 commits intoapache:masterfrom
alpinegizmo:6447-update-aws-emr-docs

Conversation

@alpinegizmo
Copy link
Contributor

EMR now has explicit Flink support, so there's no need to install Flink by hand unless you need something custom.

Copy link
Contributor

@greghogan greghogan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alpinegizmo a few thoughts; +1 to updating this for this release!

Flink is a supported application on Amazon EMR. Basically all you have to do is choose Flink as an application, along with whatever
else you need, and configure the instances and roles. [Amazon's documentation](http://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-flink.html) gives all the details.

<img src="{{ site.baseurl }}/fig/flink-on-emr.png" class="img-responsive">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this png be deleted from the repo?

### Standard EMR Installation

The EMR documentation contains [examples showing how to start an EMR cluster](http://docs.aws.amazon.com/ElasticMapReduce/latest/ManagementGuide/emr-gs-launch-sample-cluster.html). You can follow that guide and install any EMR release. You don't need to install *All Applications* part of the EMR release, but can stick to *Core Hadoop*:
Flink is a supported application on Amazon EMR. Basically all you have to do is choose Flink as an application, along with whatever
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about something like "Flink is a supported application on Amazon EMR. Amazon's documentation describes configuring Flink, creating and monitoring a cluster, and working with jobs."?


The EMR documentation contains [examples showing how to start an EMR cluster](http://docs.aws.amazon.com/ElasticMapReduce/latest/ManagementGuide/emr-gs-launch-sample-cluster.html). You can follow that guide and install any EMR release. You don't need to install the *All Applications* part of the EMR release, but can stick to *Core Hadoop*.

When creating your cluster, make sure to setup [IAM roles](http://docs.aws.amazon.com/ElasticMapReduce/latest/ManagementGuide/emr-iam-roles.html) allowing you to access your S3 buckets if required.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about something like "When creating a cluster, access to S3 buckets requires configuration of IAM roles."? And prefix with our "note" warning?

### Custom EMR Installation

When creating your cluster, make sure to setup [IAM roles](http://docs.aws.amazon.com/ElasticMapReduce/latest/ManagementGuide/emr-iam-roles.html) allowing you to access your S3 buckets if required.
The standard installation (above) is easier, but if you need to use a version of Flink that Amazon doesn't support,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about something like "Amazon EMR services are regularly updated to new releases but a version of Flink which is not available can be manually installed within a stock EMR cluster."?

@alpinegizmo
Copy link
Contributor Author

@greghogan Thanks for the feedback!

@StephanEwen
Copy link
Contributor

+1 to merge this!

StephanEwen pushed a commit to StephanEwen/flink that referenced this pull request May 6, 2017
@asfgit asfgit closed this in 6c48f9b May 6, 2017
fanyon pushed a commit to fanyon/flink that referenced this pull request May 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants