[akash1810]

What does this change?

This change routes all traffic for tag-page-rendering in PROD to ECS. Previous attempts at this (#16774) were reverted (#16776) due to an issue with assets on the CDN (see also #16808). The root cause of that issue has now been addressed (#16821) so let's try again!

This change also increases the minimum tasks to 12. At 3 tasks and 100% traffic, ECS latency averaged 300ms. This is quite high compared to EC2 which averages around 40ms. This change over-provisions to 12 tasks in an attempt to mitigate high latency; we'll tune this once we have data for how its performing.

How has this change been tested?

Not possible, as this changes PROD infrastructure.

After deploying, things to check are:

• Metrics on the Availability Dashboard
• Manual testing of the site, e.g is JS loading on tag-pages like https://www.theguardian.com/tone/minutebyminute

---

Co-authored by: @connoromalleyatwork.

[github-actions]

Deploy build 32222 of dotcom:rendering-all to CODE

All deployment options

• Deploy build 32222 of dotcom:rendering-all to CODE
• Deploy parts of build 32222 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[github-actions]

🚀 Image pushed to AWS ECR

Image digest: sha256:345db3e723a3fab88f92e76545e54b76fb92cdada65be814b8239255614ea3f5

🐛 Run the image locally

The following can be used to run the image locally:

# Refer to image using the immutable digest. Find alternatives below.
IMAGE_IDENTIFIER="@sha256:345db3e723a3fab88f92e76545e54b76fb92cdada65be814b8239255614ea3f5"

# Refer to image using branch tag
# IMAGE_IDENTIFIER=":branch-tag-page-rendering-ecs-100-try-2"

# Refer to image using build tag
# IMAGE_IDENTIFIER=":build-32222"

# Set environment variables for the AWS CLI
AWS_PROFILE="<A_PROFILE_FROM_JANUS>"
AWS_DEFAULT_REGION="eu-west-1"

IMAGE_ACCOUNT_ID=$(aws ssm get-parameter --name /organisation/accounts/artifacts --query "Parameter.Value" --output text)
REGISTRY="${IMAGE_ACCOUNT_ID}.dkr.ecr.${AWS_DEFAULT_REGION}.amazonaws.com"
IMAGE="${REGISTRY}/guardian/dotcom-rendering/dotcom-rendering${IMAGE_IDENTIFIER}"

# Login to AWS ECR https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry_auth.html
aws ecr get-login-password | docker login --username AWS --password-stdin $REGISTRY

# Pull the image
docker pull $IMAGE

# Run the image. You'll likely need to set additional flags. See https://docs.docker.com/reference/cli/docker/container/run.
docker run $IMAGE

---

From guardian/actions-ecr.

[github-actions]

Deploy build 3641 of dotcom:ab-testing to CODE

All deployment options

• Deploy build 3641 of dotcom:ab-testing to CODE
• Deploy parts of build 3641 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[gu-prout]

Seen on PROD (merged by @akash1810 6 minutes and 43 seconds ago) Please check your changes!

[akash1810]

Initial metrics show latency has creeped up a touch, from 40ms to 70ms:

This is still within the thresholds of expectations of:

• EC2 horizontally scaling at 400ms
• Frontend's 2s circuit breaker