- Mais recentes
- Mais votos
- Mais comentários
Might need more information to gauge the SEO impact.
With regards to the question, it would be easier to create a distribution per install as we could simply rely on Origin Path parameter [1] to append the directory name into URI. For instance, example.com/a.img would be example.com/path/a.img sending back to the origin.
On the other hand, we could also use CloudFront Functions or Lambda@Edge to dynamically adjust the request URI based on the needs. For example, the following CloudFront Functions would modify the URI according to the host name (alternate name):
function handler(event) {
var request = event.request;
var headers = request.headers;
var host = request.headers.host.value;
var uri = request.uri;
if (host === 'example.com') {
// If the host is example.com, prepend /example to the URI
request.uri = '/example' + uri;
}
return request;
}
Lastly, I would also recommend reading this article [2] for SEO optimization with Amazon CloudFront.
[2] https://aws.amazon.com/blogs/networking-and-content-delivery/optimize-seo-with-amazon-cloudfront/
Conteúdo relevante
- AWS OFICIALAtualizada há 4 meses
- AWS OFICIALAtualizada há 6 meses
