-
Bug
-
Resolution: Not A Defect
-
Blocker
-
EC2 plugin version: v2.0.5
Jenkins version: 2.375.2
JDK version: 11.0.16
Operating System: Amazon Linux
Replication Steps:
- I add new "Amazon EC2" cloud from Manage Jenkins > Configure Clouds.
- I fill in name, region, private key.
- I click "Test Connection" button. Result is "Success".
- I then add one AMI and fill in the required fields.
- Then I click "Check AMI" button. It will give the correct AMI name.
- But when I click "Apply" or "Save", the page renders "403 Forbidden".
I could not replicate this issue on Jenkins 2.263.4. It saves the AMI just fine.
I checked for hints in the following places, but nothing was logged regarding this issue:
- Logs from Manage Jenkins > System Logs
- Logs from journalctl
- Audit logs from the Audit Trail plugin (v3.11)
- Reports from the Monitoring plugin (v1.91.0)
I assume I have successfully established connection between the EC2 plugin and my Amazon account. So how come can I not save an AMI?