All integrationsDatabases

Amazon RDS

Run your Amazon RDS databases from a workflow: create PostgreSQL, MySQL, MariaDB and SQL Server Express instances, stop them overnight and start them in the morning, take and restore snapshots, change their settings, and read their events and log files.

actions
20
trigger
1

Triggers

Start a workflow when something happens in Amazon RDS.

  • DB instance eventRuns when Amazon RDS records an event for a DB instance, such as the instance being stopped, started or restarted, failing over, being backed up or running low on storage. Watch every instance in the connection's region or one instance, and every kind of event or one category. Events from before the workflow is turned on don't start it. How often it checks follows your workspace plan.

Actions

Steps a workflow can run in Amazon RDS.

  • List DB instancesList the DB instances in the connected region, one page at a time, optionally only those of one engine.
  • Get a DB instanceGet one DB instance: its status, endpoint to connect to, size, settings and any changes waiting to be applied.
  • Create a DB instanceCreate a DB instance. It takes 5 to 15 minutes to become available; 'Get a DB instance' shows its status. The defaults (db.t4g.micro, 20 GiB gp2, Single-AZ) are what the AWS Free plan covers. It uses the region's default VPC.
  • Modify a DB instanceChange an instance's settings. Only the fields filled in, and the choices not left unchanged, are sent. Without 'Apply immediately' most changes wait for the weekly maintenance window; a class or storage change can restart the instance.
  • Delete a DB instanceDelete a DB instance. A final snapshot is taken first unless you skip it; without one the data is gone. Refused while deletion protection is on.
  • Start a DB instanceStart a stopped DB instance. It takes a few minutes to become available.
  • Stop a DB instanceStop an available DB instance so it stops accruing instance hours (storage is still billed). AWS starts it again by itself after 7 days. Not for Aurora.
  • Reboot a DB instanceRestart the database engine, for example to apply a parameter change. The instance is unavailable for a minute or so.
  • List DB snapshotsList DB snapshots in the region: all of them, one instance's, or one snapshot by name.
  • Create a DB snapshotTake a manual snapshot of an available instance. It is kept until deleted, and takes a few minutes to become available.
  • Delete a DB snapshotPermanently delete a manual snapshot. Automated snapshots cannot be deleted; they expire with the backup retention period.
  • Restore from a snapshotCreate a new DB instance from a snapshot, keeping the snapshot. The new instance is a separate, billed instance and takes 5 to 15 minutes to become available.
  • List eventsList RDS events such as restarts, backups, failovers and configuration changes. RDS keeps 14 days; with no times given it returns the last hour.
  • List log filesList a DB instance's database log files, with size and last write.
  • Read a log fileRead part of a log file, up to 1 MB. With nothing else set it returns the newest lines; set Lines and Marker 0 to read from the start, then pass 'next_marker' on to read on.
  • List tagsList the tags on a DB instance or DB snapshot.
  • Add tagsAdd tags to a DB instance or DB snapshot. A tag whose name already exists is overwritten; other tags are kept.
  • Remove tagsRemove tags, by name, from a DB instance or DB snapshot.
  • List engine versionsList the engine versions RDS offers in this region, or only each engine's default version.
  • List orderable instance classesList the instance classes that can be created in this region for an engine, one row per class, version and storage type. Set the version and class to check one combination.

Automate Amazon RDS with Lodol.

Connect Amazon RDS, then hand Lodol the job in Slack, Claude or ChatGPT.

Free plan, no credit card