-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
DNS_AWS does not support role credentials from IMDSv2 #4960
Comments
Please upgrade to the latest code and try again first. Maybe it's already fixed. |
No it's not fixed I did it on the latest version, debug log is not needed I think this missing functionality is obvious. I checked your code where it's missing:
_use_instance_role() {
_url="http://169.254.169.254/latest/meta-data/iam/security-credentials/"
_debug "_url" "$_url"
if ! _get "$_url" true 1 | _head_n 1 | grep -Fq 200; then
_debug "Unable to fetch IAM role from instance metadata"
return 1
fi
_aws_role=$(_get "$_url" "" 1)
_debug "_aws_role" "$_aws_role"
_use_metadata "$_url$_aws_role"
} |
Just to make sure I understand...you do NOT wish to set IMDSv2 to "Optional" in the instance settings, correct? Otherwise, please see below. Set IMDSv2 to "Optional". I did, and it worked for me. It failed with "You haven't specified the aws route53 api key id and and api key secret yet." when IMDSv2 set to "Required". |
I use required because AWS strongly recommend it , btw it's barking in security hub when you have enabled v1. |
Hi, I upgraded acme.sh and try rerun --renew command but no luck. I'm getting this error: [Wed Apr 10 11:27:27 UTC 2024] Response error: |
This seems to be fixed in acme.sh 3.1.0. |
DNS_AWS do not support role credentials from IMDSv2
Steps to reproduce
enable IMDSv2 on ec2
Debug log
The text was updated successfully, but these errors were encountered: