0.0" Apply the configuration terraform init to initialize the following modules module.aws-vpc module.aws-elb module.aws-iam $ terraform init Once initialized , execute: $ terraform plan -out=aws_kubespray_plan brokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized

0" Apply the configuration terraform init to initialize the following modules module.aws-vpc module.aws-elb module.aws-iam $ terraform init Once initialized , execute: $ terraform plan -out=aws_kubespray_plan brokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized

0" Apply the configuration terraform init to ini�alize the following modules module.aws-vpc module.aws-elb module.aws-iam $ terraform init Once ini�alized , execute: $ terraform plan -out=aws_kubespray_plan Ka�a brokers o�en handles many different topics at once (read this Introduc�on to Ka�a [h�ps://ka�a.apache.org/intro] for more background). In our simple example, the Empire uses a Ka�a cluster to handle --topic empire-a >>[2018-04-10 23:50:34,638] ERROR Error when sending message to topic empi org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized This is because the policy does

0" Apply the configuration terraform init to initialize the following modules module.aws-vpc module.aws-elb module.aws-iam $ terraform init Once initialized , execute: $ terraform plan -out=aws_kubespray_plan brokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized

0" Apply the configuration terraform init to initialize the following modules module.aws-vpc module.aws-elb module.aws-iam $ terraform init Once initialized , execute: $ terraform plan -out=aws_kubespray_plan brokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized

0" Apply the configuration terraform init to initialize the following modules module.aws-vpc module.aws-elb module.aws-iam $ terraform init Once initialized , execute: $ terraform plan -out=aws_kubespray_plan brokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized

0" Apply the configuration terraform init to initialize the following modules module.aws-vpc module.aws-elb module.aws-iam $ terraform init Once initialized , execute: $ terraform plan -out=aws_kubespray_plan brokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized

are not well suited for a dev platform ● The processing overhead is non-trivial ● Falco's eBPF module + ContainerOS was not very performant Attempt #1 - The Postmortem Iteration is key ● Built a Use Ubuntu instead of ContainerOS Current Implementation Iteration is key ● Move back to eBPF module to reduce our OS footprint ● Smarter rules based on user behavior ● Automatically respond to

evolution of the kernel. Applications User space Kernel System calls Files Networking Process Module Memory One day, a concerned Captain Tux reviewed the crew And remembered that bees had long been eBPF programs run as efficiently as natively compiled kernel code or as code loaded as a kernel module. Linux supports JIT compilation towards all widespread architectures. System calls Acquiring a