-
Notifications
You must be signed in to change notification settings - Fork 24
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
Creating new certificates does not respect aws_region config value #248
Comments
That is an unexpected quirk of the way AWS is designed.
I think that most people that use Discharge are not logging into the AWS console and looking for their certificate and wondering why it’s not in the region they expected, so nobody has ever noticed this before. As long as it all just works they don’t care. If I’d documented that quirk in the Distribute section of the README would you have noticed it? Do you think it’s worth adding a note there? |
@brandonweiss I just stumbled upon this issue by looking at the issues list and it was just what I needed so I think it's worth adding on the README. NEVERMIND THIS Maybe even add it on the console log message:
|
Ah, yeah, I hadn’t thought of that. If someone has verification troubles they might try to sign in to see what’s going on. OK, so I’ll definitely add it to the README. Adding it to the log message could be good, although it’d have to be really clear or it might confuse people even more. Maybe…
It’s still not as clear “why” as I‘d like, but it explains what is happening and implies that the reason why has something to do with CloudFront. |
New certificates appear to be created in the
us-east-1
region, even in the theaws_region
is set to something else.The text was updated successfully, but these errors were encountered: