Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

215
Views
AWS S3 presigned url generated successfully but then using it via curl or Postman returns InvalidAccessKeyId

I have this code in my express server that generates an S3 presigned url using NodeJS AWS SDK:

const { S3Client } = require("@aws-sdk/client-s3");
const { getSignedUrl } = require("@aws-sdk/s3-request-presigner");
    
app.get('/getS3PresignedUrl', async (req, res) => {


  const s3 = new S3Client({
      region: 'ap-southeast-2',
      credentials: {
        accessKeyId: accessKey.data.access_key,
        secretAccessKey: accessKey.data.secret_key
      }

    });
  const presignedS3Url = await getSignedUrl(s3, new PutObjectCommand({
      Bucket: 'xxx',
      Key: 'test.txt',
    }) 
  );
  res.send({
    status: true,
    message: 'success',
    data: {
      s3Url: presignedS3Url 
    }
  });
})

Once I get the URL, I use that and put it in either curl or Postman but both gets 403 InvalidAccessKeyId. For example:

  1. curl enter image description here
  2. Postman enter image description here

I don't understand why it fails with 403 when the S3 url is generated successfully? Note, I use that url right away and does not exceed the 900 seconds expire limit.

Any ideas what is the issue here?

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!