Minimizing Credential Overhead for EC2 and Aurora

Design secure access to AWS resources. Determine appropriate data security controls.
Answer Correct answer: A — Use AWS Secrets Manager with automatic rotation enabled so EC2 instances fetch fresh Aurora user names and passwords without manual file maintenance.

A company has an application that runs on Amazon EC2 instances and uses an Amazon Aurora database. The EC2 instances connect to the database by using user names and passwords that are stored locally in a file. The company wants to minimize the operational overhead of credential management. What should a solutions architect do to accomplish this goal?

  1. Use AWS Secrets Manager. Turn on automatic rotation. Correct Answer
  2. Use AWS Systems Manager Parameter Store. Turn on automatic rotation.
  3. Create an Amazon S3 bucket to store objects that are encrypted with an AWS Key Management Service (AWS KMS) encryption key. Migrate the credential file to the S3 bucket. Point the application to the S3 bucket.
  4. Create an encrypted Amazon Elastic Block Store (Amazon EBS) volume for each EC2 instance. Attach the new EBS volume to each EC2 instance. Migrate the credential file to the new EBS volume. Point the application to the new EBS volume.

Community Insight

The question tests which AWS service can both store and automatically rotate database credentials, and the common trap is assuming Parameter Store offers native rotation or that re-hosting the file on S3/EBS reduces management effort.

This SAA-C03 scenario asks how an EC2-hosted application should stop storing Aurora user names and passwords in a local file while cutting credential-management overhead. AWS Secrets Manager with automatic rotation is the correct answer (A), because it centrally stores, encrypts, and rotates database credentials without manual intervention.

Option B is the most common wrong pick because learners associate Parameter Store with secrets, but it has no built-in rotation capability unless you build and run your own Lambda-based rotation logic yourself.

Community Discussion (113 comments)

