A logistics company is integrating its on-premises inventory server with AWS. The server must automatically upload daily reports to an Amazon S3 bucket. To comply with strict security standards, the company prohibits storing long-term AWS access keys on the physical on-premises server. Which configuration represents the most secure AWS-recommended best practice to grant this access?
- ACreate an IAM user with programmatic access, attach the required S3 policy, and store the long-term access keys in an encrypted file on the server.
- BGenerate access keys for the AWS account root user, and configure the server's backup script to use these credentials for direct authentication.
- Configure AWS IAM Roles Anywhere on the on-premises server to obtain temporary, short-lived security credentials using local digital certificates.Cevap
- DModify the S3 bucket policy to grant write access to the public, relying entirely on the on-premises server's source IP address restriction for security.
Cevap
Configure AWS IAM Roles Anywhere on the on-premises server to obtain temporary, short-lived security credentials using local digital certificates.
The configuration utilizing AWS IAM Roles Anywhere is correct because it allows on-premises physical hardware to authenticate using local digital certificates (X.509) and assume an IAM role. This process returns temporary, short-lived security credentials (access key, secret key, and session token), successfully eliminating the need to store long-term keys on the server.
Adım Adım Çözüm
Anahtar Kavram
AWS IAM Roles Anywhere enables on-premises workloads to securely access AWS resources using temporary IAM credentials derived from local X.509 digital certificates, eliminating long-term credentials.
Alternatif Yöntem
An alternative method is to register the on-premises server as an AWS Systems Manager (SSM) managed instance using Systems Manager Hybrid Activations, allowing it to assume IAM roles through the SSM Agent.
Tahmini Süre:2m 0s