Repository navigation
Conversation
akash1810
reviewed
Oct 26, 2026
akash1810
left a comment
Member
There was a problem hiding this comment.
LGTM. Let's get final approval from @guardian/dotcom-platform though.
| @@ -254,8 +254,8 @@ export const InteractiveRenderingPropsPROD: RenderingCDKStackProps = { | |||
| }, | |||
| // Route 100% traffic to EC2. | |||
Member
There was a problem hiding this comment.
Suggested change
| // Route 100% traffic to EC2. | |
| // Route 99% traffic to EC2, 1% to ECS. |
arelra
approved these changes
Oct 26, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this change?
At present, all Interactives PROD traffic is routed to the EC2 service. This PR will send 1% of traffic to the new ECS service, leaving 99% on EC2.
Why?
We expect no difference between the two. If the metrics confirm that nothing changes, we will have increased confidence and roll forward to 10%. If we can detect any change, we will roll back to 100% EC2.
How has this change been tested?
Simple tests have been run which make requests to both services and compare the results, excluding the X-Gu-Target-Group response header and a few server timestamps. Responses have been found to be identical. As the comparison includes the commit hash, we have a high degree of confidence that the services' codebases are identical.
Screenshots