Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Amazon S3 Bucket - Put Object not authenticating #3733

Closed
lakomiak opened this issue Dec 11, 2024 · 5 comments
Closed

[BUG] Amazon S3 Bucket - Put Object not authenticating #3733

lakomiak opened this issue Dec 11, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@lakomiak
Copy link

Type of Connector

Independent Publisher Connector

Name of Connector

Amazon S3 Bucket - Put Object

Describe the bug

I am trying to connect to an AWS S3 bucket in my VPC and have verified the credentials to be correct but the connector fails with a forbidden error as follows. I know as part of this connection this connector has to create a signature with the credentials encrypted in order to gain Authentication. I don't know what is actually getting passed to AWS in the end to know if there is an issue with the signature becuase the credentials are verified as working.

InvalidAccessKeyIdThe AWS Access Key Id you provided does not exist in our records.

Is this a security bug?

Yes, this is a security bug

What is the severity of this bug?

Severity 1 - Connector is broken or there's a very serious issue

To Reproduce

Define connection in the put object action and attempt to connect to AWS S3 bucket defined

Expected behavior

Connection established to S3 and file passed in the connector pushed to the S3 bucket defined.

Environment summary

PowerAutomate Cloud flow

Additional context

No other information is available but the error message.

@lakomiak lakomiak added the bug Something isn't working label Dec 11, 2024
@megel
Copy link
Contributor

megel commented Mar 1, 2025

Hi @lakomiak,

you have described that your AWS S3 bucket is in your VPC. Is it possible, that you have blocked the public endpoints of S3 API?

Please try the connector with a standard S3 bucket that is public available to see, if the authentication works as expected.

@vmanoharas
Copy link
Contributor

Hi @lakomiak

Please see the solution provided by @megel and close this bug, if your issue resolved.

@megel
Copy link
Contributor

megel commented Apr 1, 2025

@lakomiak any updates?

@lakomiak
Copy link
Author

lakomiak commented Apr 2, 2025 via email

@vmanoharas
Copy link
Contributor

Thank you @lakomiak for the confirmation.

Thank you @megel for your help, I am closing this Bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants