QuestionQ86

VerifiedSecurity

A developer is building an application that gives users the ability to view bank accounts from multiple sources in a single dashboard. The developer has automated the process to retrieve API credentials for these sources. The process invokes an AWS Lambda function that is associated with an AWS CloudFormation custom resource.

The developer wants a solution that will store the API credentials with minimal operational overhead.

Which solution will meet these requirements in the MOST secure way?

Explanation

Since the credentials are retrieved externally by the custom-resource Lambda function itself (not generated by CloudFormation), the function can call the ssm:PutParameter SDK operation and store them as a genuine SecureString parameter, which encrypts the value with AWS KMS at rest and in transit. This requires no additional infrastructure to manage, giving minimal operational overhead. NoEcho (options C and D) is a CloudFormation template-parameter display attribute, not an actual encryption mechanism for a stored SSM parameter value, so it does not secure the credential the way SecureString does, and Secrets Manager's GenerateSecretString (option A) is meant for auto-generating new random secrets, not storing externally-retrieved credentials.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!