- Newest
- Most votes
- Most comments
It sounds like the issue may be related to the caching behavior of the edge server. When a user clicks on the shortened link in the email, the request is routed through the edge server, which may cache the content for a certain amount of time before checking for updates on the origin server.
One potential solution is to configure the caching behavior of the edge server to reduce the cache time, or to disable caching altogether. This may cause a higher load on the origin server, but would ensure that updates are reflected in the content served by the edge server.
Another solution may be to use a different service for link tracking that does not rely on the edge server URL. For example, some URL shortening services provide the option to use a custom domain for the shortened links, which would allow you to use your Cloudfront URL instead of the edge server URL. Alternatively, you could set up your own URL shortening service using a tool like YOURLS or Bitly, which would give you full control over the URL generation process.
Finally, you may want to consider using a different email service provider that does not modify the URLs in your emails. While this may not be feasible depending on your specific requirements and workflows, it may be worth exploring as a potential solution.
Relevant content
- asked a year ago
- Accepted Answerasked 2 years ago
- asked 5 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 8 days ago
- AWS OFFICIALUpdated a year ago