Partner human-services agencies must upload case PDFs into the county's governed Amazon S3 buckets using familiar SFTP workflows without giving partners broad AWS console access. Which migration transfer approach fits?
Select an answer to reveal the explanation.
Short Explanation
Partners already speak SFTP; don't force them onto the AWS console or spray public bucket writes. Transfer Family gives managed SFTP into your governed S3 buckets—polite front door, locked house.
Full Explanation
Partner human-services agencies that must upload case PDFs into the county's governed Amazon S3 buckets using familiar SFTP workflows—without broad AWS console access—fit AWS Transfer Family for managed SFTP into those buckets. That preserves partner usability while keeping IAM, encryption, and logging under county control for confidential case materials shared across agencies. Sharing long-lived root account access keys with every partner agency fails least privilege and creates unmanageable credential sprawl across external organizations. Opening anonymous public S3 writes from the internet for convenience fails confidentiality for sensitive case PDFs and violates typical retention and privacy policies. Requiring partners to ship paper printouts for scanning after cutover fails digital migration goals and reintroduces courier and privacy risk for vulnerable residents. Exam caveat: Transfer Family is the SFTP-to-S3 pattern for external partners into governed buckets. Operational check: stand up Transfer Family endpoints, map partner identities to scoped IAM roles into governed prefixes, enable logging and encryption, ban shared root keys, and pilot one agency before broad rollout across human-services partners.