Picking a WAF configuration for a voting application


We have an Amplify hosted application that effectively has a voting component - where the URL has an identifier as part of it to cast a vote - so, for "Yes" the URL goes to https://domain.com/vote/?answer=YES and no goes to https://domain.com/vote/?answer=NO There are rules around voting, so we save a client-side cookie as to whether you have already voted. So, the URL hits our server, it responds with a redirect and a cookie to log the fact you voted on the client machine. So, if you go to vote again, it sees the cookie and either doesn't allow your vote or changes the prior vote. We clearly don't want bots voting, so it looks like putting WAF in front of the URl would help. There appear to be an infinite number of WAF configurations. Does anyone have a configuration suggestion that would allow us to protect the voting URL from fraudulent use?

gefragt vor 3 Monaten122 Aufrufe
1 Antwort


Amplify does not directly support AWS WAF, so you need to link AWS WAF to CloudFront.

For AWS managed rules, I think the "Bot Control" rule group below will help you block bots.

Also, in this case, if you think that access from people other than the client is unnecessary, I thought that the following "IP reputation rule groups" might be useful.

profile picture
beantwortet vor 3 Monaten

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen