eb deploy throwing - ERROR: NotAuthorizedError - Operation Denied. Access Denied

[AnshulRaghav]

Getting error while eb deploy : ERROR: NotAuthorizedError - Operation Denied. Access Denied

Stack: Django application hosted on AWS using Elasticbeanstalk.

Everything was working fine the last time I deployed using eb deploy for my QA environment. Now suddenly getting this error that I'm not authorized to perform this action. Checked the credentials and key-pair as well. Nothing in the settings has been updated after the last deployment. The only thing that is different from the previous deployment is packages since requiremnents.txt has been updated. eb ssh is working fine as well.

Gettings these exceptions when tried eb deploy --debug

raise NotFoundError('Object not found.')
ebcli.objects.exceptions.NotFoundError: Object not found.

raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (AccessDenied) when calling the ListMultipartUploads operation: Access Denied

raise NotAuthorizedError('Operation Denied. ' + message)
ebcli.objects.exceptions.NotAuthorizedError: Operation Denied. Access Denied

[tim-finnigan]

Hi @AnshulRaghav for the EB CLI I recommend opening an issue in their repository, posting in re:Post, or opening a support case. This repository is for the Python SDK boto3.

This documentation on configuring the EB CLI may help: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-configuration.html.

Also this Elastic Beanstalk Developer Guide page on managing user policies may be worth looking into further as well: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/AWSHowTo.iam.managed-policies.html.

Hope that helps, please let us know if you had any follow up questions.

[AnshulRaghav]

Thank you for the reply @tim-finnigan . I managed to resolve this by adding S3FullAccess policy.

[Dilipkarnavat]

for what S3FullAccess policy

[michaelkeenan]

This page scores well for google queries about this problem, so for future googlers: check out the answer at this StackOverflow question, which explains the problem in more detail. (Though, the solution is exactly as AnshulRaghav said: add the S3FullAccess policy to the deployment user. That's still the correct solution even if deployment used to work and you've changed no configuration related to authorization so you're thinking that can't possibly be it. See StackOverflow for details.)