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

django ses issue (with celery): BotoServerError: BotoServerError: 403 Forbidden #85

Open
saurabhprakash opened this issue Feb 12, 2016 · 4 comments

Comments

@saurabhprakash
Copy link

I am using django-ses:

Please find settings for it

EMAIL_BACKEND = 'django_ses.SESBackend'
EMAIL_HOST = 'email.us-east-1.amazonaws.com'
EMAIL_PORT = 465
EMAIL_HOST_USER = '----------------'
EMAIL_HOST_PASSWORD = '-------------------'

AWS_ACCESS_KEY_ID = '-------------------'
AWS_SECRET_ACCESS_KEY = '------------------------------'
AWS_SES_REGION_ENDPOINT = 'email.us-east-1.amazonaws.com'

Find the error stack:

BotoServerError: BotoServerError: 403 Forbidden
<ErrorResponse xmlns="http://ses.amazonaws.com/doc/2010-12-01/">
  <Error>
    <Type>Sender</Type>
    <Code>AccessDenied</Code>
    <Message>User: arn:aws:iam::00000000000:user/ses-smtp-user.20160209-000000 is not authorized to perform: ses:GetSendQuota</Message>
  </Error>
  <RequestId>0000000-0000-0000-0000-0000000000</RequestId>
</ErrorResponse>
@PritishC
Copy link

PritishC commented Mar 2, 2016

Perhaps your IAM user doesn't have sufficient permissions to perform that action? There should be a permission group for SESAdministratorAccess (or just Read and Write or something similar, if you don't want to give admin access) which you will need to apply on your IAM user.

@theanilbajar
Copy link

theanilbajar commented Apr 11, 2017

If you are sending mail from verified email ID to another verified email ID, then please try this User Policy that worked for me with Django.
Please update your User Policy with this:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "ses:SendEmail",
                "ses:SendRawEmail",
                "ses:GetSendQuota"
            ],
            "Resource": "*"
        }
    ]
}

@ghost
Copy link

ghost commented Dec 12, 2022

If you are sending mail from verified email ID to another verified email ID, then please try this User Policy that worked for me with Django. Please update your User Policy with this:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "ses:SendEmail",
                "ses:SendRawEmail",
                "ses:GetSendQuota"
            ],
            "Resource": "*"
        }
    ]
}

It should be added to README.

@pcraciunoiu
Copy link
Contributor

If you'd like to PR this change to the README, I can review it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants