An Atlantis Server has been setup on EC2 instance and the corresponding URL has been mapped to a DNS. The same URL has been put into the Webhook configuration on Bitbucket and some triggers have been configured. But whenever the events (say: pullrequest) triggers the Atlantis Server running on EC2 instance, it gives -: HTTP 403 "Access control configuration prevents your request from being allowed at this time. Please contact your service provider if you feel this is incorrect." :- error.
The end requirement for the POC is to Integrate Atlantis with Bitbucket to initiate Terraform plan on pull request.
Hello @Mayank Gupta ,
Welcome to Atlassian Community!
The HTTP 403 error you are receiving means there was some issue with the authentication between bitbucket and your destination server. You have either not provided the credentials in your webhook URL or the credentials were not correct.
Currently in Bitbucket Cloud webooks only support HTTPS basic authentication, and you need to specify the credentials as part of the webhook URL, as the below example :
https://<username of the destination>:<password of the destination>@<URL of the destination>
I'd like to point out that e-mail addresses are not currently supported to be used as the username in the webhook's URL, and this is being tracked in the bug ticket BCLOUD-14773 .
Additionally, I'd also like to share that we already have a feature request to include the possibility of adding a secret as part of the webhook configuration to be an alternative method of authentication. You can take a look at that feature request in the following link :
You can feel free to add your vote there, since this helps both developers and product managers to understand the interest. Also, make sure you add yourself as a watcher in case you want to receive first-hand updates from that ticket. Please note that all features are implemented with this policy in mind.
Hope that helps! Let me know in case you have any questions.
Thank you, @Mayank Gupta .
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events