1 Answer
- Newest
- Most votes
- Most comments
0
The issue was related to an invalid bucket policy applied on beanstalk default bucket.
answered 7 years ago
Relevant content
- AWS OFFICIALUpdated 5 months ago
The issue was related to an invalid bucket policy applied on beanstalk default bucket.