A company wants to share information with a third party. The third party has an HTTP API endpoint that the company can use to share the information. The company has the required API key to access the HTTP API.
The company needs a way to manage the API key by using code. The integration of the API key with the application code cannot affect application performance.
Which solution will meet these requirements MOST securely?
Storing the API credentials in AWS Secrets Manager is the most secure and practical solution. AWS Secrets Manager provides a secure way to manage and retrieve sensitive information, like API keys, without hardcoding them in the source code or storing them in less secure locations. By using AWS SDK to retrieve the credentials at runtime, the application can maintain strong security without compromising performance.
answer A
Why B is marked as correct ????
parameter store is secure, so A
Answer A
Secret Manager is the safest way to store secrets in AWS.
B isn't secury A is the best option for this scenary
Most secure
parameter store is the better solution so A
The other options (B, C and D) are not as safe or manageable:
A is correct
A seems to be the most secure and correct. Always use Secret Manger to store secrets, as the name implies.
A is correct
Straight A
A is it
A is the correct answer.
A is correct. B is wrong because you never store credentials in source control.
B is certainly a wrong answer because if you read the application development with AWS case study and also the best practices then in it the AWS itself does not encourage the developer to store the sensitive API and license keys in code on the other hand it encourages to use the provided solutions like KMS, Secrets Manager and Parameter Store.