certwatch | monitor Certificate Transparency logs and to find
kandi X-RAY | certwatch Summary
kandi X-RAY | certwatch Summary
This application is designed to monitor Certificate Transparency logs and to find any new certificates issued for domain suffix and add them to a Postgresql database. Specifically, once every 24 hours it will fetch the latest list of known CT logs from Google (see jobs/job_update_logs.go) and set up a "cron" such that every 5 minutes a new signed tree head will be fetched (see jobs/job_check_sth.go), and if the tree size has increased, a job will be scheduled for fetch new entries (see jobs/job_get_entries.go). The fetch entries job will try to fetch up to around 1000 entries at once, and if for any reason not all entries are returned (which is permitted per RFC6962), it will reschedule 2 new jobs to fetch half of the remaining entries each. If any requests fail, they will be retried using the que-go library, which handles exponential back-off. Once new certificates of interest are detected, they are written to the Postgresql database, and (if configured) will send a notification to Slack hook, and (if configured) will add an entry to a CKAN data source (such as data.gov.au).
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- GetEntries fetches all entries for a job .
- getFieldsAndValsForCert returns a map of fields for a cert .
- CheckLogSTH checks the status of the STH configuration .
- RefreshMetadataForEntries refreshes all certs for the given certificates
- makeGovAURecord decodes a ckanRecord from bkle tree .
- NewLogMetadata adds a new log entry to the database .
- UpdateCTLogList updates the CTLog metadata for a known log
- showCert shows a certificate
- Main entry point for testing .
- makeClientForURL returns an http client and an http . Client for the given connectURL .
certwatch Key Features
certwatch Examples and Code Snippets
Community Discussions
Trending Discussions on certwatch
QUESTION
I originally posted this question as an issue on the GitHub project for the AWS Load Balancer Controller here: https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2069.
I'm seeing some odd behavior that I can't trace or explain when trying to get the loadBalacnerDnsName from an ALB created by the controller. I'm using v2.2.0 of the AWS Load Balancer Controller in a CDK project. The ingress that I deploy triggers the provisioning of an ALB, and that ALB can connect to my K8s workloads running in EKS.
Here's my problem: I'm trying to automate the creation of a Route53 A Record that points to the loadBalancerDnsName
of the load balancer, but the loadBalancerDnsName
that I get in my CDK script is not the same as the loadBalancerDnsName
that shows up in the AWS console once my stack has finished deploying. The value in the console is correct and I can get a response from that URL. My CDK script outputs the value of the DnsName as a CfnOutput value, but that URL does not point to anything.
In CDK, I have tried to use KubernetesObjectValue
to get the DNS name from the load balancer. This isn't working (see this related issue: https://github.com/aws/aws-cdk/issues/14933), so I'm trying to lookup the Load Balancer with CDK's .fromLookup
and using a tag that I added through my ingress annotation:
ANSWER
Answered 2021-Jun-13 at 20:23I think that the answer is to use external-dns.
ExternalDNS allows you to control DNS records dynamically via Kubernetes resources in a DNS provider-agnostic way.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install certwatch
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page