用于S3存储桶的ListObjectsV2操作AccessDended

Question

在GitlabCi期间，我得到了：“致命错误：调用ListObjectsV2操作时发生错误（AccessDenied）：访问被拒绝”

我的桶政策：

{
"Version": "2008-10-17",
"Statement": [
    {
        "Sid": "AllowPublicRead",
        "Effect": "Allow",
        "Principal": {
            "AWS": "*"
        },
        "Action": "s3:*",
        "Resource": "arn:aws:s3:::BUCKET-NAME/*"
    }
]

}

在gitlabCI设置集中：

• AWS\u ACCESS\u KEY\u ID:YOUR-AWS-ACCESS-KEY-ID
• AWS\u SECRET\u ACCESS\u密钥：YOUR-AWS-SECRET-ACCESS-KEY
• S3\u BUCKET\u NAME:YOUR-S3-BUCKET-NAME
• DISTRIBUTION\u ID:CLOUDFRONT-DISTRIBUTION-ID

我的gitlab-ci.yml

image: docker:latest

stages:
  - build
  - deploy

build:
  stage: build
  image: node:8.11.3
script:
  - export API_URL="d144iew37xsh40.cloudfront.net"
  - npm install
  - npm run build
  - echo "BUILD SUCCESSFULLY"
artifacts:
   paths:
    - public/
expire_in: 20 mins
environment:
name: production
only:
   - master
deploy:
  stage: deploy
  image: python:3.5
dependencies:
   - build
script:
  - export AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID
  - export AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY
  - export S3_BUCKET_NAME=$S3_BUCKET_NAME
  - export DISTRIBUTION_ID=$DISTRIBUTION_ID
  - pip install awscli --upgrade --user
  - export PATH=~/.local/bin:$PATH
  - aws s3 sync --acl public-read --delete public $S3_BUCKET_NAME
  - aws cloudfront create-invalidation --distribution-id 
$DISTRIBUTION_ID --paths '/*'
  - echo "DEPLOYED SUCCESSFULLY"

environment:
   name: production
only:
  - master

Answer 1

尝试将bucket策略更新为：

{
"Version": "version_id",
"Statement": [
    {
        "Sid": "AllowPublicRead",
        "Effect": "Allow",
        "Action": [
            "s3:*"
        ],
        "Resource": [
            "arn:aws:s3:::BUCKET-NAME",
            "arn:aws:s3:::BUCKET-NAME/*"
        ]
    }
] }

我希望你明白这是非常不安全的。

Answer 2

我最近有这个问题。无论我做了什么，无论我提供了什么权限，在运行aws s3 ls时，我总是得到“调用ListObjectsV2操作时出错（AccessDenied）：拒绝访问”

我忘记了在我的环境中配置了多个aws配置文件。aws命令使用的是默认配置文件，该配置文件具有不同的访问密钥集。我必须为命令指定--profile标志：

aws s3 ls

成功了。这是一个利基情况，但也许它会帮助某人。

Answer 3

我不确定这个被接受的答案是否真的可以接受，因为它只允许在bucket上进行所有操作。此外，Sid具有误导性…；-）

这篇AWS文章提到了AWS s3 sync所需的权限。

相应的策略是这样的：

{
"Version": "version_id",
"Statement": [
    {
        "Sid": "AllowBucketSync",
        "Effect": "Allow",
        "Action": [
            "s3:GetObject", 
            "s3:PutObject", 
            "s3:ListBucket"
        ],
        "Resource": [
            "arn:aws:s3:::BUCKET-NAME",
            "arn:aws:s3:::BUCKET-NAME/*"
        ]
    }
] }