Search Results for "external"

Spring Cloud Config provides server-side and client-side support for externalized configuration in a distributed system. With the Config Server, you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production, you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. ...

The AWS SDK for C++ is a modern, open-source library offering C++ applications native access to AWS services like S3, DynamoDB, Kinesis and more. It is built to support C++11 (and later) and is designed to be high-performance with minimal external dependencies, making it suitable for game engines, embedded systems, cross-platform clients and server applications. The SDK provides both high-level APIs (for common use) and low-level service client access (for full control) so developers can mix convenience and fine-tuned behavior as needed. It supports major platforms including Windows, macOS, and Linux, and uses CMake for builds so you can include only the services your application needs, helping reduce binary size and surface attack area. ...

Protect the most sensitive parts of your organization; from senior executive discussion to intellectual property and cybersecurity. An entire communications platform under your control, with end-to-end encrypted voice, video, messaging and collaboration. Easily scales to serve the largest of organizations, supply chains and entire ecosystems. Support thousands of users in a single end-to-end encrypted chat room. Connect millions in real time across multiple organizations. Decentralization...

...Provides interfaces to implement your own business logic for selecting which events to process, processing events, handling errors, and handling log processing status updates. Monitor, store, and validate activity events for authenticity. Easily generate audit reports required by internal policies and external regulations.

ExternalDNS synchronizes exposed Kubernetes Services and Ingresses with DNS providers. Inspired by Kubernetes DNS, Kubernetes' cluster-internal DNS server, ExternalDNS makes Kubernetes resources discoverable via public DNS servers. Like KubeDNS, it retrieves a list of resources (Services, Ingresses, etc.) from the Kubernetes API to determine the desired list of DNS records. Unlike KubeDNS, however, it's not a DNS server itself, but merely configures other DNS providers accordingly, e.g. AWS...

GLBC is a GCE L7 load balancer controller that manages external loadbalancers configured through the Kubernetes Ingress API. Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Ingress resource. An Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL / TLS, and offer name-based virtual hosting.

Kubernetes External Secrets allows you to use external secret management systems, like AWS Secrets Manager or HashiCorp Vault, to securely add secrets in Kubernetes. Read more about the design and motivation for Kubernetes External Secrets on the GoDaddy Engineering Blog. The community and maintainers of this project and related Kubernetes secret management projects use the #external-secrets channel on the Kubernetes slack for discussion and brainstorming. ...

Cloudprober is a monitoring software that makes it super-easy to monitor availability and performance of various components of your system. Cloudprober employs the “active” monitoring model. It runs probes against (or on) your components to verify that they are working as expected. For example, it can run a probe to verify that your frontends can reach your backends. Similarly it can run a probe to verify that your in-Cloud VMs can actually reach your on-premise systems. This kind of...

...It will enable Lambda functions to invoke other Lambda functions deployed to the Greengrass Core, publish messages to the Greengrass Core and work with the local Shadow service. To use the AWS IoT Greengrass Core SDK, you must first import the AWS IoT Greengrass Core SDK in your Lambda function as you would with any other external libraries. You then need to create a client for ‘iot-data’ or ‘lambda’. Use ‘iot-data’ if you wish to publish messages to the local Greengrass Core and interact with the local Shadow service. Use ‘lambda’ if you wish to invoke other Lambda functions deployed to the same Greengrass Core. As new features are added to AWS IoT Greengrass, newer versions of the AWS IoT Greengrass SDK may be incompatible with older versions of the AWS IoT Greengrass core.