There is no such permission as 's3:ListBuckets' - there is "s3:ListBucket" - and "s3:ListAllMyBuckets"Post edit -
S3cmd throwing this error on config -
Thought that the s3:ListBuckets permission from the json should cover it?
{
"Action": "s3:*",
"Effect": "Allow",
"Resource": [
"arn:aws:s3:::mybucket",
"arn:aws:s3:::mybucket/*"
]
},
{
"Effect": "Allow",
"Action": [
"s3:ListAllMyBuckets",
"s3:GetAccountPublicAccessBlock"
],
"Resource": "*"
}
s3:*
s3:Get*
s3:PutObject*
s3:List*
Sorry, I mean 's3:ListBucket'.There is no such permission as 's3:ListBuckets' - there is "s3:ListBucket" - and "s3:ListAllMyBuckets"
the simulator is looking at '*' in "simulation resource" - ie any and every bucket. You (rightly) have probably restricted actions to your actual bucket. the simulator tool is a waste of time IMHO.Sorry, I mean 's3:ListBucket'.
Just don't know why the permission is denied.
Thanks, but I use the stimulator because I was getting error in the s3cmd config.the simulator is looking at '*' in "simulation resource" - ie any and every bucket. You (rightly) have probably restricted actions to your actual bucket. the simulator tool is a waste of time IMHO.
I agree, even amazon advised users to remove ListAllMyBuckets and replace it with ListBucket.This is why I dont like s3cmd - you dont actually need s3:ListAllMyBuckets for XF to work. Anyway either your perms are wrong or your using the wrong set of creds? Incidentally if you are running this on an ec2 instance, you shouldn't even be using an IAM user
This - https://xenforo.com/community/threa...ith-their-original-name-and-extension.201643/lol - they definitely do not do that. But I agree that AWS is not for everyone and you really shouldn't use it unless you know what you are doingCode:This is not even mentioning their renaming of the files in the Bucket to .data.
No - works in the same way as attachments as far as naming goes.Image caching is also lost in the process, right?
eks? I think you mean efs, not kubernetes.s3 is slower than the local filesystem, for sure, and even eks
You are likely in the first year hence the free ec2 benefits.eks? I think you mean efs, not kubernetes.
Agree that efs is relatively expensive compared to s3 - to a point. S3 cost and performance on very small files is abysmal. And despite running one of the bigger and most complex XF sites going around (70 mill+ posts, 100,000+ users) our EFS cost last month was 7 cents! But yeah, running on AWS can be expensive if you dont know what you are doing - we scale up and down and mint new amis regularly - it suits our needs but the vast majority of XF sites dont need this.
S3 don't just charge for gb storage. The charges includes storage, bandwidth copy & cut etc.023 vs .3 per gb stored
Have been using EFS since it was in "preview" years ago - the days of "free ec2 benefits" are long gone.You are likely in the first year hence the free ec2 benefits.
getting a sata based hdd from cheap dedicated server for a forum and may even be cheaper.
'Better' in this context is relative.Have been using EFS since it was in "preview" years ago - the days of "free ec2 benefits" are long gone.
good god no - I dont care how cheap a dedicated server is, the overhead on maintenance, backup, reliability and scalability means it is a false economy never mind that you are paying for unused capacity. AWS S3 or DO spaces or Azure Blobs or GCP Cloud Storage or CloudFlare R2 (when available) are much better options
Typo, so used to using eks at work :X yes, i meant efs in all instances and updated my post.eks? I think you mean efs, not kubernetes.
i'm curious how you manage a 7 cent charge. Even a small site would rip through that.Agree that efs is relatively expensive compared to s3 - to a point. S3 cost and performance on very small files is abysmal. And despite running one of the bigger and most complex XF sites going around (70 mill+ posts, 100,000+ users) our EFS cost last month was 7 cents! But yeah, running on AWS can be expensive if you dont know what you are doing - we scale up and down and mint new amis regularly - it suits our needs but the vast majority of XF sites dont need this.
Correct, i was only comparing storage. in/egress and touch cost money too.S3 don't just charge for gb storage. The charges includes storage, bandwidth copy & cut etc.
This also adds a lot of overhead and DR planning. S3 is already pretty resilient - enough for my needs - without going into crazy DR plans. If us-east gets nuked, i don't care about my forum anymore.On a very bright day DO Spaces should be much cheaper than s3, also, getting a sata based hdd from cheap dedicated server for a forum and may even be cheaper.
Just use different storage host from the main performance based host.
good god no - I dont care how cheap a dedicated server is, the overhead on maintenance, backup, reliability and scalability means it is a false economy never mind that you are paying for unused capacity. AWS S3 or DO spaces or Azure Blobs or GCP Cloud Storage or CloudFlare R2 (when available) are much better options
my s3 costs are around $5 a month for forum related activities (i store other stuff there too). I am behind cloudflare too for caching.'Better' in this context is relative.
S3 pricing model should be tad expensive for a relative busy forum but a good idea for backup because of the reliability.
The EFS is used really only for code cache and templates. We have 'internal-data' set to use S3, despite this XF actually does the templates and code cache locally, so we mount an EFS volume for that -not that much data and no retrieval costs. We run multiple servers so that data needs to be stored in a file system that is both shared and reasonably fast (compared to S3) - We can hit 200 or hits a second so we need to be reasonably performant.i'm curious how you manage a 7 cent charge. Even a small site would rip through that.
Policy has invalid action: s3:ReplicateObject
error:We use essential cookies to make this site work, and optional cookies to enhance your experience.