Monosnap Custom S3 Bucket - IAM Policy

monosnap-s3-iam-policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AllowGroupToSeeBucketListInTheConsole",
      "Action": [
        "s3:ListAllMyBuckets",
        "s3:GetBucketLocation"
      ],
      "Effect": "Allow",
      "Resource": [
        "arn:aws:s3:::*"
      ]
    },
    {
      "Sid": "AllowRootLevelListingOfTheBucket",
      "Action": [
        "s3:ListBucket"
      ],
      "Effect": "Allow",
      "Resource": [
        "arn:aws:s3:::my-monosnap-s3-bucket"
      ]
    },
    {
      "Sid": "Stmt1410750108000",
      "Effect": "Allow",
      "Action": [
        "s3:GetObjectAcl",
        "s3:GetObject",
        "s3:GetObjectVersionAcl",
        "s3:GetObjectVersion",
        "s3:ListBucket",
        "s3:PutObjectAcl",
        "s3:PutObject",
        "s3:PutObjectVersionAcl"
      ],
      "Resource": [
        "arn:aws:s3:::my-monosnap-s3-bucket/*"
      ]
    }
  ]
}

Replace all instances of my-monosnap-s3-bucket with your actual S3 bucket name.

Thanks for the gist! Weirdly not working for me though… :-(

Looks like it could be due to propagation delay: https://monosnap.com/en/page/faq#q11

Uploads usually fail due to insufficient permissions on IAM user you've created. To check if that's correct, please, use Full S3 access policy on the user. Monosnap needs at least permission to list all buckets and full access to the required bucket. Note: we have received messages about policy propagation delay on Amazon servers, it may take up to 24 hours.

👍 Thanks

I'm right understand that Full S3 access policy means full access to any bucket in S3?