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

403 Forbidden - Request forbidden by administrative rules.Request forbidden by administrative rules. #78

Closed
TELUS-Alexander opened this issue Nov 28, 2014 · 6 comments

Comments

@TELUS-Alexander
Copy link

Hello,

When I try to sync lift-search I get the following message:

"403 Forbidden
Request forbidden by administrative rules."

What is it attributed by?

Thank you for your help.

@kevinlangleyjr
Copy link
Member

It seems this error can be attributed to an incorrect access policy that does not allow you to use the doc endpoint. Lift should configure this for you, did you change any of the access policy settings there within the CloudSearch backend? We use ifconfig.me to detect the server's IP address and set the access policy as such. There was recently a small outage for them and if you had configured Lift during that outage it is definitely a possibility that caused the issue.

Can you check the access policy that was set and confirm that your IP address is there? If not, you can always adjust it within the backend of CloudSearch and then Lift should sync without an issue.

https://forums.aws.amazon.com/thread.jspa?messageID=364184

@TELUS-Alexander
Copy link
Author

Hi Kevin,

Thank you for answering this inquiry.

I am not sure where to locate the access policy information or what actions I should take as a result of your reply.

I was able to locate the "Access Credentials" info and may see that the key was added in "
2013-07-11 16:11 EDT" and is Active, no info of IP or server.

Are you able to elaborate on your reply please so that I know which action to take?

Awaiting your reply and appreciate your help.

@kevinlangleyjr
Copy link
Member

You can read about the CloudSearch specific Access Policies here http://awsdocs.s3.amazonaws.com/cloudsearch/2011-02-01/cloudsearch-dg-2011-02-01.pdf on page 131.

screen shot 2014-12-08 at 2 02 23 pm

You can find the Access Policies here within the backend of CloudSearch and should set it to have one search and one document end point for each web server Lift is running on.

screen shot 2014-12-08 at 2 00 54 pm

If you'd rather a quicker way to fix this issue. You can reset Lift and as I said before it should create the access policy for you upon creating the new domain.

@TELUS-Alexander
Copy link
Author

Hi Kevin,

This corrected the issue, thank you very much for your support.

@kevinlangleyjr
Copy link
Member

Glad to be able to help!

@TELUS-Alexander
Copy link
Author

By the way, I wish it was much easier to add meta_fields to the index. Perhaps enable it from the admin as opposed to hard coding them.

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

2 participants