AWS DocumentDB
Description​
Amazon DocumentDB is a scalable, fully managed, and highly durable document database service provided by Amazon Web Services (AWS). It's designed to be compatible with MongoDB, a popular NoSQL database, allowing developers to use the same MongoDB application code, drivers, and tools they already use today. Amazon DocumentDB is engineered to provide high availability, reliability, and scalability, making it suitable for workloads that require stable performance and the ability to recover from disaster scenarios.
General details​
- Developer(s): Amazon Web Services (AWS)
- Open source: No
- Language(s): Not applicable as it's managed by AWS. However, it interfaces with applications typically written in languages supported by MongoDB drivers (e.g., Python, Java, Node.js).
- Repository: N/A
- License: The service is provided under AWS's service terms and conditions.
- Operating system(s): As a fully managed service, Amazon DocumentDB runs on AWS infrastructure. The underlying operating system management is abstracted away from the user.
- Actively maintained: Yes (within the past month)
Intended use on the device​
The SOUP is used in the medical device for the following specific purposes only:
- Long-term storage of record history of user interactions with web API endpoints (information sent by the user and response issued by the API).
- As an alternative to a SQL database to store information (email, password, name, organization, etc.) of the users that have been registered in the web API. This information is later accessed for user authentication.
- Keep a registry of the historical versions of the AI models and microservices of the medical device.
Requirements​
For the integration and safe usage of this SOUP within a software system, it's important to outline both functional and performance requirements. These requirements help mitigate risks and ensure compatibility and performance standards are met.
Functional​
- Compatibility with MongoDB: Maintain strong compatibility with MongoDB, supporting the same APIs and operations to ensure seamless application integration.
- Data storage and management: Capable of storing, indexing, and querying JSON-like, document-based data efficiently.
- Scalability: Support easy scaling of storage and computing resources without any upfront planning.
- Security: Robust security features like encryption at rest and in transit, network isolation using VPCs, and identity and access management controls.
- Backup and recovery: Automatic backup and point-in-time recovery features are required.
Performance​
- Availability: Offer multi-AZ deployments for high availability and fault tolerance.
- Durability: Data storage should be durable and reliable, with minimal risk of data loss even in failure scenarios.
- Throughput: Capable of handling high read and write throughputs, scaling dynamically with workload demands.
- Latency: Provide low-latency responses to database queries, even under high load.
System requirements​
Establishing minimum software and hardware requirements is important to mitigate risks, such as security vulnerabilities, performance issues, or compatibility problems, and to ensure that the SOUP functions effectively within the intended environment.
Software​
After evaluation, we find that there are no specific software requirements for this SOUP. It works properly on standard computing devices, which includes our environment.
Hardware​
After evaluation, we find that there are no specific hardware requirements for this SOUP. It works properly on standard computing devices, which includes our environment.
Documentation​
The official SOUP documentation can be found at Amazon DocumentDB Documentation.
Additionally, a criterion for validating the SOUP is that all the items of the following checklist are satisfied:
- The vendor maintains clear and comprehensive documentation of the SOUP describing its functional capabilities, user guidelines, and tutorials, which facilitates learning and rapid adoption.
- The documentation for the SOUP is regularly updated and clearly outlines every feature utilised by the medical device, doing so for all integrated versions of the SOUP.
Related software items​
We catalog the interconnections between the microservices within our software architecture and the specific versions of the SOUP they utilise. This mapping ensures clarity and traceability, facilitating both the understanding of the system's dependencies and the management of SOUP components.
Although the title of the section mentions software items, the relationship with SOUP versions has been established with microservices (also considered software items, by the way) because each one is inside a different Docker container and, therefore, has its own isolated runtime environment.
| SOUP version | Software item(s) |
|---|---|
| N/A | WEB API GATEWAY |
Related risks​
The following are risks applicable to this SOUP from the table found in document R-TF-013-002 Risk management record_2023_001:
- 58. SOUP presents an anomaly that makes it incompatible with other SOUPs or with software elements of the device.
- 59. SOUP is not being maintained nor regularly patched.
- 60. SOUP presents cybersecurity vulnerabilities.
Lists of published anomalies​
The incidents, anomalies, known issues or changes between versions for this SOUP can be found at:
History of evaluation of SOUP anomalies​
04 Mar 2024​
- Reviewer of the anomalies: Alejandro Carmena Magro
- Version(s) of the SOUP reviewed: N/A
No anomalies have been found.
Record signature meaning​
- Author: JD-004
- Reviewer: JD-003
- Approver: JD-005