Skip to content

attempt push to ecs with new policy #9

attempt push to ecs with new policy

attempt push to ecs with new policy #9

Triggered via push May 1, 2026 16:14
Status Failure
Total duration 1m 14s
Artifacts

develop.yml

on: push
build-push-deploy
1m 4s
build-push-deploy
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
build-push-deploy
User: arn:aws:sts::282236276875:assumed-role/GithubActions-analytics-dashboard-ui/GitHubActions is not authorized to perform: ecs:RegisterTaskDefinition on resource: arn:aws:ecs:***:282236276875:task-definition/Analytics-Dashboard-New-ECSFrontEndTaskDefinition-wCH7pchQPCkB:* because no identity-based policy allows the ecs:RegisterTaskDefinition action
build-push-deploy
Failed to register task definition in ECS: User: arn:aws:sts::282236276875:assumed-role/GithubActions-analytics-dashboard-ui/GitHubActions is not authorized to perform: ecs:RegisterTaskDefinition on resource: arn:aws:ecs:***:282236276875:task-definition/Analytics-Dashboard-New-ECSFrontEndTaskDefinition-wCH7pchQPCkB:* because no identity-based policy allows the ecs:RegisterTaskDefinition action
build-push-deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, jwalton/gh-ecr-push@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/