Open Source Linux Cloud Services Software - Page 4
Sort By:
Cloud Services Software for Linux
View 60 business solutions-
$300 Free Credits to Build on Google CloudPut your $300 in credit toward real workloads, then keep building with free monthly usage for 20+ products. No commitment and no charge until you upgrade.
-
Ship Agents FasterGemini Enterprise Agent Platform lets you rapidly build, scale, govern and optimize production-ready agents grounded in your organization's data. The platform enables developers to build custom or pre-built agents for virtually any use case. New customers get $300 in free credits.
-
1
AWS IoT Greengrass Core SDK
SDK to use with functions running on Greengrass Core using Python
The AWS IoT Greengrass Core SDK is meant to be used by AWS Lambda functions running on an AWS IoT Greengrass Core. 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. -
2
AWS Lambda NodeJS Runtime Interface
Extend your preferred base images to be Lambda compatible
We have open-sourced a set of software packages, Runtime Interface Clients (RIC), that implement the Lambda Runtime API, allowing you to seamlessly extend your preferred base images to be Lambda compatible. The Lambda Runtime Interface Client is a lightweight interface that allows your runtime to receive requests from and send requests to the Lambda service. The Lambda NodeJS Runtime Interface Client is vended through npm. You can include this package in your preferred base image to make that base image Lambda compatible. To make it easy to locally test Lambda functions packaged as container images we open-sourced a lightweight web-server, Lambda Runtime Interface Emulator (RIE), which allows your function packaged as a container image to accept HTTP requests. You can install the AWS Lambda Runtime Interface Emulator on your local machine to test your function. -
3
AWS SDK ZF2 Module
ZF2 module for using the AWS SDK for PHP to interact with AWS services
Get started quickly using AWS with the AWS SDK for PHP. The SDK is a modern, open-source PHP library that makes it easy to integrate your PHP application with AWS services like Amazon S3, Amazon Glacier, and Amazon DynamoDB. Version 3 of the AWS SDK for PHP is now generally available and includes a number of improvements and new features while maintaining nearly identical API patterns for easy migration from version 2. Conveniently marshal and unmarshal JSON documents and PHP arrays for storage in Amazon DynamoDB. Remove the session state scale bottleneck by easily storing the application session state in DynamoDB. Use PHP's built-in functions such as fopen, copy, and file_get_contents to work with objects stored in Amazon S3. Automates polling for resource state changes such as waiting for a newly launched Amazon EC2 instance to reach the 'running' state. -
4
AWS SDK for C++
AWS SDK for C++
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. Documentation, code examples and build instructions make integration straightforward, and the modular build ability allows teams to pick and choose service clients. -
Save Up to 91% on Cloud Compute With Spot VMsRun batch jobs at 60-91% off with Spot VMs. Long-running workloads get automatic discounts with sustained use.
-
5
AWS SDK for Ruby
AWS SDK for Ruby
Get started quickly using AWS with the AWS SDK for Ruby. The SDK helps take the complexity out of coding by providing Ruby classes for many AWS services including Amazon S3, Amazon EC2, DynamoDB, and more. The SDK is provided as individual downloadable packages for each AWS service, which include code and documentation. The SDK is also available through Ruby Gems. Version 3 of the AWS SDK for Ruby modularizes the monolithic SDK into service-specific gems, for example, aws-sdk-s3 and aws-sdk-dynamodb. Now each service gem uses strict semantic versioning, along with the benefits of continuous delivery of AWS API updates. With modularization, you can pick and choose which service gems your application or library requires, and update service gems independently of each other. You will need to configure credentials and a region, either in configuration files or environment variables, to make API calls. It is recommended that you provide these via your environment. -
6
AWS Serverless Workshops
Code and walkthrough labs to set up serverless applications
This repository contains a collection of workshops and other hands-on content that will guide you through building various serverless applications using AWS Lambda, Amazon API Gateway, Amazon DynamoDB, AWS Step Functions, Amazon Kinesis, and other services. This workshop shows you how to build a dynamic, serverless web application. You'll learn how to host static web resources with Amazon S3, how to use Amazon Cognito to manage users and authentication, and how to build a RESTful API for backend processing using Amazon API Gateway, AWS Lambda and Amazon DynamoDB. Shows you how to build in security at multiple layers of your application, starting with sign-up and sign-in functionality for your application, how to secure serverless microservices, and how to leverage AWS's identity and access management (IAM) to provide fine-grained access control to your application's users. You'll learn how AWS Amplify integrates with Amazon Cognito, Amazon API Gateway, AWS Lambda, and IAM. -
7
AWS Service Provider for Laravel
A Laravel 5+ (and 4) service provider for the AWS SDK for PHP
This is a simple Laravel service provider for making it easy to include the official AWS SDK for PHP in your Laravel and Lumen applications. Get started quickly using AWS with the AWS SDK for PHP. The SDK is a modern, open-source PHP library that makes it easy to integrate your PHP application with AWS services like Amazon S3, Amazon Glacier, and Amazon DynamoDB. Conveniently marshal and unmarshal JSON documents and PHP arrays for storage in Amazon DynamoDB. Use PHP's built-in functions such as fopen, copy, and file_get_contents to work with objects stored in Amazon S3. Remove the session state scale bottleneck by easily storing application session state in DynamoDB. Automates polling for resource state changes such as waiting for a newly launched Amazon EC2 instance to reach the 'running' state. In order to use the AWS SDK for PHP within your app, you need to retrieve it from the Laravel Service Container. -
8
AWS Service Provider for Silex
Simple Silex service provider for including the AWS SDK for PHP
Get started quickly using AWS with the AWS SDK for PHP. The SDK is a modern, open-source PHP library that makes it easy to integrate your PHP application with AWS services like Amazon S3, Amazon Glacier, and Amazon DynamoDB. Version 3 of the AWS SDK for PHP is now generally available and includes a number of improvements and new features while maintaining nearly identical API patterns for easy migration from version 2. Conveniently marshal and unmarshal JSON documents and PHP arrays for storage in Amazon DynamoDB. Remove the session state scale bottleneck by easily storing the application session state in DynamoDB. Use PHP's built-in functions such as fopen, copy, and file_get_contents to work with objects stored in Amazon S3. Automates polling for resource state changes such as waiting for a newly launched Amazon EC2 instance to reach the 'running' state. -
9
AWS SigV4 Library
AWS library to sign AWS HTTP requests with Signature Version 4
The AWS SigV4 Library is a standalone library for generating authorization headers and signatures according to the specifications of the Signature Version 4 signing process. Authorization headers are required for authentication when sending HTTP requests to AWS. This library can optionally be used by applications sending direct HTTP requests to AWS services requiring SigV4 authentication. This library has no dependencies on any additional libraries other than the standard C library. This library is distributed under the MIT Open Source License. This library has gone through code quality checks including verification that no function has a GNU Complexity score over 8, and checks against deviations from mandatory rules in the MISRA coding standard. Deviations from the MISRA C:2012 guidelines are documented under MISRA Deviations. This library has also undergone static code analysis using Coverity static analysis, and validation of memory safety through the CBMC automated reasoning tool. -
Cut Data Warehouse Costs by 54%BigQuery delivers 54% lower TCO with exabyte scale and flexible pricing. Free migration tools handle the SQL translation automatically.
-
10
AWS VPC Terraform module
Terraform module which creates VPC resources on AWS
Terraform module which creates VPC resources on AWS. By default this module will provision new Elastic IPs for the VPC's NAT Gateways. This means that when creating a new VPC, new IPs are allocated, and when that VPC is destroyed those IPs are released. Sometimes it is handy to keep the same IPs even after the VPC is destroyed and re-created. To that end, it is possible to assign existing IPs to the NAT Gateways. This prevents the destruction of the VPC from releasing those IPs, while making it possible that a re-created VPC uses the same IPs. By default, if NAT Gateways are enabled, private subnets will be configured with routes for Internet traffic that point at the NAT Gateways configured by use of the above options. Since AWS Lambda functions allocate Elastic Network Interfaces in proportion to the traffic received, it can be useful to allocate a large private subnet for such allocations, while keeping the traffic they generate entirely internal to the VPC. -
11
AWS X-Ray Daemon
The AWS X-Ray daemon listens for traffic on UDP port 2000
The AWS X-Ray daemon listens for traffic on UDP port 2000, gathers raw segment data, and relays it to the AWS X-Ray API. The daemon works in conjunction with the AWS X-Ray SDKs and must be running so that data sent by the SDKs can reach the X-Ray service. The X-Ray SDK sends segment documents to the daemon to avoid making calls to AWS directly. You can send the segment/subsegment in JSON over UDP port 2000 to the X-Ray daemon, prepended by the daemon header. On AWS Lambda and AWS Elastic Beanstalk, use those services' integration with X-Ray to run the daemon. Lambda runs the daemon automatically any time a function is invoked for a sampled request. On Elastic Beanstalk, use the XRayEnabled configuration option to run the daemon on the instances in your environment. To run the X-Ray daemon locally, on-premises, or on other AWS services, download it, run it, and then give it permission to upload segment documents to X-Ray. -
12
Amazon CodeGuru Profiler Python Agent
Amazon CodeGuru Profiler Python Agent
Amazon CodeGuru Profiler collects runtime performance data from your live applications and provides recommendations that can help you fine-tune your application performance. Using machine learning algorithms, CodeGuru Profiler can help you find your most expensive lines of code and suggest ways you can improve efficiency and remove CPU bottlenecks. CodeGuru Profiler provides different visualizations of profiling data to help you identify what code is running on the CPU, see how much time is consumed, and suggest ways to reduce CPU utilization. Use CodeGuru Profiler to help profile your applications in the cloud from a single, centralized dashboard. CodeGuru Profiler currently supports applications written in all Java virtual machine (JVM) languages and Python. -
13
Amazon EKS Anywhere
Run Amazon EKS on your own infrastructure
Amazon EKS Anywhere is an open-source deployment option for Amazon EKS that allows customers to create and operate Kubernetes clusters on-premises, with optional support offered by AWS. EKS Anywhere supports VMware vSphere as the first deployment target, with others coming in the near future, including bare metal coming in 2022. Amazon EKS Anywhere helps simplify the creation and operation of on-premises Kubernetes clusters with default component configurations while providing tools for automating cluster management. AWS supports all Amazon EKS Anywhere components including the integrated 3rd-party software, so that customers can reduce their support costs and avoid maintenance of redundant open-source and third-party tools. Amazon EKS Anywhere gives you on-premises Kubernetes operational tooling that’s consistent with Amazon EKS. It builds on the strengths of Amazon EKS Distro and provides open-source software that’s up-to-date and patched. -
14
Amazon Elastic Container Service RPM
Amazon Elastic Container Service RPM
The Amazon Elastic Container Service RPM is software developed to support the Amazon ECS Container Agent. The Amazon ECS RPM is packaged for RPM-based systems that utilize Upstart as the init system. The upstart script installed by the Amazon ECS RPM runs at the completion of runlevel 3, 4, or 5 as the system starts. The script will clean up any previous copies of the Amazon ECS Container Agent, and then start a new copy. Logs from the RPM are available at /var/log/ecs/ecs-init.log, while logs from the Amazon ECS Container Agent are available at /var/log/ecs/ecs-agent.log. The Amazon ECS RPM makes the Amazon ECS Container Agent introspection endpoint available at http://127.0.0.1:51678/v1. Configuration for the Amazon ECS Container Agent is read from /etc/ecs/ecs.config. All of the configurations in this file are used as environment variables of the ECS Agent container. Additionally, some configurations can be used to configure other properties of the ECS Agent container. -
15
Amazon Genomics CLI
Tool to simplify the processes of deploying the AWS infrastructure
Amazon Genomics CLI is an open-source CLI that helps customers run genomics workflows in the cloud by automating the deployment of best practices infrastructure for workflow engines. Amazon Genomics CLI reduces the time for scientists and developers to start running existing genomics workflows at scale and speeds up iteration cycles as they develop new ones. Amazon Genomics CLI is an open-source tool for genomics and life science customers that simplifies and automates the deployment of cloud infrastructure, providing you with an easy-to-use command-line interface to quickly setup and run genomics workflows on Amazon Web Services (AWS) specified by languages like WDL. By removing the heavy lifting from setting up and running genomics workflows in the cloud, software developers and researchers can automatically provision, configure and scale cloud resources to enable faster and more cost-effective population-level genetics studies, drug discovery cycles, and more. -
16
Amazon Neptune Gremlin .NET SigV4
A custom library for Amazon Neptune that enables AWS Signature Version
This project provides a custom library that extends the Apache TinkerPop Gremlin.NET client to enable AWS IAM Signature Version 4 signing for establishing authenticated connections to Amazon Neptune. For example usage refer to: NeptuneGremlinNETSigV4Example.cs. This example shows how to leverage this library for establishing an authenticated connection to Neptune. The GremlinClient library accepts both a GremlinServer object as well as a webSocketConfiguration object that contains a custom configuration set for establishing the WebSocket connection to Amazon Neptune. The SigV4RequestSigner library fetchs IAM credentials using the FallbackCredentialsFactory API (which works similarly to the Java Default Credential Provider Chain), performs the proper Signature Version 4 signing of an http request, and creates the proper WebSocket configuration based on this signed http request. One can then pass this webSocketConfiguration to the GremlinClient to create the connection to Neptune. -
17
Amazon Neptune Gremlin Java Sigv4
A Gremlin client for Amazon Neptune that includes AWS Signature
An extension to GremlinDriver with a custom channelizer that enables AWS Signature Version 4 signed requests to Amazon Neptune. This series uses TinkerPop 3.3.x client. Note that active maintenance on TinkerPop 3.3.x has stopped and hence, this version is not recommended. This series uses TinkerPop 3.4.x client. This major version tracks the latest stable release for this package. Note that a minor version (y in 2.x.y) is bumped whenever a new version of Apache TinkerPop is added as a dependency or a major feature is introduced. All minor versions in 2.x series are backward compatible. This package can also be used to enable Gremlin Console to send signed requests to Neptune, refer to Connecting to Neptune Using the Gremlin Console with Signature Version 4 Signing. -
18
Amazon Neptune Sparql Java Sigv4
A SPARQL client for Amazon Neptune that includes AWS Signature
A SPARQL client for Amazon Neptune that includes AWS Signature Version 4 signing. Implemented as an RDF4J repository. SPARQL client for Amazon Neptune that includes AWS Signature Version 4 signing. Implemented as an RDF4J repository and Jena HTTP Client. -
19
Apache CloudStack
Apache CloudStack is an opensource Infrastructure as a Service (IaaS)
Apache CloudStack is open source software designed to deploy and manage large networks of virtual machines, as a highly available, highly scalable Infrastructure as a Service (IaaS) cloud computing platform. CloudStack is used by a number of service providers to offer public cloud services, and by many companies to provide an on-premises (private) cloud offering, or as part of a hybrid cloud solution. CloudStack is a turnkey solution that includes the entire "stack" of features most organizations want with an IaaS cloud: compute orchestration, Network-as-a-Service, user and account management, a full and open native API, resource accounting, and a first-class User Interface (UI). CloudStack currently supports the most popular hypervisors: VMware, KVM, Citrix XenServer, Xen Cloud Platform (XCP), Oracle VM server and Microsoft Hyper-V. Users can manage their cloud with an easy to use Web interface, command line tools, and/or a full-featured RESTful API. -
20
AutoVPN
Create on demand disposable OpenVPN endpoints on AWS
Script that allows the easy creation of OpenVPN endpoints in any AWS region. Creating a VPN endpoint is done with a single command that takes ~3 minutes. It will create the proper security groups. It spins up a tagged ec2 instance and configures OpenVPN software. Once the instance is configured an OpenVPN configuration file is downloaded and ready to use. There is also functionality to see which instances are running in which region and the ability to terminate the instance when done. Additional functionality includes specifying instance type, generating ssh keypairs, specifying custom AMI, changing login user, and more to come. Create on-demand OpenVPN Endpoints in AWS that can easily be destroyed after done only pay for what you use. -
21
Azure SDK for .NET
Active development of the Azure SDK for .NET
This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs or our versioned developer docs. New wave of packages that we are announcing as GA and several that are currently releasing in preview. These libraries follow the Azure SDK Design Guidelines for .NET and share a number of core features such as HTTP retries, logging, transport protocols, authentication protocols, etc., so that once you learn how to use these features in one client library, you will know how to use them in other client libraries. You can learn about these shared features at Azure.Core. Last stable versions of packages that are production-ready. These libraries provide similar functionalities to the preview packages, as they allow you to use and consume existing resources and interact with them, for example: upload a storage blob. Stable library directories typically contain 'Microsoft.Azure' in their names. -
22
Azure SDK for Java
Active development of the Azure SDK for Java
This repository is for the active development of the Azure SDK for Java. For consumers of the SDK we recommend visiting our public developer docs or our versioned developer docs. To get started with a specific service library, see the README.md file located in the library's project folder. You can find service libraries in the /SDK directory. For a list of all the services, we support to access to our list of all existing libraries. New wave of packages that follow the Azure SDK Design Guidelines for Java and share a number of core features such as HTTP retries, logging, transport protocols, authentication protocols, etc., so that once you learn how to use these features in one client library, you will know how to use them in other client libraries. These libraries can be easily identified by folder, package, and namespaces names starting with azure-, e.g. azure-key vault. -
23
Azure SDK for JavaScript
This repository is for active development of the Azure SDK for JS
This repository is for the Azure SDK for JavaScript (Node.js & Browser). It contains libraries for the breadth of Azure services. Management libraries are packages that you would use to provision and manage Azure resources. Client libraries are packages that you would use to consume these resources and interact with them. The readme for each package contains code samples and package information. This readme can be found in the corresponding package folder under the folder of the service of your choice in the /SDK folder of this repository. The same readme file can be found on the landing page for the package in npm. The API reference documentation of the latest versions of these packages can be found at our public developer docs. The API reference documentation of older versions can be found in our versioned developer docs. -
24
Azure SDK for Python
Active development of the Azure SDK for Python
This repository is for active development of the Azure SDK for Python. For consumers of the SDK we recommend visiting our public developer docs or our versioned developer docs. For your convenience, each service has a separate set of libraries that you can choose to use instead of one, large Azure package. To get started with a specific library, see the README.md (or README.rst) file located in the library's project folder. Last stable versions of packages that have been provided for usage with Azure and are production-ready. These libraries provide you with similar functionalities to the Preview ones as they allow you to use and consume existing resources and interact with them, for example: upload a blob. They might not implement the guidelines or have the same feature set as the November releases. They do however offer wider coverage of services. A new set of management libraries that follow the Azure SDK Design Guidelines for Python are now available. -
25
BLESS
An SSH Certificate Authority that runs as an AWS Lambda function
BLESS is an SSH Certificate Authority that runs as an AWS Lambda function and is used to sign SSH public keys. SSH Certificates are an excellent way to authorize users to access a particular SSH host, as they can be restricted for a single-use case, and can be short-lived. Instead of managing the authorized_keys of a host, or controlling who has access to SSH Private Keys, hosts just need to be configured to trust an SSH CA. BLESS should be run as an AWS Lambda in an isolated AWS account. Because BLESS needs access to a private key that is trusted by your hosts, an isolated AWS account helps restrict who can access that private key, or modify the BLESS code you are running. AWS Lambda functions can use an AWS IAM Policy to limit which IAM Roles can invoke the Lambda Function. If properly configured, you can restrict which IAM Roles can request SSH Certificates.
