We mostly have requirements to upload files in file storage servers like AWS S3 Server, Dropbox, Google Drive, etc. This post will help in uploading files to S3 Server. We will use named credential to upload file in S3 server.
Steps for uploading file in S3 Server using named credential
- Create a named credential for AWS Credential
- Create an apex class to upload file
- Test functionality
1. Create a named credential for AWS Credential
Create a named credential with Authentication Protocol as AWS Signature Version 4.
AWS Signature Version 4 (SigV4) is the process to add authentication information to AWS API requests sent by HTTP. No need to set any header in this case. All information is shared using this named credential itself.
Named Credential Detail
| Name | S3Upload |
| Url | https://s3.amazonaws.com/salesforcecodex or https://{bucket}.s3.{region}.amazonaws.com |
| Identity Type | Named Principle |
| Authentication Protocol | AWS Signature Version 4 |
| AWS Access Key Id | {Your access key} |
| AWS Secret Access Key | {Your secret access key} |
| AWS Region | {your s3 bucket region} |
| AWS Service | s3 |
2 Create an apex class to upload file
Let us create an apex class that will upload files to the AWS S3 server. For this post, I have created one function which will take LinkedEntityId which is a record where the file is attached.
We need blob data of attachment to store in S3 Server. So we have used file content VersionData which is in blob format.
Apart from callout, we need not be required to put any header information for API requests. Named credential will take care of auth headers.
3. Test functionality
Let us test uploading of files. For testing, the below code can be executed in the developer console’s anonymous window to upload a document that is attached to the record id. This recordid can be of case, account, contact or any custom object.
AWSFileService service=new AWSFileService();
service.UploadDocuments('5002v00002qbQxWAAU');The above code can also be written in one method to make requests dynamic and used by many processes.
@AuraEnabled
public static void UploadDocToS3Server(string recordId)
{
AWSFileService service=new AWSFileService();
service.UploadDocuments(recordId);
}We can call method UploadDocToS3Server from lightning components.
References:
Signature Version 4 signing process
Checkout previous posts for similar requirements.
Uploading Files to S3 Server using Apex
15 Comments
Hi Dhanik,
Got here from the previous post about uploading to S3. I’ve tried setting this up but I’m getting an error message :
SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method.XXXXXXAWS4-HMAC-SHA256The URL I set was:
https://MYBUCKETNAME.s3.eu-west-2.amazonaws.com – is this correct?
Also – I don’t see anywhere where we use trhe filename string and ass it on – am I missing something here?
Thanks,
N
Hello N,
You have to use like this https://s3.amazonaws.com/salesforcecodex. Here salesforcecodex is bucket name, so put your bucket name in place of it. I feel it will work if you give proper detail to named credential.
Let us connect, if you face issue even after that. Connect to my linked-in profile for this.
Thank You,
Dhanik
Pingback: Download S3 File using AWS Signature Version 4.0
Hi Dhanik,
Thanks for your post. It was really helpful. I tried the same for an opportunity record but getting the below error not sure why.
System.HttpResponse[Status=Bad Request, StatusCode=400]”|
Hello Bharat,
Have you checked complete error detail using response.getBody()? This error mostly comes when our URL is not created properly. If all good from your side and still issue, please connect on linked-in or telegram. We will connect and resolve it.
Thank You,
Dhanik
Hi,
I’m receiving an Error: 400 The authorization header is malformed; the region ‘eu-central-1’ is wrong; expecting ‘us-east-1
My configuration for named Credentials:
URL: https://s3.amazonaws.com/mybucketname
AWS Region: eu-central-1
AWS Service: S3
I’m wondering what’s wrong
Hey,
Please check this post
Thank You,
Dhanik
Pingback: Cuttly Url Shortener in Salesforce | SalesforceCodex
Hi I got this error, The XML you provided was not well-formed or did not validate against our published schema salesforce when testing the code above.
Hey Geecel,
Can you check the line where you are getting errors? Let me know, so that we can connect and resolve your issue.
Thank You,
Dhanik
I was able to resolved the issue. I updated from req.setEndpoint(‘callout:AWSSignature’); to req.setEndpoint(‘callout:AWSSignature’ +’/’+attach.Title.replaceAll(‘[^a-zA-Z0-9\\s+]’,’-‘).toLowerCase()+ ‘.’+attach.FileExtension.toLowerCase()); I hope this helps.
Thankyou!
This solution worked out for me, when I was facing Access denied issue, thanks.
Pingback: Difference between SOAP and REST API? - SalesforceCodex
I am getting ‘403’ Access denied Error. I am using the same code but still getting this error.
Hello Muthu,
Please check access to user which you are using to explore API.
Thank You,
Dhanik