Search for a command to run...
I am a Lead Engineer from India. Love to blog about serverless and help teams design and develop serverless architecture. An AWS cloud practitioner. Blogs about AWS Services utilising AWS CDK, CloudFormation, Terraform.
No comments yet. Be the first to comment.
Transformers, the backbone of many state-of-the-art NLP models such as BERT, GPT has revolutionized the way we approach natural language understanding tasks. One key innovation in transformers is their ability to handle entire sequences of tokens sim...
When an User prompts the questions to the LLM, it produces the response based on the training data. The pre-trained LLM data is its parametric data. It might not have an context specific to our query. LLM still produces an answer confidently. It is t...
In the fast-evolving field of artificial intelligence, Large Language Models (LLMs) have rapidly transformed how we approach language processing. These models, such as ChatGPT, Claude, and Bard, have proven their utility across a range of application...
Amazon S3 is a powerful, scalable storage service, but when multiple clients or processes attempt to write to the same S3 object simultaneously, things can get tricky. Since S3 doesn’t natively handle concurrent writes or provide object locking, it’s...
When working with distributed systems in a microservice architecture, we must always architect our services with failure in mind. When the transaction happens between a microservice, we have to handle the failures. The Saga pattern can be used in a f...
Terraform is a great Infrastructure As Code tool for provisioning cloud services using declarative configuration files. The most common question that comes up with terraform is how to handle the secrets like database passwords, Authentication Keys, and other data which are sensitive.
We should not store the sensitive data in plain text in our Terraform configuration. Because anyone who has access to that repository can see the secrets.
Never store sensitive data in plain text
AWS Secret Manager allows us to retrieve database credentials, API keys, and other secrets using Secret Manager API. Instead of storing the hardcoded secret values, we can directly fetch them from the secret manager API. It also provides us the option to rotate the credentials for a configurable number of days.
In this blog post, we will create a secret in AWS Secrets Manager and show how we can retrieve the values using Terraform.
Select the AWS secret Manager service from the AWS console.
Click on Store a new secret button.
It provides various options for the secret Type. It supports credentials for RDS, DocumentDB, Redshift clusters, and also other types of secret. Here, we select other types of secret.
In Plaintext store the MongoDB credentials.
mongodb://USERNAME:PASSWORD@rahul-mongo.cluster.ap-south-1.docdb.amazonaws.com:27017
Click on Next and then provide the secret name mongodbURI.
Click on Next and you can configure automatic rotation. We will Disable automatic rotation.
Click on Next and you will be taken to review the configuration. Click on the Store button.
You can see the secret in the list as shown below.
Now, in the terraform code, we can use the aws_secretsmanager_secret_version data source to read this secret.
data "aws_secretsmanager_secret" "secret_name" {
name = "mongodbURI"
}
data "aws_secretsmanager_secret_version" "secret_credentials" {
secret_id = data.aws_secretsmanager_secret.secret_name.id
}
And now you can use those secrets in the rest of your Terraform code. For example, we can get the secrets in environment_variables.
environment_variables = {
"mongoURI" = data.aws_secretsmanager_secret_version.secret_credentials.secret_string
}
In our Lambda, we can see the value is extracted by going to the AWS Lambda console and check the environment variable.
In this blog post, we see how to create a secret in the AWS Secret Manager service. We also looked at the terraform script to extract the secret values into the environment variable of Lambda. The associated Git Repository is here