Search Results for "aws-cpp-sdk-s3"

A Fluent Bit output plugin for CloudWatch Logs. This plugin uses the AWS SDK Go, and uses its default credential provider chain. If you are using the plugin on Amazon EC2 or Amazon ECS or Amazon EKS, the plugin will use your EC2 instance role or ECS Task role permissions or EKS IAM Roles for Service Accounts for pods. The plugin can also retrieve credentials from a shared credentials file, or from the standard AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN environment variables. ...

This project is the source code of lightsailctl, a tool that augments Amazon Lightsail features in AWS CLI. lightsailctl is executed automatically by AWS CLI when certain subcommands are used, such as AWS lightsail push-container-image. lightsailctl is written in Go, so please install Go. Keep reading if you want to work with lightsailctl source code locally. This container image pushing logic requires a number of steps that are outsourced from AWS CLI to lightsailctl.

A Fluent Bit output plugin for Amazon Kinesis Data Firehose. This plugin will continue to be supported. However, we are pausing development on it and will focus on the high-performance version instead. If the features of the higher performance plugin are sufficient for your use cases, please use it. It can achieve higher throughput and will consume less CPU and memory. This plugin has been tested with Fluent Bit 1.2.0+. It may not work with older Fluent Bit versions. We recommend using the...

A Fluent Bit output plugin for Amazon Kinesis Data Streams. A partition key is used to group data by shard within a stream. A Kinesis Data Stream uses the partition key that is associated with each data record to determine which shard a given data record belongs to. For example, if your logs come from Docker containers, you can use container_id as the partition key, and the logs will be grouped and stored on different shards depending upon the id of the container they were generated from....

Networking plugin repository for pod networking in Kubernetes using Elastic Network Interfaces on AWS. Launch kubelet with network plugins set to cni (--network-plugin=cni), the cni directories configured (--cni-config-dir and --cni-bin-dir) and node ip set to the primary IPv4 address of the primary ENI for the instance (--node-ip=$(curl http://169.254.169.254/latest/meta-data/local-ipv4)). It is also recommended that you set --max-pods equal to (the number of ENIs for the instance type × (the number of IPs per ENI - 1)) + 2; for details, see vpc_ip_resource_limit.go. ...