[AWSFNDN-22] aws-s3-connector: Option for not using credentials Created: 09/Feb/21  Updated: 13/Apr/21  Resolved: 11/Feb/21

Status: Closed
Project: AWS foundation (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0-cloud

Type: New Feature Priority: Neutral
Reporter: Jesus Alonso Assignee: Jesus Alonso
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to AWSFNDN-25 Port AWSFNDN-22 commits to master Closed
supersession
supersedes EXTDAM-125 Investigation. Automatic authenticati... Closed
Template:
Acceptance criteria:
Empty
Documentation update required:
Yes
Date of First Response:
Epic Link: Imaging and External DAM

 Description   

According to CLOUD-70, we are not going to use credentials in S3 but the instance will have attached a role with the needed permissions. Thus, we need to update the aws-s3-connector code to:

  • Do not validate whether the credentials exists
  • Create the s3-client and presigner without credentials.

We will use the following configuration variables to detect when this is needed or not:

  • magnolia.aws.validateCredentials
  • magnolia.aws-s3.useCredentials

 



 Comments   
Comment by Michael Duerig [ 18/Mar/21 ]

Created the epic AWSFNDN-23 to track this and future changes like this one.

Generated at Sun Feb 11 23:23:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.