suhan_14 👍 2 Selected: A
A is correct. AWS secret manager make sense in here with auto rotation to reduce blast radius of leaked cred, as AWS SM is build to store these types of sensitive info. AWS System manager params store is build to storing much less concerning cred like normal url, app config etc.
46e1a46 👍 1 Selected: A
A: AWS Secrets Manager is purpose-built for storing database credentials and natively supports automatic rotation for Amazon Aurora, which eliminates the operational overhead of manually managing and rotating credentials
tungpt_me 👍 1 Selected: A
A is the correct answer. B incorrect. AWS parameter store doesn't have auto rotation
Moindev65 👍 1 Selected: B
Use API Gateway → SQS FIFO → Lambda. SQS FIFO guarantees first-in, first-out processing and exactly-once delivery per MessageGroupId. API Gateway can integrate directly with SQS to enqueue each order; Lambda processes from the FIFO queue. A (SNS) and D (SQS standard) don’t guarantee ordering. C (auhttps://www.examtopics.com/exams/amazon/aws-certified-solutions-architect-associate-saa-c03/view/1/#thorizer) is unrelated to ordering or processing flow.
Clouddon 👍 1 Selected: A
Use AWS Secrets Manager with automatic rotation enabled to securely manage Aurora database credentials, eliminate manual updates, and minimize operational overhead.
trieu81200111 👍 1 Selected: A
A is correct
hossex5 👍 1 Selected: A
a is the answer
Kamatchi 👍 2 Selected: A
This is asked in the exam I have taken today
MundiChor 👍 1 Selected: A
Order of elimination: B. Parameter Store can store secrets. You can enforce TTL to expire credentials but you cannot auto rotate C and D are plan overhead and not secure enough.
ak240519 👍 1 Selected: A
A is the correct answer. as Instance store doesn't support auto rotation
adamatic 👍 1 Selected: A
AWS Secrets Manager is a service that helps users manage, rotate, and retrieve secrets for applications, services, and IT resources. It can be used to secure secrets for AWS Cloud, third-party services, and on-premises -Automatic rotation: Secrets can be automatically rotated
MGKYAING 👍 2 Selected: A
AWS Secrets Manager: Is a managed service specifically designed to securely store and retrieve secrets, such as database credentials, API keys, and SSH keys. Provides features like automatic rotation, which helps to reduce the risk of compromised credentials. Integrates seamlessly with many AWS services, including Amazon RDS (which Aurora is a part of).
Gizmo2022 👍 1
Answer is A https://aws.amazon.com/cn/blogs/security/how-to-connect-to-aws-secrets-manager-service-within-a-virtual-private-cloud/ https://aws.amazon.com/blogs/security/rotate-amazon-rds-database-credentials-automatically-with-aws-secrets-manager/
Abishek016 👍 3 Selected: A
This is an ideal solution. Secrets Manager can rotate credentials automatically and ensures that the EC2 instances retrieve the most recent credentials securely.
Buruguduystunstugudunstuy 👍 3 Selected: A
Option A, using AWS Secrets Manager and turning on automatic rotation, would be the best solution to minimize the operational overhead of credential management. AWS Secrets Manager is a service that makes it easier to manage secrets, such as database credentials, by storing and rotating them automatically. By turning on automatic rotation, you can ensure that the secrets are regularly rotated, reducing the risk of unauthorized access to the database. This would minimize the operational overhead of credential management, as you would not have to manually rotate the secrets or update the EC2 instances with the new credentials.
Buruguduystunstugudunstuy 👍 1
Option B, using AWS Systems Manager Parameter Store and turning on automatic rotation, would not be suitable for storing secrets, such as database credentials, as it is intended for storing system parameters. Option C, creating an S3 bucket to store objects that are encrypted with an AWS KMS encryption key and migrating the credential file to the S3 bucket, would not provide automatic rotation of the secrets. Option D, creating an encrypted EBS volume and migrating the credential file to the new EBS volume, would not provide automatic rotation of the secrets.
Ruffyit 👍 2
A: READ!!! AWS Secrets Manager is a secrets management service that helps you protect access to your applications, services, and IT resources. This service enables you to rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle. It says SSM Parameter store cant rotate automatically.
jallaix 👍 3
Everybody here voting A, but only the master user's password of the Aurora database can be automatically stored and rotated. Who uses the master user's credentials in their application ? It looks to me like a serious security issue... Moreover answer A is not complete, missing steps are: - create IAM role to get secret - assign IAM role to EC2 instance - adapt the application to retrieve the secret from Secrets Manager instead of erading the file - make sure retrieval occurs every week I dont' call that minimizing operational overhead... Answer D is a lot more simple. In a real situation, none of these answers are relevant.
iyiola_daniel 👍 1
Same thing I thought. Answer D seems simpler, but option A is the best approach.
griggrig 👍 1 Selected: A
Option A , because of leas overhead.
parth_g_mehta 👍 1 Selected: A
Parameter Store: Storing and managing a database connection string or API endpoint URL that doesn’t require frequent rotation. Secrets Manager: Storing and managing database credentials that need to be rotated regularly for security compliance.
JalimRabeiBR 👍 1
Answer A is correct
OctavioBatera 👍 1 Selected: A
Secrets Manager, as The Mandalorian would say "this is the way!"
TilTil 👍 1 Selected: A
SSM has no automatic rotation.
Shalini10dec 👍 1
The most suitable option for minimizing operational overhead of credential management in this scenario is: B. Use AWS Systems Manager Parameter Store. Turn on automatic rotation. AWS Systems Manager Parameter Store is a service that helps you manage configuration data, including sensitive information such as passwords and database strings, in a central, secure store. With automatic rotation enabled, the credentials can be automatically updated at scheduled intervals, reducing the manual effort required for credential management.
Kanagarajd 👍 1 Selected: A
Secret manager with auto rotation.
awsgeek75 👍 1 Selected: A
BCD are extremely high operational overhead and not secure like A
A_jaa 👍 1 Selected: A
A is correct
ifaby 👍 3 Selected: B
B becasue the user wants reduce costs and SSM Parameter Store layer Standard is free and the type SecureString uses KMS
AbirAbu 👍 2
It should be "A."
santbot 👍 1 Selected: A
A - SECREATS MANAGER
Mandar15 👍 3 Selected: A
Aurora automatically stores and manages database credentials in AWS Secrets Manager. Aurora rotates database credentials regularly, without requiring application changes. Secrets Manager secures database credentials from human access and plain text view.
NaaVeeN 👍 4
If most Voted answers is done by us, then Who is marking the answers as Correct ?
novice16 👍 1 Selected: A
Secret manager and auto rotation does the job
Blackberry 👍 1
Can admit update only 💯 answers. It's confusing most voted or correct answer which to prefer
akshunn 👍 1 Selected: A
A it is
Hassaoo 👍 1
A is Right Because secret manager is meant for Rds Integration
PLN6302 👍 1
Option A
kapalulz 👍 2 Selected: A
parameter store does not support auto rotation and AWS Secrets Manager does.
TariqKipkemei 👍 1 Selected: A
Minimize the operational overhead of credential management = AWS Secrets Manager
hakim1977 👍 1 Selected: A
The answer is A without hesitation, in the AWS console: Secret manager => store a ne secret => choose the "Credentials for Amazon RDS database" option
oguzbeliren 👍 1
Parameter store doesn't support password rotation, but secret manger does.
Guru4Cloud 👍 1 Selected: A
Here is the explanation: AWS Secrets Manager is a service that provides a secure and convenient way to store, manage, and rotate secrets. Secrets Manager can be used to store database credentials, SSH keys, and other sensitive information. AWS Secrets Manager also supports automatic rotation, which can help to minimize the operational overhead of credential management. When automatic rotation is enabled, Secrets Manager will automatically generate new secrets and rotate them on a regular schedule
james2033 👍 1 Selected: A
A
miki111 👍 1
Option A MET THE REQUIREMENT
cookieMr 👍 8 Selected: A
Option A: Using AWS Secrets Manager and enabling automatic rotation is the recommended solution for minimizing the operational overhead of credential management. AWS Secrets Manager provides a secure and centralized service for storing and managing secrets, such as database credentials. By leveraging Secrets Manager, the application can retrieve the database credentials programmatically at runtime, eliminating the need to store them locally in a file. Enabling automatic rotation ensures that the database credentials are regularly rotated without manual intervention, enhancing security and compliance.
TienHuynh 👍 1 Selected: A
A is a right choice
hypnozz 👍 2
A is the right choice...Because, in Both you can force to rotate or delete de secrets, but, in secrets manager you can use a lambda to generate automatic secrets, also, it´s integrated with RDS, like Aurora...and it´s mostly used for that propouse. You can use parameter store, but you have to update the parameters by yourself
Bmarodi 👍 1 Selected: A
Option A meets this goal.
beginnercloud 👍 1 Selected: A
A is correct
cheese929 👍 1 Selected: A
A is the most logial answer.
cheese929 👍 1
A is correct
CLOUDUMASTER 👍 1
Key term used is with less operational overhead, systems parameter store allows you to do the same at no additional cost and where Secrets manager charges 0.40 per secret. Nowhere in the text does is say that autorotation is a must and furthermore, enabling auto rotation is available of parameter store..
Azaa 👍 3 Selected: A
From the AWS doc it clearly saying choose AWS Secrets manager if it requires auto rotation ``` To implement password rotation lifecycles, use AWS Secrets Manager. You can rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle using Secrets Manager. For more information, see What is AWS Secrets Manager? in the AWS Secrets Manager User Guide.
chibaniMed 👍 1 Selected: A
AWS Systems Manager Parameter Store provides secure, hierarchical storage for configuration data management and secrets management. You can store data such as passwords, database strings, and license codes as parameter values. However, Parameter Store doesn't provide automatic rotation services for stored secrets. Instead, Parameter Store enables you to store your secret in Secrets Manager, and then reference the secret as a Parameter Store parameter.
mrgeee 👍 1 Selected: A
Definitely A
Dinoo_Man 👍 1
A is correct: Secrets Manager: It was designed specifically for confidential information (like database credentials, API keys) that needs to be encrypted, so the creation of a secret entry has encryption enabled by default. It also gives additional functionality like rotation of keys.
CLOUDUMASTER 👍 2
B sounds logical there is no question saying that auto rotation is supposed to be a key component though
SaranJ 👍 1 Selected: A
operational overhead of credential management is the key term which means secret rotation and encryption and these are features of Secret Manager. Although Aurora doesn't have built-in integration with Secret Manager but focus on Keyword of the question gives an Answer = A
PhucVuu 👍 4 Selected: A
Keywords: - User names and passwords that are stored locally in a file -> minimize the operational overhead of credential management. (Improve security with lowest operational overhead) A: Correct - with AWS Secret Manager the the username and password will be encrypted with KMS and it also has the automatic rotation. B: Incorrect - AWS Systems Manager Parameter Store don't have automatic rotation C: Incorrect - Actually, we can apply this but we will do a lot of things compare to AWS Secret Manager. D: Incorrect - We can do this but it is required more operational overhead than AWS Secret Manager
gx2222 👍 1 Selected: A
To minimize the operational overhead of credential management, a solutions architect should use AWS Secrets Manager. AWS Secrets Manager is a secrets management service that helps you protect access to your applications, services, and IT resources without the upfront investment and on-going maintenance costs of operating your own infrastructure. It enables you to retrieve clear text secrets such as database credentials and API keys securely, rotate secrets safely, and manage access with detailed audit logs. In this case, the architect can store the user names and passwords in AWS Secrets Manager and configure automatic rotation of credentials to enhance security. The application can then retrieve the credentials from Secrets Manager at runtime instead of from a file stored locally on each EC2 instance, which minimizes operational overhead. Therefore, Option A is the correct answer.
channn 👍 1 Selected: A
Key words: database user and password; minimize the operational. Option B: AWS Systems Manager Parameter Store does not support automatic rotation of secrets. Option C: additional steps is required Option D: requires additional management
acuaws 👍 2 Selected: B
B Parameter Store DOES NOT provide automatic rotation.
linux_admin 👍 1 Selected: A
Option A suggests using AWS Secrets Manager to manage the user names and passwords used to connect to the Amazon Aurora database. By storing the credentials in Secrets Manager, the company can centrally manage the credentials and control access to them. With automatic rotation turned on, Secrets Manager can automatically generate new credentials at regular intervals, minimizing the operational overhead of credential management.
jdr75 👍 3
CORRECT IS A, not B, and it's evident. Again Examtopis offers the incorrect anwer as the correct. Who is responsible of choosing the incorrect answer in examtopics as the correct one? -- someone should think about this, because it's not serious.
sanking 👍 1 Selected: B
With AWS Secrets Manager, the application code can retrieve credentials securely by calling Secrets Manager APIs, eliminating the need to store secrets in the code or configuration files. So if we select A, there are a lot code change (from read pwd from file to call API). AWS Systems Manager Parameter Store can use AWS Secrets Manager to manage password. And "You can reference Systems Manager parameters in your scripts, commands, SSM documents, and configuration and automation workflows by using the unique name that you specified when you created the parameter. " It is easy to switch to use “the unique name”. So B is better than A. (B include A)
bilel500 👍 1 Selected: A
AWS Secrets Manager enables you to rotate, manage, and retrieve database credentials, API keys and other secrets throughout their lifecycle. It also makes it really easy for you to follow security best practices such as encrypting secrets and rotating these regularly.
KittieHearts 👍 1 Selected: A
It's a secret key, it will be A.
ahalamri 👍 1 Selected: A
A is Correct.
Bilal_2019 👍 1 Selected: A
To minimize the operational overhead of credential management, a solutions architect could implement the following: Use AWS Secrets Manager to store and manage the database user names and passwords securely. Update the application to retrieve the user names and passwords from AWS Secrets Manager instead of from the local file. By using AWS Secrets Manager, the company can centrally manage the database user names and passwords and enforce security best practices such as regular rotation of secrets, fine-grained access control, and audit trail of secret usage. This can help simplify the credential management and improve the security of the application.
Bilal_2019 👍 1 Selected: B
Yes, using AWS Systems Manager Parameter Store is a good option for minimizing the operational overhead of credential management in this scenario. Here's what you can do: Store the database credentials securely in the Parameter Store as a SecureString data type. Enable automatic rotation of the credentials to periodically generate a new set of credentials and update the stored value in the Parameter Store. Modify the application to retrieve the credentials from the Parameter Store at runtime, rather than storing them locally in a file. By doing this, the management and rotation of the credentials can be automated, which reduces the operational overhead and ensures the security of the system.
Bilal_2019 👍 1
Chat GPT Chooses A with explanation as below To minimize the operational overhead of credential management, a solutions architect could implement the following: Use AWS Secrets Manager to store and manage the database user names and passwords securely. Update the application to retrieve the user names and passwords from AWS Secrets Manager instead of from the local file. By using AWS Secrets Manager, the company can centrally manage the database user names and passwords and enforce security best practices such as regular rotation of secrets, fine-grained access control, and audit trail of secret usage. This can help simplify the credential management and improve the security of the application.
Bilal_2019 👍 1
Also, chooses B Yes, using AWS Systems Manager Parameter Store is a good option for minimizing the operational overhead of credential management in this scenario. Here's what you can do: Store the database credentials securely in the Parameter Store as a SecureString data type. Enable automatic rotation of the credentials to periodically generate a new set of credentials and update the stored value in the Parameter Store. Modify the application to retrieve the credentials from the Parameter Store at runtime, rather than storing them locally in a file. By doing this, the management and rotation of the credentials can be automated, which reduces the operational overhead and ensures the security of the system.
buiducvu 👍 1 Selected: A
Selected Answer: A
BlueVolcano1 👍 1 Selected: A
There's no automatic rotation in Parameter Store.
nalindm 👍 1 Selected: A
parameter store does not support auto rotation
jannymacna 👍 1
A. use AWS secrets Manager... No debate
Abdel42 👍 1 Selected: A
B is wrong because it does not support automatic rotation
SilentMilli 👍 2 Selected: A
AWS Secrets Manager is a secrets management service that enables you to store, manage, and rotate secrets such as database credentials, API keys, and SSH keys. Secrets Manager helps you secure your secrets by automatically rotating them according to a schedule that you specify. This can help minimize the operational overhead of managing and rotating secrets, as well as reduce the risk of secrets being compromised. With Secrets Manager, you can store the user names and passwords for your Amazon Aurora database in a central location and have them automatically rotated on a schedule that you specify. The EC2 instances can then retrieve the secrets as needed, rather than having to store them locally in a file.
aba2s 👍 2 Selected: A
B is wrong because parameter store does not support auto rotation. please see this link at the end https://tutorialsdojo.com/aws-secrets-manager-vs-systems-manager-parameter-store/
AdiosAmigo 👍 1
In the question, it was said to be a file stored locally on the instance. It seems unencrypted. If you look at this part, it seems that the parameter store is correct.
xicomynor 👍 1
Except that parameter store does not support auto-rotation. So the statement is incorrect.
techhb 👍 1 Selected: A
its A
Ello2023 👍 1
A. Less admin overheads.
melearning 👍 1 Selected: A
The operation overhead should be minimal. This can be done in secret manager.
wombles 👍 2
Parameter Store supports automatic rotation through its Secrets Manager integration as per the documentation A - is correct in this scenario.
psr83 👍 2 Selected: A
To implement password rotation lifecycles, use AWS Secrets Manager. You can rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle using Secrets Manager. For more information
kvenikoduru 👍 1
It should be A;
NikaCZ 👍 1 Selected: A
AWS Secrets Manager is a secrets management service that helps you protect access to your applications, services, and IT resources. This service enables you to rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle.
rajesh1216 👍 1 Selected: B
It's A for obvious reason
NikaCZ 👍 1 Selected: A
AWS Secrets Manager is a secrets management service that helps you protect access to your applications, services, and IT resources.
yoben84 👍 1 Selected: A
something is weird with these answers. the community can't be all wrong
Nandan747 👍 1 Selected: A
Now, this is absurd. B is DEFINITELY not right simply because Parameter store DOES NOT support auto-rotation of keys. Correct Answer is A C, D- Too much operational overhead, you can achieve the same thing using Secrets Manager w/o doing all that.
SilentMilli 👍 1 Selected: A
Secrets Manager permit rotation
benaws 👍 1
Obviously A
zabouchedid 👍 1 Selected: A
A
shyam_yadav 👍 1
Ans is A
DannisExamTopic 👍 1 Selected: A
secrets manager is newer
Wpcorgan 👍 1
A is correct
ABCMail 👍 1 Selected: A
AWS secrets manager is most logical
Kartikey140 👍 1
A option is correct.
al20220711 👍 2
The advantage of Systems Manager over Secrets Manager is costing. But it doesn't mention in the question. SO A is better.
17Master 👍 35 Selected: A
READ!!! AWS Secrets Manager is a secrets management service that helps you protect access to your applications, services, and IT resources. This service enables you to rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle.
KVK16 👍 4 Selected: A
AWS Secrets Manager, a service that makes it easier to rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle. You can configure Secrets Manager to rotate secrets automatically, which can help you meet your security and compliance needs. Secrets Manager offers built-in integrations for MySQL, PostgreSQL, and Amazon Aurora on Amazon RDS, and can rotate credentials for these databases natively. You can control access to your secrets by using fine-grained AWS Identity and Access Management (IAM) policies. To retrieve secrets, employees replace plaintext secrets with a call to Secrets Manager APIs, eliminating the need to hard-code secrets in source code or update configuration files and redeploy code when secrets are rotated.
BoboChow 👍 2 Selected: A
AWS Secrets Manager is newer to SSM Parameter Store, and I'm not sure the later one can turn on automatic rotation
josh_fan 👍 1 Selected: A
A
ogerber 👍 4 Selected: A
no rotation option on parameter store. never store credentials on buckets, its a hazard. its A!!
D2w 👍 1 Selected: A
A, is meant for storing secrets e.g password ect
tuloveu 👍 3 Selected: A
A is correct.
rein_chau 👍 3 Selected: A
A is correct.
Sinaneos 👍 107 Selected: A
B is wrong because parameter store does not support auto rotation, unless the customer writes it themselves, A is the answer.
hro 👍 5
A - additionally, Aurora manages the settings for the secret and rotates the secret every seven days by default.
iCcma 👍 3
ty bro, I was confused about that and you just mentioned the "key" phrase, B doesn't support autorotation

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

AWS Secrets Manager is purpose-built to store, retrieve, and rotate credentials throughout their lifecycle, and it ships with native rotation support for Amazon Aurora, Amazon RDS MySQL/PostgreSQL and other engines via a Lambda rotation function. Turning on automatic rotation removes the manual cycle of updating the local credential file, so the EC2 application simply calls GetSecretValue at runtime and always receives fresh, KMS-encrypted credentials. This directly satisfies the stated goal of minimizing operational overhead of credential management while eliminating the plaintext file on disk. As hro noted, "Aurora manages the settings for the secret and rotates the secret every seven days by default."

Why the Other Options Are Wrong

Option B fails because Systems Manager Parameter Store does not support automatic rotation natively; as Sinaneos stated, "parameter store does not support auto rotation, unless the customer writes it themselves." Option C merely relocates the same credential file into an S3 object, which still requires the application to fetch and parse a static file, adds an S3 dependency, and ogerber warned "never store credentials on buckets, its a hazard." Option D is equally weak: an encrypted EBS volume is still a locally mounted file per instance, so every rotation forces manual file updates on each EC2 instance and multiplies operational work instead of reducing it.

Community Comment Notes

The comment thread converges strongly on A, with PhucVuu framing the trade-off as "Improve security with lowest operational overhead" and KVK16 pointing to Secrets Manager's "built-in integrations for MySQL, PostgreSQL, and Amazon Aurora." cookieMr emphasized that the application "can retrieve the database credentials programmatically at runtime," which matches the recommended integration pattern. Abishek016 summarized the consensus that automatic rotation "ensures that the EC2 instances retrieve the most recent credentials securely." One commenter, NaaVeeN, questioned how answers get marked correct, which is a workflow concern rather than a technical one.

Official Reference

Exam Strategy

When a question says to minimize operational overhead around credentials, immediately look for automatic rotation — Secrets Manager is the only AWS service offering it natively for RDS/Aurora. Eliminate any option that keeps the secret in a file-like store, since relocation to S3 or EBS does not reduce rotation work.

Frequently Asked Questions

Why can't I use Parameter Store to rotate the Aurora credentials automatically?

Parameter Store has no built-in rotation engine for database credentials. You would have to author, deploy, and maintain your own Lambda rotation function, which defeats the goal of minimizing operational overhead.

Why is moving the credential file to an S3 bucket or EBS volume not enough?

S3 and EBS only relocate the stored file; the application still reads static credentials and someone must still update the file on every rotation. Neither service performs automatic credential rotation for you.

More SAA-C03 FAQ →

Related Analysis

A financial services company wants to shut down two data cen

A-Grade

A company runs its legacy web application on AWS. The web ap

A-Grade

A company needs to use its on-premises LDAP directory servic

A-Grade

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide