Citizen browsers must reach the city services portal only over HTTPS with a valid certificate on the custom domain. What should the team configure?
Select an answer to reveal the explanation.
Short Explanation
Citizens need a real lock in the browser—valid cert on the custom domain at CloudFront or API Gateway, HTTPS enforced. Plain HTTP and “trust our self-signed IP” are not how a municipal portal greets the public.
Full Explanation
Public citizen portals should terminate TLS with a valid certificate (commonly ACM) on CloudFront or an API Gateway custom domain and redirect or require HTTPS. Serving HTTP, omitting edge certificates, or relying on ad-hoc self-signed certificates for production citizen traffic fails confidentiality and trust requirements.