capabilities.work

Verify Engine Support Then Provision

A 3-step recipe with Amazon RDS. We can help you get access.

Recipe · 3 steps

Verify Engine Support Then Provision

with Amazon RDS · IT Infrastructure Management

Confirm an engine version is offered, then create and await a DB instance.

  1. Describe the available engine versions for the supplied engine and version to confirm the combination is offered before provisioning.
  2. Create the DB instance pinned to the validated engine and engine version with the supplied class, credentials and storage.
  3. Describe the DB instance and inspect its status. While the instance is still creating the workflow loops back to poll again; once it is available the flow ends.
What you'll need to have ready
  • dbInstanceIdentifier: The unique identifier for the new DB instance.
  • dbInstanceClass: The compute and memory capacity class (e.g. db.m5.large).
  • engine: The database engine to validate and provision.
  • engineVersion: The engine version to validate and pin on the new instance.
  • masterUsername: The name for the master database user.
  • masterUserPassword: The password for the master database user.
  • allocatedStorage: The storage to allocate in gibibytes (GiB).
For your developer

Arazzo workflow amazon-rds:verify-engine-then-provision, 3 operations: DescribeDBEngineVersions → CreateDBInstance → DescribeDBInstances. Specs on APIs.io.

More recipes with Amazon RDS

Add an Aurora Replica InstanceClean Up a DB SnapshotSnapshot and Rebuild a DB InstanceConvert Instance to Multi-AZDelete an Aurora DB ClusterEnable Backup RetentionModify a DB Instance ClassProvision an Aurora DB ClusterProvision a DB InstanceReboot a DB Instance