Repository navigation
fix(aws-transform): link executor policies to the public AWS pages - #293
Open
TheSaiEaranti wants to merge 1 commit into
Open
TheSaiEaranti wants to merge 1 commit into
TheSaiEaranti wants to merge 1 commit into
Conversation
The EC2 and Batch remote execution references linked the Executor policy to code.amazon.com, which redirects to an Amazon corporate sign-in. Both policies are published AWS managed policies, so link their pages in the AWS Managed Policy Reference instead. Bumps aws-transform to 1.9.1.
TheSaiEaranti
requested review from
a team,
krokoko,
laithalsaadoon and
rshevchuk-git
October 28, 2026 21:54
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.
The remote EC2 and Batch execution references link the Executor policy to code.amazon.com, which is Amazon's internal code browser. Outside Amazon the link redirects to a corporate sign-in page, so neither a user nor the agent can open the policy. Both policies are published AWS managed policies, so this points the links at their pages in the AWS Managed Policy Reference.
Related
No existing issue. The links came in with the 1.4.0 sync in #242. Before that, the EC2 reference pointed at a public GitHub URL (#196).
Changes
continuous-modernization-ec2-execution.md: linkAWSTransformInfrastructureExecutorAccessEC2to https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSTransformInfrastructureExecutorAccessEC2.htmlcontinuous-modernization-batch-execution.md: linkAWSTransformInfrastructureExecutorAccessBatchto https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSTransformInfrastructureExecutorAccessBatch.htmlThe link text and the rest of each line are unchanged.
aws-lambda-durable-functionsanddsqlalready link managed policies to the same reference.I didn't point the EC2 link back at the bundled
references/AWSTransformInfrastructureExecutorAccessEC2.json, because it is older than the published policy (it has notag:GetResources, for example). Since this plugin is synced from an internal source, the same change probably needs to go there too, or the next sync will bring the old links back.Verification:
uv run tools/validate-urls.pyreports both as [401]. With this change those two entries are gone and nothing new is reported.arn:aws:iam::aws:policy/AWSTransformInfrastructureExecutorAccessEC2and...Batch).dprint check,markdownlint-cli2, thelint:manifestsajv checks,node tools/validate-cross-refs.cjs,uv run tools/validate-references.pyanduv run tools/validate-size.py: same output as main.uv run --with pytest pytest tools plugins: 132 passed.Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.