missing information in add certificate in ACM
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws
- Domain
- cloud, documentation
Research direction
Start with the “Set up CNAMEs” section in how-to-add-a-certificate-using-ACM.html and review the linked Stack Overflow answer about GoDaddy and Google Domains. Update the explanation so readers understand the ACM validation and KAUI CNAMEs, provider-specific name values, and the remaining Kill Bill API certificate question; done when those setup steps and scope are unambiguous.
Written by the indexing model from the issue text.
Description
At the time of writing this issue, setup CNAME section in this docs need more explanation.
[1] .... The two strings labeled Name and Value should be copied to the two required entries for your CNAME. Copy these long strings carefully. Do not include any trailing periods. ....
Not all DNS manager in domain registrar should copy all those strings in ACM's CNAME name column. GoDaddy and Google Domains only need a prefix. See this so post.
[2] Your second CNAME is simpler. The Name entry will be kaui. The Value entry is the DNS name of your Load Balancer.
We need to add one or two paragraphs about the purpose of this. Maybe explain explicitly that we need 2 CNAME in our DNS Manager:
- For ACM validation
- For KAUI
- For Kill Bill API it self, if needed (For discussion: I'm little bit confused as well about where we should put this information. Java Client for example, need extra work -- set certificate etc. if certificate is not valid or it is just self-signed certificate).
- Dominant language
- CSS
- Stars
- 43
- Forks
- 86
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from killbill/killbill-docs
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
killbill/killbill-docs#557 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
killbill/killbill-docs#622 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
killbill/killbill-docs#585 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
killbill/killbill-docs#562 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 55/100
killbill/killbill-docs#548 ·
Maintainers usually reply within 1 day
All issues in killbill/killbill-docs
Similar issues
-
enhancement needs-triage service/kinesisanalyticsv2
Difficulty 1/5 1-3 hours Newbie friendliness 75/100
hashicorp/terraform-provider-aws#50261 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
certimate-go/certimate#1471 ·
-
Add a check for GitHub flexible federated identity credentials missing an immutable repository claimPossibly taken @harshit3355 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bridgecrewio/checkov#7714 ·
Maintainers usually reply within 1 day
-
alicloud_nas_file_system: support Agentic storage typePossibly taken @BaoZhiFei claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aliyun/terraform-provider-alicloud#10730 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100