Choose the AWS region before offering an Oracle database through PD AWS Oracle. The region affects application latency, available instance classes and engine versions, and the network in which AWS creates the database.

Set the intended region

1. Identify where the application using Oracle will run.
2. Open the package’s Module tab and review Region.
3. Keep Backing service set to Amazon RDS.
4. Review the plan, engine version and storage for that region.
5. Save, then review the customer’s accepted choices before provisioning.

Locating the database near the application can reduce network delay. A region shown in a selector does not establish that every plan and version is orderable there for your AWS account. Also check the required VPC, subnets and permissions before creating a service.

Check choices as well as defaults

Review the region saved on the package. If your installation offers additional customer choices, check the actual accepted service configuration too; do not assume another platform’s option-generation instructions apply.

The module-panel connection test uses its own default region and the first active account. Passing it does not prove the account can create the requested database in this region.

Plan a move separately

Editing a package’s Region field does not migrate the data of an existing RDS database. For an existing service, keep the original resource and working application connection intact while the AWS administrator plans a destination, data transfer and cutover. Record the source and intended destination separately and establish how the moved database will be managed before changing the original service or retiring its database. Editing a default is not a migration or an instruction to attach a different resource.

See the PD AWS Oracle Blesta guide for related tasks, or explore PD AWS Oracle.