[
https://issues.apache.org/jira/browse/FLINK-8513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-8513:
----------------------------------
Labels: auto-unassigned stale-minor (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Add documentation for connecting to non-AWS S3 endpoints
> --------------------------------------------------------
>
> Key: FLINK-8513
> URL: https://issues.apache.org/jira/browse/FLINK-8513
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / FileSystem, Documentation
> Reporter: chris snow
> Priority: Minor
> Labels: auto-unassigned, stale-minor
>
> It would be useful if the documentation provided information on connecting to
> non-AWS S3 endpoints when using presto. For example:
>
> ----
> You need to configure both {{s3.access-key}} and {{s3.secret-key}} in Flink's
> {{flink-conf.yaml}}:
> {code:java}
> s3.access-key: your-access-key
> s3.secret-key: your-secret-key{code}
> If you are using a non-AWS S3 endpoint (such as [IBM's Cloud Object
> Storage|https://www.ibm.com/cloud/object-storage]), you can configure the S3
> endpoint in Flink's {{flink-conf.yaml}}:
> {code:java}
> s3.endpoint: your-endpoint-hostname{code}
> ----
>
> Source:
> [https://github.com/apache/flink/blob/master/docs/ops/deployment/aws.md]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
