Search for a command to run...
I’m Lakhan Samani from India 🇮🇳. I’m the creator and maintainer of authorizer.dev | Freelance Software Engineer | Prev: Cloud Software Engineer at ArangoDB. I am passionate about building products and developer tools. This website is my internet space, where I write about Building Software | Open Source | Finance and Life.
No comments yet. Be the first to comment.
Permission-aware RAG with Authorizer + OpenFGA + Qdrant: a runnable demo where two users ask the same question and get different answers — because the vector search itself respects who can see what. Fully self-hosted.
We just shipped Authorizer v2 — a major rewrite of our open-source, self-hosted authentication and authorization server. If you've ever been frustrated by per-seat auth pricing, vendor lock-in, or shi
In this blog post, we will learn how to authorize users for API calls, based on valid sessions and roles using Authorizer. Authorizer is an open-source database-independent auth solution. You can bring your database and have authentication and author...
We’re excited to announce the stable version of https://authorizer.dev with the most significant updates 🥳. The most complex part of your application, i.e. auth has never been this simple in the open-source space before. Bring your database and have...
Hello people, on 3rd November 2022 I had amazing opportunity to speak at AWS community (Vadodara) event happening in my city. I presented on using Authorizer with DynamoDB and EKS.
Authorizer is database independent open source auth solution. It supports 12+ databases including all the major SQL, NoSQL and Graph databases.
So, as a part of demo I created a Task Manager (TODO) application, which will allow authenticated user to
The tech stack we will be using is:
Here is a small architecture diagram demonstrating how the overall application will look like
Github Repository: This repository contains code for TODO API, Frontend Application, EKS Cluster Creation, Ingress / Domain Setup
aws configure --profile PROFILE_NAME
export AWS_PROFILE=PROFILE_NAME
export AWS_ACCESS_KEY_ID=YOUR_ACCESS_KEY_ID
export AWS_SECRET_ACCESS_KEY=YOUR_SECRET_ACCESS_KEY
git clone https://github.com/lakhansamani/authorizer-aws-demo.git
cd authorizer-aws-demo
Note: You can update machine configuration in eks.yaml file.
eksctl create cluster -f eks.yaml
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx \
--namespace ingress-nginx \
--create-namespace \
--timeout 600s \
--debug \
--set controller.publishService.enabled=true
Cert manager is used to generate TLS certificate
helm repo add jetstack https://charts.jetstack.io
helm repo update
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.8.2/cert-manager.crds.yaml
helm install \
cert-manager jetstack/cert-manager \
--namespace cert-manager \
--create-namespace \
--version v1.8.2
Note: Please change
authorizer.authorizer_urlas per your domain and URL.
helm repo add authorizer https://helm-charts.authorizer.dev
helm repo update
helm install \
--set authorizer.database_type=dynamodb \
--set authorizer.aws_access_key_id=${AWS_ACCESS_KEY_ID} \
--set authorizer.aws_secret_access_key=${AWS_SECRET_ACCESS_KEY} \
--set authorizer.aws_region=us-east-1 \
--set authorizer.authorizer_url=https://auth.aws-demo.authorizer.dev \
--set redis.install=true \
--set redis.storage=5Gi \
--set redis.storageClassName=gp2 \
--set securityContext.readOnlyRootFilesystem=false \
authorizer authorizer/authorizer
Example: auth.aws-demo.authorizer.dev in below screenshot
Note: Change email & hostzoneID as per step5 in
cluster_issuer.yaml
Cert manager will add txt record and will verify the domain details using this issuer.
kubectl apply -f cluster_issuer.yaml
Note: Change authorizer domain as per your auth domain in
authorizer_ingress.yaml
kubectl apply -f authorizer_ingress.yaml
Open your authorizer dashboard, configure admin password and get client ID.
Note: Change
authorizer_client_idto based64 encoded value authorizer client_id value obtained in step 7 in api.yaml L:8. Also change domain name in ingress section.
kubectl apply -f api.yaml
You can deploy frontend to provider of your choice OR on the same stack. For demo purpose I have deployed it on Netlify and connected subdomain there.
Thats all you need. Hope it makes your life easier to deploy authorizer + any other service on AWS
For more information check