To set up instance principals so an application running on an instance can call OCI public services without user credentials, you need to create a dynamic group with matching rules to specify which instances are allowed to make API calls, create policies granting permissions to the dynamic group to access services, and deploy the application and SDK to all instances in the dynamic group. Generating Auth Tokens is not necessary for this setup as those are typically used for third-party applications or scenarios where dynamic groups and instance authentication are not possible.
To authenticate to Oracle Cloud Infrastructure (OCI) API endpoints without accessing the OCI console, you should use an API signing key and an auth token. An API signing key allows programmatic access to API requests, while an auth token is a uniquely generated token used for API authentication purposes. Both methods bypass the need for console login credentials, making them suitable for this requirement.
To meet the requirement of securely storing patient health records for a period of five years without modification, overwriting, or deletion, you should create an OCI Object Storage time-bound Retention Rule on the HealthRecords bucket for five years and enable Retention Rule Lock on this bucket. This ensures that the records cannot be altered or deleted during the specified retention period, complying with regulatory requirements.
The two components that cannot be deleted in your Oracle Cloud Infrastructure Virtual Cloud Network are the default security list and the default route table. When a VCN is created, it automatically includes a default security list and a default route table. These components are integral to the functioning of the VCN and are therefore not deletable. Other components like the service gateway, routing gateway, and subnet can be managed and deleted as needed based on the user’s configuration requirements.
To ensure high availability, fault tolerance, and data durability even in the event of an outage in one availability domain or a complete region, the architect should create a replication policy to send data to a different bucket in another Oracle Cloud Infrastructure region. This approach provides continuous data synchronization across regions, protecting against regional failures and ensuring that the data remains accessible and durable without costly service disruptions.