Benjamin Edwards
1208c0151e
feat(firehose): add Terraform documentation to README.md feat(firehose): add Terraform module for IAM policy feat(firehose): add Terraform output for IAM policy ARN docs(byo-firehose-logging-destination): add introduction and explanation of IAM role and policy This commit adds an introduction and explanation of the IAM role and policy defined in the Terraform code. Specifically, it explains that the IAM role named `fleet_role` is being defined in the AWS account, and that it will be assumed by the Fleet application being hosted. The commit also explains that the IAM role is being given specific permissions to perform certain actions on the Firehose service, and that the associated IAM policy specifies the minimum allowed permissions. Additionally, the commit explains that the Firehose service is KMS encrypted, and that the IAM role needs permission to the KMS key being used to encrypt the data going into Firehose. Finally, the commit explains that the code sets up a secure and controlled environment for the Fleet application to perform its necessary actions on the Firehose service within the AWS account. refactor(byo-firehose-logging-destination): reformat table of resources and inputs feat(byo-firehose-logging-destination): add KMS key resource for firehose encryption feat(byo-firehose-logging-destination): add S3 bucket resource for logging destination feat(byo-firehose-logging-destination): add IAM policy and role resources for firehose feat(byo-firehose-logging-destination): add IAM policy attachment resource for fleet-firehose policy feat(byo-firehose-logging-destination): add data source for current AWS region feat(byo-firehose-logging-destination): add data source for KMS alias feat(byo-firehose-logging-destination): add data source for IAM policy documents feat(byo-firehose-logging-destination): add outputs for firehose IAM role, delivery streams, and S3 bucket fix(iam.tf): change aws_iam_policy and aws_iam_policy_attachment resource names to include fleet prefix closes https://github.com/fleetdm/fleet/issues/11331
Website News Report a bug
Fleet is the lightweight, open source telemetry platform for servers and workstations. Deploy osquery with Fleet to get comprehensive, customizable data from all your devices and operating systems – without the downtime risk.
Try Fleet
Head to fleetdm.com/try-fleet to fire up a one-off cloud instance for quickly trying out Fleet.
Now what?
Check out the Learn how to use Fleet doc to learn how to add your device to Fleet and how to ask questions about your devices by running queries.
Team
Fleet is independently backed and actively maintained with the help of many amazing contributors.
📖 In keeping with our value of openness, Fleet Device Management's company handbook is public and open source. You can read about the history of Fleet and osquery and our commitment to improving the product. To upgrade from Fleet ≤3.2.0, just follow the upgrading steps for the earliest subsequent major release from this repository (it'll work out of the box until the release of Fleet 5.0).
Documentation
Documentation for Fleet can be found here.
Community
Chat
Please join us in the #fleet channel on osquery Slack.
Contributing
Contributions are welcome, whether you answer questions on Slack/GitHub/StackOverflow/Twitter, improve the documentation or website, write a tutorial, give a talk, start a local osquery meetup, troubleshoot reported issues, or submit a patch. The Fleet code of conduct is on GitHub.
