Okuthunyelwe kuchaza izinyathelo zokwenza ngokuzenzakalelayo ukuphathwa kwezitifiketi ze-SSL kusuka
Lesi sihloko sihlukaniswe izigaba ezi-4:
- ukudala ifayela le-zip;
- ukwakha indima ye-IAM;
- ukudala umsebenzi we-lambda osebenzayo i-acme-dns-route53;
- ukudala isibali sikhathi se-CloudWatch esicupha umsebenzi izikhathi ezi-2 ngosuku;
Qaphela: Ngaphambi kokuthi uqale udinga ukufaka
Idala ifayela le-zip
I-acme-dns-route53 ibhalwe ku-GoLang futhi isekela inguqulo engekho ngaphansi kuka-1.9.
Sidinga ukudala ifayela le-zip elinambambili acme-dns-route53
ngaphakathi. Ukuze wenze lokhu udinga ukufaka acme-dns-route53
kusuka endaweni yokugcina ye-GitHub usebenzisa umyalo go install
:
$ env GOOS=linux GOARCH=amd64 go install github.com/begmaroman/acme-dns-route53
I-binary ifakiwe $GOPATH/bin
umkhombandlela. Sicela uqaphele ukuthi ngesikhathi sokufakwa sicacise izindawo ezimbili ezishintshile: GOOS=linux
ΠΈ GOARCH=amd64
. Bakwenza kucace ku-Go compiler ukuthi idinga ukudala kanambambili ofanele i-Linux OS kanye ne-amd64 architecture - yilokhu okusebenza ku-AWS.
I-AWS ilindele ukuthi uhlelo lwethu lusetshenziswe kufayela le-zip, ngakho-ke masidale acme-dns-route53.zip
ingobo yomlando ezoqukatha kanambambili esanda kufakwa:
$ zip -j ~/acme-dns-route53.zip $GOPATH/bin/acme-dns-route53
Qaphela: Okunambambili kufanele kube kuyimpande yengobo yomlando ye-zip. Kulokhu sisebenzisa -j
ifulege.
Manje isiteketiso sethu se-zip sesilungele ukusetshenziswa, okusele nje ukudala indima ngamalungelo adingekayo.
Ukudala indima ye-IAM
Sidinga ukumisa indima ye-IAM ngamalungelo adingwa i-lambda yethu ngesikhathi isenziwa.
Asibize le nqubomgomo lambda-acme-dns-route53-executor
futhi ngokushesha umnikeze indima eyisisekelo AWSLambdaBasicExecutionRole
. Lokhu kuzovumela i-lambda yethu ukuthi isebenze futhi ibhale amalogi kusevisi ye-AWS CloudWatch.
Okokuqala, sakha ifayela le-JSON elichaza amalungelo ethu. Lokhu kuzovumela izinsiza ze-lambda ukuthi zisebenzise indima lambda-acme-dns-route53-executor
:
$ touch ~/lambda-acme-dns-route53-executor-policy.json
Okuqukethwe kwefayela lethu kungokulandelayo:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"logs:CreateLogGroup"
],
"Resource": "arn:aws:logs:<AWS_REGION>:<AWS_ACCOUNT_ID>:*"
},
{
"Effect": "Allow",
"Action": [
"logs:PutLogEvents",
"logs:CreateLogStream"
],
"Resource": "arn:aws:logs:<AWS_REGION>:<AWS_ACCOUNT_ID>:log-group:/aws/lambda/acme-dns-route53:*"
},
{
"Sid": "",
"Effect": "Allow",
"Action": [
"route53:ListHostedZones",
"cloudwatch:PutMetricData",
"acm:ImportCertificate",
"acm:ListCertificates"
],
"Resource": "*"
},
{
"Sid": "",
"Effect": "Allow",
"Action": [
"sns:Publish",
"route53:GetChange",
"route53:ChangeResourceRecordSets",
"acm:ImportCertificate",
"acm:DescribeCertificate"
],
"Resource": [
"arn:aws:sns:${var.region}:<AWS_ACCOUNT_ID>:<TOPIC_NAME>",
"arn:aws:route53:::hostedzone/*",
"arn:aws:route53:::change/*",
"arn:aws:acm:<AWS_REGION>:<AWS_ACCOUNT_ID>:certificate/*"
]
}
]
}
Manje ake siqhube umyalo aws iam create-role
ukudala indima:
$ aws iam create-role --role-name lambda-acme-dns-route53-executor
--assume-role-policy-document ~/lambda-acme-dns-route53-executor-policy.json
Qaphela: khumbula inqubomgomo i-ARN (Igama Lensiza Ye-Amazon) - sizoyidinga ezinyathelweni ezilandelayo.
Indima lambda-acme-dns-route53-executor
idaliwe, manje sidinga ukucacisa izimvume zayo. Indlela elula yokwenza lokhu ukusebenzisa umyalo aws iam attach-role-policy
, inqubomgomo yokuphasisa i-ARN AWSLambdaBasicExecutionRole
kanje:
$ aws iam attach-role-policy --role-name lambda-acme-dns-route53-executor
--policy-arn arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole
Qaphela: uhlu olunezinye izinqubomgomo lungatholakala
Idala umsebenzi we-lambda osebenzayo i-acme-dns-route53
Hooray! Manje usungakwazi ukuthumela umsebenzi wethu ku-AWS usebenzisa umyalo aws lambda create-function
. I-lambda kufanele imiswe kusetshenziswa okuguquguqukayo kwemvelo okulandelayo:
AWS_LAMBDA
- ikwenza kucace i-acme-dns-route53 lokho kubulawa kwenzeka ngaphakathi kwe-AWS Lambda.DOMAINS
β uhlu lwezizinda ezihlukaniswe ngokhefana.LETSENCRYPT_EMAIL
- iquketheMasibethele I-imeyili .NOTIFICATION_TOPIC
- Igama le-SNS Notification Topic (uyazikhethela).STAGING
- ngenani1
indawo yesiteji isetshenziswa.1024
MB - umkhawulo wememori, ungashintshwa.900
amasekhondi (15 min) - ukuphela kwesikhathi.acme-dns-route53
- Igama le-binary yethu, elisendaweni yomlando.fileb://~/acme-dns-route53.zip
- indlela eya endaweni yomlando esiyidalile.
Manje masisebenzise:
$ aws lambda create-function
--function-name acme-dns-route53
--runtime go1.x
--role arn:aws:iam::<AWS_ACCOUNT_ID>:role/lambda-acme-dns-route53-executor
--environment Variables="{AWS_LAMBDA=1,DOMAINS="example1.com,example2.com",[email protected],STAGING=0,NOTIFICATION_TOPIC=acme-dns-route53-obtained}"
--memory-size 1024
--timeout 900
--handler acme-dns-route53
--zip-file fileb://~/acme-dns-route53.zip
{
"FunctionName": "acme-dns-route53",
"LastModified": "2019-05-03T19:07:09.325+0000",
"RevisionId": "e3fadec9-2180-4bff-bb9a-999b1b71a558",
"MemorySize": 1024,
"Environment": {
"Variables": {
"DOMAINS": "example1.com,example2.com",
"STAGING": "1",
"LETSENCRYPT_EMAIL": "[email protected]",
"NOTIFICATION_TOPIC": "acme-dns-route53-obtained",
"AWS_LAMBDA": "1"
}
},
"Version": "$LATEST",
"Role": "arn:aws:iam::<AWS_ACCOUNT_ID>:role/lambda-acme-dns-route53-executor",
"Timeout": 900,
"Runtime": "go1.x",
"TracingConfig": {
"Mode": "PassThrough"
},
"CodeSha256": "+2KgE5mh5LGaOsni36pdmPP9O35wgZ6TbddspyaIXXw=",
"Description": "",
"CodeSize": 8456317,
"FunctionArn": "arn:aws:lambda:us-east-1:<AWS_ACCOUNT_ID>:function:acme-dns-route53",
"Handler": "acme-dns-route53"
}
Idala isibali sikhathi se-CloudWatch esicupha umsebenzi izikhathi ezi-2 ngosuku
Isinyathelo sokugcina ukusetha i-cron, ebiza umsebenzi wethu kabili ngosuku:
- dala umthetho we-CloudWatch ngevelu
schedule_expression
. - dala umgomo womthetho (lokho okufanele kwenziwe) ngokucacisa i-ARN yomsebenzi we-lambda.
- nikeza imvume kumthetho wokushayela umsebenzi we-lambda.
Ngezansi nginamathisele ukucushwa kwami ββkwe-Terraform, kodwa empeleni lokhu kwenziwa kalula kusetshenziswa ikhonsoli ye-AWS noma i-AWS CLI.
# Cloudwatch event rule that runs acme-dns-route53 lambda every 12 hours
resource "aws_cloudwatch_event_rule" "acme_dns_route53_sheduler" {
name = "acme-dns-route53-issuer-scheduler"
schedule_expression = "cron(0 */12 * * ? *)"
}
# Specify the lambda function to run
resource "aws_cloudwatch_event_target" "acme_dns_route53_sheduler_target" {
rule = "${aws_cloudwatch_event_rule.acme_dns_route53_sheduler.name}"
arn = "${aws_lambda_function.acme_dns_route53.arn}"
}
# Give CloudWatch permission to invoke the function
resource "aws_lambda_permission" "permission" {
action = "lambda:InvokeFunction"
function_name = "${aws_lambda_function.acme_dns_route53.function_name}"
principal = "events.amazonaws.com"
source_arn = "${aws_cloudwatch_event_rule.acme_dns_route53_sheduler.arn}"
}
Manje usulungiselelwe ukuthi udale futhi ubuyekeze ngokuzenzakalelayo izitifiketi ze-SSL
Source: www.habr.com