Submitted By: mitch.saltykov
Topic: CI Error
Team: Tier 1 Support
The ves-oracle-export repository started failing on Wednesday, without any changes committed in months. Looks like an AWS authorization issue of some sort getting the credentials it uses?
User: arn:aws-us-gov:sts::008577686731:assumed-role/ves-gha-oidc-role/GitHubActions is not authorized to perform: ssm:GetParameter on resource: arn:aws-us-gov:ssm:us-gov-west-1:008577686731:parameter/vets-api/income-limits/ves_db_username because no identity-based policy allows the ssm:GetParameter action
Submitted By: mitch.saltykov Topic: CI Error Team: Tier 1 Support
The
ves-oracle-export
repository started failing on Wednesday, without any changes committed in months. Looks like an AWS authorization issue of some sort getting the credentials it uses?https://github.com/department-of-veterans-affairs/ves-oracle-export/actions/runs/12074856599
This repo has been using the same credentials that the vets-api Income Limits data sync script references (https://github.com/department-of-veterans-affairs/vets-api/blob/master/.github/scripts/income-limits-data-sync.rb) - could that be the problem? Do we need to add our own credentials for this repo?