-
-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lack of S3 Credentials when using Plan action, cannot replicate locally on the same EC2 instance. #234
Comments
Please set the ACTIONS_STEP_DEBUG secret to true and run the job again. When was the last time this worked and what version of the action were you using? How are you providing the aws credentials to your runner? |
I will rerun with debug true in about 8 hours. It last worked on Nov 30th, and we are using latest. We did see you pushed an update on the first but we also tried using the pinned 1.3.0 version. We normally have it marked as v1 to use your latest patch. We provide aws credentials via IAM roles and a config file located in .aws/config that demotes profiles to use |
Basically the same logging output. I've taken out the individual terraform directories that successfully initialized |
Problem description
When running the plan action, as of Dec 1st, w/ no changes to either our IAM role permissions or the workflow file, our Plan action has started failing w/
When trying to run the same actions locally we run into no errors, and instead are given the correct plan output.
We've tried to copy up config files into the .aws directory, as well as double checking all IAM roles to ensure access should completely fine, and still the error persists.
This is run on a self-hosted Amazon Linux 2 EC2 instance through Github Actions.
Terraform version
1.3.6
Backend
No response
Workflow YAML
Workflow log
The text was updated successfully, but these errors were encountered: