Teamsite integration with Amazon cloudfront

Hi all,
here is a use case we are trying to implement. We want to get rid of Akamai and use Amazon cloud front caching service.But for that what is needed is all the relative links needs to be changed to absolute links with http://contentserver.url.com preceding, where contentserver is the Amazon
cloudfront server.The issue here is those absolute links will not work in our staging environment since the new/updated contents will not be available on Amazon cloudfront server till we deploy to Amazon cloudfront which we want to do only when the content is being pushed to prod.

Has anyone done this kind of implementation?

any comments/feedback is welcome

thx in advance

Find more posts tagged with

Comments

Rick Poulin

I don't know that this is a TeamSite problem as much as an architecture problem.

My suggestion would be that your workflow and/or deployment process have a perl/java script that "fixes" all the links in your HTML as required, just before deploying the files out. That script would obviously use values specific to the environment it's presently deploying to.

Adam Stoller

If this is for DCTs/DCRs - you could create hidden fields that get updated with the desired path whenever the visible fields change - and then make sure that you either generate the HTML with the values in the hidden fields or DD the hidden fields or something like that. If you're doing generated HTML you may need to set up some iwproxy rules to dynamically "revert" those paths to be TeamSite-local for Preview purposes.