I am trying to make a callout to AWS S3 using named credentials and Apex

The named credential is set up as follows

Label: AWS S3
Name: AWS_S3
URL: https://bucket-name.s3.amazonaws.com
Identity Type: Named Principal
Authentication Protocol: AWS Signature Version 4
AWS Access Key: AKIAxxxxxx
AWS Secret Access Key: xxxxxx
AWS Region: ap-southeast-2
AWS Service: s3
Generate Authorization header: true
Merge fields in header: false
Merge fields in body: false

The Apex class is very simple

HttpRequest req = new HttpRequest();
Http http = new Http();
HTTPResponse res = http.send(req);                
return res.getBody();

The response body contains the following:

SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method.AKIAxxxxx

I have used the same bucket, endpoint and credentials using Postman and am able to successfully return the list of objects in the bucket so it is not an IAM permissions issue

There have been a couple of similar questions on stackexchange but unfortunately they do not provide any resolution or assistance in this case: AWS Signature Version 4 Using Named Credentials AWS Signature Version 4 Named Credential doesn't seems like working

I've tried looking for code samples or further pointers in the Apex documentation but it doesn't really give any further guidance on how to proceed or correctly set this up so I'm a bit stuck

  • 1
    this AWS feature came out in Summer 19 (V46). Is your Apex class at V46?
    – cropredy
    Sep 24, 2019 at 1:18
  • Yes <?xml version="1.0" encoding="UTF-8"?> <ApexClass xmlns="urn:metadata.tooling.soap.sforce.com" fqn="s3Connector"> <apiVersion>46.0</apiVersion> <status>Active</status> </ApexClass>
    – Devst
    Sep 24, 2019 at 1:35
  • Interestingly enough a PUT operation to create a file with the same credentials works just fine!
    – Devst
    Sep 24, 2019 at 2:34

1 Answer 1


Okay so the answer is actually pretty straightforward so am leaving it here for anybody else struggling with the same issue.

The endpoint needs to have a trailing / so either your URL in the named credential needs to look like this https://bucket-name.s3.amazonaws.com/ Or when you are making the callout append the / in the Apex like this req.setEndpoint('callout:AWS_S3/');

  • 2
    Thanks @devst. I was facing the same issue and now it got resolved :)
    – Amit Singh
    Apr 21, 2020 at 19:27
  • thanks for the help
    – Raphael D
    Mar 14, 2021 at 10:49
  • with a Legacy Named Cred - this works for us with or without the trailing slash.
    – identigral
    Dec 6, 2022 at 19:08

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .