【问题标题】:AWS Secrets Manager call from Lambda returning null/none来自 Lambda 的 AWS Secrets Manager 调用返回 null/none
【发布时间】:2022-03-04 01:34:00
【问题描述】:

我正在使用 AWS Lambda 函数调用 AWS Secrets Manager 以检索密钥值,但它只返回值 None/Null。

这是我的代码:

# Secrets Manager
import boto3
import base64
from botocore.exceptions import ClientError


def lambda_handler(event, context):
    # Secrets Manager
    def get_secret():

        secret_name = "arn:aws:secretsmanager:region:accountid:secret:full-secret-name"
        region_name = "region"

        # Create a Secrets Manager client
        session = boto3.session.Session()
        client = session.client(
            service_name='secretsmanager',
            region_name=region_name
        )

        # Only handle the specific exceptions for the 'GetSecretValue' API.
        # See https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_GetSecretValue.html
        # We rethrow the exception by default.

        try:
            get_secret_value_response = client.get_secret_value(
                SecretId=secret_name
            )
        except ClientError as e:
            if e.response['Error']['Code'] == 'DecryptionFailureException':
                # Secrets Manager can't decrypt the protected secret text using the provided KMS key.
                # Deal with the exception here, and/or rethrow at your discretion.
                raise e
            elif e.response['Error']['Code'] == 'InternalServiceErrorException':
                # An error occurred on the server side.
                # Deal with the exception here, and/or rethrow at your discretion.
                raise e
            elif e.response['Error']['Code'] == 'InvalidParameterException':
                # You provided an invalid value for a parameter.
                # Deal with the exception here, and/or rethrow at your discretion.
                raise e
            elif e.response['Error']['Code'] == 'InvalidRequestException':
                # You provided a parameter value that is not valid for the current state of the resource.
                # Deal with the exception here, and/or rethrow at your discretion.
                raise e
            elif e.response['Error']['Code'] == 'ResourceNotFoundException':
                # We can't find the resource that you asked for.
                # Deal with the exception here, and/or rethrow at your discretion.
                raise e
        else:
            # Decrypts secret using the associated KMS CMK.
            # Depending on whether the secret is a string or binary, one of these fields will be populated.
            if 'SecretString' in get_secret_value_response:
                secret = get_secret_value_response['SecretString']
            else:
                decoded_binary_secret = base64.b64decode(get_secret_value_response['SecretBinary'])

    secretValue = get_secret()
    print(secretValue)
    return secretValue

在返回中,我得到null,在打印中我得到None。不太确定我在这里做错了什么,但它不会出错,也不会得到我的价值。

Secret 已加密,但 Lambda IAM 角色拥有 KMS 密钥的使用权限,并且 KMS 密钥也已授予 IAM 角色使用权限。

我也尝试过将 secret_name 设置为 Secrets 名称,如下所示:

secret_name = "full-secret-name-no-arn"

问候

【问题讨论】:

  • 这实际上是我喜欢 Java 的地方。如果您将函数声明为我想要一个秘密值,它看起来像 public String getSecret() - 如果没有返回秘密字符串,编译器会给您一个错误。但是 Python 似乎有这种行为,如果没有明确返回,则将返回值 'None'

标签: amazon-web-services aws-lambda aws-kms aws-secrets-manager


【解决方案1】:

分辨率:

# Secrets Manager
import json
import boto3
import base64
import logging
from botocore.exceptions import ClientError

logger = logging.getLogger()
logger.setLevel(logging.INFO)

def lambda_handler(event, context):
    logger.info("Inside lambda_handler...")

    # SecretsManager
    secretValues = json.loads(get_secret())

def get_secret():
    logger.info("Inside get_secret...")
    secret_name = "full-arn-goes-here"
    region_name = "region-goes-here"

    # Create a Secrets Manager client
    session = boto3.session.Session()
    client = session.client(
        service_name='secretsmanager',
        region_name=region_name

    )

    try:
        get_secret_value_response = client.get_secret_value(SecretId=secret_name)
        logger.info("Received Response")
    except ClientError as e:
        if e.response['Error']['Code'] == 'DecryptionFailureException':
            # Secrets Manager can't decrypt the protected secret text using the provided KMS key.
            # Deal with the exception here, and/or rethrow at your discretion.
            raise e
        elif e.response['Error']['Code'] == 'InternalServiceErrorException':
            # An error occurred on the server side.
            # Deal with the exception here, and/or rethrow at your discretion.
            raise e
        elif e.response['Error']['Code'] == 'InvalidParameterException':
            # You provided an invalid value for a parameter.
            # Deal with the exception here, and/or rethrow at your discretion.
            raise e
        elif e.response['Error']['Code'] == 'InvalidRequestException':
            # You provided a parameter value that is not valid for the current state of the resource.
            # Deal with the exception here, and/or rethrow at your discretion.
            raise e
        elif e.response['Error']['Code'] == 'ResourceNotFoundException':
            # We can't find the resource that you asked for.
            # Deal with the exception here, and/or rethrow at your discretion.
            raise e
        else:
            # Please see https://docs.aws.amazon.com/secretsmanager/latest/apireference/CommonErrors.html for all the other types of errors not handled above
            raise e
    else:
        # Decrypts secret using the associated KMS CMK.
        # Depending on whether the secret is a string or binary, one of these fields will be populated.
        if 'SecretString' in get_secret_value_response:
            logger.info("Inside string response...")
            return get_secret_value_response['SecretString']
        else:
            logger.info("Inside binary response...")
            return base64.b64decode(get_secret_value_response['SecretBinary'])

只需将secretValues = json.loads(get_secret()) 放入您的处理程序即可。

【讨论】:

  • 我认为你在问题中的代码最初的问题是你没有在 get_secret() 中返回秘密
【解决方案2】:

您的 get_secret() 没有返回语句

【讨论】:

    【解决方案3】:

    除了上述更改之外,请确保您的 Lambda 执行角色具有访问密钥管理器和 KMS 服务的适当权限。这是附加到执行角色的示例 IAM 策略。应用后,以下策略将允许 Lambda 检索密钥而不返回“无”。

    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": "logs:CreateLogGroup",
                "Resource": "arn:aws:logs:us-west-2:<ACCOUNT_ID>:*"
            },
            {
                "Effect": "Allow",
                "Action": [
                    "logs:CreateLogStream",
                    "logs:PutLogEvents"
                ],
                "Resource": [
                    "arn:aws:logs:us-west-2:<ACCOUNT_ID>:log-group:/aws/lambda/sampletest*:*"
                ]
            },
            {
                "Effect": "Allow",
                "Action": [
                    "secretsmanager:GetSecretValue",
                    "secretsmanager:DescribeSecret",
                    "secretsmanager:ListSecretVersionIds",
                    "secretsmanager:PutSecretValue",
                    "secretsmanager:UpdateSecret",
                    "secretsmanager:TagResource",
                    "secretsmanager:UntagResource"
                ],
                "Resource": [
                    "arn:aws:secretsmanager:us-west-2:<ACCOUNT_ID>:secret:<SECRET_NAME>"
                ]
            },
            {
                "Effect": "Allow",
                "Action": [
                    "kms:Decrypt"
                ],
                "Resource": "arn:aws:kms:us-west-2:<ACCOUNT_ID>:key/<KMS_ID>"
            }
        ]
    }
    

    【讨论】:

      【解决方案4】:

      问题很棘手......因为 AWS 没有为您提供任何有价值的日志信息,说明缺少访问 Secrets Manager 服务的权限。您需要处理正在运行的进程的 IAM 角色,并为 Secrets Manager 访问添加适当的权限,它不会出现问题!!!

      AWS 只是返回 'None' 却没有给你任何错误信息,真是令人沮丧:(

      【讨论】:

        猜你喜欢
        • 2021-03-17
        • 2020-09-28
        • 2023-01-01
        • 2019-08-30
        • 2020-10-26
        • 2021-02-13
        • 2023-03-18
        • 2020-04-07
        • 2019-05-03
        相关资源
        最近更新 更多