¶ Intro
Application and database connection can be done via
- Environment variables. But this is not secure and not recomended way.
- Dependency lib in helm chart.
Lets review dependency lib option in this guide and follow below steps to get it done.
¶ Dependency lib
If you deploy new helm chart to sview application repository make sure you include dependency lib in Chart.yaml
dependencies:
- name: lib
version: 0.2.0
repository: "file://../lib/"
¶ Modify IAM service
Figure shows new IAM service account creation . If you have it allready just modify by adding policy
policies:
- "arn:aws:iam::1111111111:policy/env-pod-sa-ssm-read-dev-<tenant>-plat"
role:
policies:
LogAccess: |
...
¶ SSM Parameter
Supported:
- global (shared)
- individual (for one app)
Usualy database HOSTNAME, PASSWORD and USERNAME are auto created for databases. all you need just define env var names you need expose.
s example we define Mysql RDS connection keys as db: dependency.
we have created shared Mysql RDS instance that will be used for few applications.
AWS mysql-rds is deployed in to lambdas namespace with instance name shared . So no matter where your app is deployed you can reference Database instance .
envKey - we define name for Environment Variable that we expect in our application
secretKey - is key name in SSM parameter. there are auto defined keys for database :
- username
- password
- endpoint
- replica_endpoint_1
- replica_endpoint_2
- ...
For more information about dependencies management check dependency management page.