S3 RO credentials with Amazon Web Services Billing Connector is giving a "Failed to authenticate"?
We are attempting to use the pre-built Amazon Web Services Billing Connector to connect to the S3 bucket containing our cost and usage reports.
The access key/secret key credentials have read-only and list permissions to the bucket:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ListObjectsInBucket",
"Effect": "Allow",
"Action": [
"s3:ListBucket"
],
"Resource": [
"arn:aws:s3:::<bucket>"
]
},
{
"Sid": "GetObject",
"Effect": "Allow",
"Action": "s3:GetObject",
"Resource": [
"arn:aws:s3:::<bucket>/*"
]
}
]
}
The pre-built Amazon S3 connector successfully imports the data from the bucket using the same credentials. The pre-build Amazon Web Services Billing Connector fails with "Failed to authenticate. Verify the credentials and try again. Domo is ready, but the credentials you entered are invalid. Verify your account credentials and try again."
What additional permissions or what other settings are needed by this connector?
Comments
-
you need this too:
```
{
"Action": [
"s3:ListAllMyBuckets"
],
"Resource": "*",
"Effect": "Allow"
}```
0
Categories
- All Categories
- 1.2K Product Ideas
- 1.2K Ideas Exchange
- 1.3K Connect
- 1K Connectors
- 267 Workbench
- Cloud Amplifier
- 3 Federated
- 2.5K Transform
- 78 SQL DataFlows
- 524 Datasets
- 1.9K Magic ETL
- 2.9K Visualize
- 2.2K Charting
- 433 Beast Mode
- 22 Variables
- 507 Automate
- 113 Apps
- 386 APIs & Domo Developer
- 8 Workflows
- 25 Predict
- 9 Jupyter Workspaces
- 16 R & Python Tiles
- 331 Distribute
- 76 Domo Everywhere
- 255 Scheduled Reports
- 65 Manage
- 65 Governance & Security
- 1 Product Release Questions
- Community Forums
- 39 Getting Started
- 25 Community Member Introductions
- 67 Community Announcements
- 4.8K Archive