A courts case-management vendor insists on an exotic database engine feature that Amazon RDS does not support, and the county otherwise standardizes on managed RDS and Aurora. How should architects treat a self-managed database on Amazon EC2?
Select an answer to reveal the explanation.
Short Explanation
Self-managed on EC2 is the exception desk, not the county standard. If courts truly need a feature RDS doesn't have, document it, run it on EC2, and keep an exit ramp. Don't turn one vendor quirk into a fleet of homemade databases.
Full Explanation
Task 4.3 allows self-managed databases on EC2 when engine features or vendor constraints block Amazon RDS or Aurora, but that choice must be an explicit, documented exception rather than the default. Professional practice records the blocking feature, operational ownership, backup and DR, and a path to managed services later. Defaulting every department to EC2, refusing AWS entirely, or replacing the OLTP engine with ElastiCache misapplies the exception.