HomeMesosphereNo notifications. 4 unresolved issues.

Provide S3 Credentials via the default AWS provider chain.
ClosedAll Users

Authored by aquamatthias on Apr 25 2017, 12:32 AM.

Details

Summary

Use the AWS java client to retrieve credentials from the default provider chain.
This results in the following provider chain:

  • use credentials provided from URI parameters
  • use credentials set via the environment
  • use credentials set via system properties
  • use default credentials set via the credentials file
  • use credentials provided via the Amazon EC2 Container Service
  • use credential defined via system configuration in akka.stream.alpakka.s3
Test Plan

Backup to an S3 storage without providing crentials:
runMain mesosphere.marathon.core.storage.backup.Backup --backup_location s3://bucket/file?region=eu-central-1

Diff Detail

Repository
rMARATHON marathon
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
Changes from before your most recent comment are hidden. Show Older Changes
jeschkies requested changes to this revision.Apr 25 2017, 12:04 PM

Thanks. I just have two questions.

src/main/scala/mesosphere/marathon/stream/UriIO.scala
110–113

I'm wondering if we should say that we first check the uri parameters and then follow the default provider chain as documented here.

Is providing the credentials in the URI save?

This revision now requires changes to proceed.Apr 25 2017, 12:04 PM

Could you also add the reference.conf section as I suggested in the bug?

aquamatthias added inline comments.Apr 26 2017, 1:50 PM
src/main/scala/mesosphere/marathon/stream/UriIO.scala
110–113

This comment describes the chain to get credentials, by also describing how the AWS default chain works.
Do you want me to change this?

The main focus of this PR is to enable credential providers, so it is not necessary to send them in the URL.

jeschkies accepted this revision.Apr 26 2017, 4:29 PM
This revision is now accepted and ready to land.Apr 26 2017, 4:29 PM
This revision was automatically updated to reflect the committed changes.