AWS Service Operator for Kubernetes makes managing your resources a breeze
Integrate your AWS resources with Kubernetes with this new Service Operator from AWS. Take advantage of Kubernetes’ built-in control loop without any interruptions.
Integrating additional resources into an application in Kubernetes is always a risk. Sometimes they work nicely together; sometimes it causes problem after problem. Thanks to the new Service Operator for Kubernetes, managing your AWS resources is a total breeze.
Usually, if developers wanted to integrate Amazon DynamoDB or deploy a S3 Bucket into their Kubernetes app, they would need tools like AWS CloudFormation or Hashicorp Terriform. These extra tools cause friction, making a disjointed experience between Kubernetes and AWS. They’d need an operator to manage and maintain the pipeline to properly deploy these resources.
However, thanks to the AWS Service Operator, developers can take advantage of the Kubernetes’ built-in control loop and manage their AWS resources directly from the CLI. AWS Services are modeled as Custom Resource Definitions (CRDs) in Kubernetes and applied to the cluster. Essentially, a developer can model their entire application architecture to AWS services, even backing it from a single YAML manifest.
Since Kubernetes is built on top of the controller pattern, it allows apps and tools to listen to central state manager and take appropriate action when necessary. The AWS Service Operate takes advantage of this architecture to create decoupled experiences. No need to worry about how components are integrated!
Additionally, AWS Service Operator will reduce the time it takes to create new apps as well as keep them in the desired state. The desired state is stored within the API server for both the Kubernetes components and the AWS services.
The AWS Service Operator allows developers to to manage DynamoDB Tables, S3 Buckets, Amazon Elastic Container Registry (Amazon ECR) Repositories, SNS Topics, SQS Queues, and SNS Subscriptions. More integrations are coming soon!
Getting the AWS Service Operator for Kubernetes
Want to try this out for yourself? As expected, you will need some kind of AWS account. If you’re using the Amazon Elastic Container Service of Kubernetes (EKS), then you can provision this with CloudFormation. You’ll also need a Kubernetes cluster, kubectl, and awscli. More information is available here.