From fd871c1fa3135910e6e8b4abce812ff8c30e24bd Mon Sep 17 00:00:00 2001 From: Julia Branke Date: Wed, 19 Aug 2026 15:09:50 +0100 Subject: [PATCH] Add link to Fastly deployments section of riff-raff doc --- cdn.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/cdn.md b/cdn.md index 7eb7125..0d48acf 100644 --- a/cdn.md +++ b/cdn.md @@ -39,3 +39,7 @@ We suggest using the London-LCY point of presence as your shield. Fastly has extensive logging capabilities. This can be useful for debugging and data analysis. We advise [streaming logs to Amazon S3](https://docs.fastly.com/en/guides/log-streaming-amazon-s3). When logging to S3 you should [create an IAM role for Fastly](https://docs.fastly.com/en/guides/creating-an-aws-iam-role-for-fastly-logging) using Fastly's AWS account as the principal rather than creating static credentials. Reader facing services will generate a high volume of logs so you should only enable logging where it is needed. You may consider [logging a sample of requests](https://docs.fastly.com/en/guides/useful-conditions-for-logging#logging-samples). + +### Deploy with Riff-Raff + +Information on deployment and how to generate a Fastly API Token for each Riff-Raff stage can be found in the [Fastly deployments section of our Riff-Raff documentation](https://github.com/guardian/deploy-tools-platform/blob/main/cloudformation/riffraff/riff-raff-roles.md#fastly-deployments). \ No newline at end of file