Thank you so much!😄 Yes, IaC (using Terraform, Serverless, CloudFormation, etc) is a topic that I find very interesting. I have a video series about The Serverless framework ( ua-cam.com/video/5xBHeN5OOzI/v-deo.html ) where I use it to deploy lambda functions, API gateways etc. I will try to make more videos like these in the future. If CloudFormation templates itself is a topic that you find interesting, I can try to make some videos about that as well. Maybe integrate it with the Serverless framework, since that is a very common use case. Or just write native CloudFormation templates 🙌 Thank you for the tip, much appreciated!😄
Hi :) Well, it depends on what kind error you get, but by looking at the code you have written: It can be because you have double quotes surrounding the Overwrite statement. This should be a Boolean (True or False) without quotes. Another cause to the issue could be that your Lambda execution role don't have the required access to do write operations on SSM parameters. The policy I added in this video have only read access. You should create a custom IAM policy with write access to your SSM parameter and attach it to the Lambda execution role. Just as an example: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "ssm:PutParameter", "Resource": "arn:aws:ssm:REGION_NAME:YOUR_AWS_ACCOUNT:parameter/YOUR_PARAMETER_NAME" } ] } I've tested this code and It should work: client = boto3.client('ssm') response = client.put_parameter(Name='external-api-url', Value='test put', Overwrite=True)
@@EndreSynnes thank you...I have fixed the error..one more thing ..curtently we store 100 versions of a parameter after to store one more version it will delete the first inserted. Is there any alternate way
I see 😃 Parameter Store will only store 100 versions of the same parameter, so yes it will delete the oldest version if you go above that limit. Is there any particular reason you have to store more than 100 versions and still keep the first one? There is a workaround described here (docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-versions.html) as "moving parameter labels", but again you should maybe look into why you would need so many versions in the first place 😊
Thank you for the video. Explanation is very clear and easy to understand. Keep up the good work
Thank you! 😄
Thank you for the explaining , neat and simple
Thank you!😄
I love the hands on parts. You should consider also making videos about using CloudFormation templates to deploy Lambdas and other resources etc.
Thank you so much!😄 Yes, IaC (using Terraform, Serverless, CloudFormation, etc) is a topic that I find very interesting. I have a video series about The Serverless framework ( ua-cam.com/video/5xBHeN5OOzI/v-deo.html ) where I use it to deploy lambda functions, API gateways etc. I will try to make more videos like these in the future. If CloudFormation templates itself is a topic that you find interesting, I can try to make some videos about that as well. Maybe integrate it with the Serverless framework, since that is a very common use case. Or just write native CloudFormation templates 🙌
Thank you for the tip, much appreciated!😄
good video!
Thank you! 😄
Please help its urgent, How can I retreive stored values from parameter store using Java?
Hi,
The aws documentation has some examples using Java which should work fine 😊 docs.aws.amazon.com/cdk/v2/guide/get_ssm_value.html
Hii...How to update ssm parameters from lambda..I have used put_paramete(Name="",Value="",type="",Overwrite="True")...but it showing error
Hi :)
Well, it depends on what kind error you get, but by looking at the code you have written: It can be because you have double quotes surrounding the Overwrite statement. This should be a Boolean (True or False) without quotes.
Another cause to the issue could be that your Lambda execution role don't have the required access to do write operations on SSM parameters. The policy I added in this video have only read access. You should create a custom IAM policy with write access to your SSM parameter and attach it to the Lambda execution role.
Just as an example:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "ssm:PutParameter",
"Resource": "arn:aws:ssm:REGION_NAME:YOUR_AWS_ACCOUNT:parameter/YOUR_PARAMETER_NAME"
}
]
}
I've tested this code and It should work:
client = boto3.client('ssm')
response = client.put_parameter(Name='external-api-url', Value='test put', Overwrite=True)
@@EndreSynnes thank you...I have fixed the error..one more thing ..curtently we store 100 versions of a parameter after to store one more version it will delete the first inserted. Is there any alternate way
I see 😃 Parameter Store will only store 100 versions of the same parameter, so yes it will delete the oldest version if you go above that limit. Is there any particular reason you have to store more than 100 versions and still keep the first one? There is a workaround described here (docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-versions.html) as "moving parameter labels", but again you should maybe look into why you would need so many versions in the first place 😊
@@EndreSynnes yes I don't need but just wanted to know if there is any way