cloudposse / cloudposse/docs

Mitigating Let's Encrypt Rate Limiting Issues

Open
#174 1 comment 0 reactions 1 assignee Claimed by @osterman View on GitHub
documentation
Dominant language
MDX
Stars
99
Forks
34
PR merge metrics
No merged PRs in 30d

Description

## what
We're concerned about LetsEncrypt rate limiting issues. It's fair enough to switch our staging environment over to using Lets Encrypt's staging env, but I'm concerned about this in production.

## why

It basically means we could be blocked from changes to our infrastructure if let's encrypt rate limits us again. So we need a solution to that in some respect. Naively we could switch to using a wildcard cert. *.example.net and just make sure all of the servers use the dns name of server-123-123.example.net

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.