Skip to content
Analytics & data warehouses

amazonaws.com:redshift

Amazon Redshift sandbox and mock API

<fullname>Amazon Redshift</fullname> <p> <b>Overview</b> </p> <p>This is an interface reference for Amazon Redshift. It contains documentation for one of the programming or command line interfaces you can use to manage Amazon Redshift clusters. Note that Amazon Redshift is asynchronous, which means that some interfaces may require techniques, such as polling or asynchronous callback handlers, to d Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
238
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-redshift.slurry.io/#Action=AcceptReservedNodeExchange \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2012-12-01.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 238.

  • GET/#Action=AcceptReservedNodeExchange
  • POST/#Action=AcceptReservedNodeExchange
  • GET/#Action=AddPartner
  • POST/#Action=AddPartner
  • GET/#Action=AssociateDataShareConsumer
  • POST/#Action=AssociateDataShareConsumer
  • GET/#Action=AuthorizeClusterSecurityGroupIngress
  • POST/#Action=AuthorizeClusterSecurityGroupIngress
  • GET/#Action=AuthorizeDataShare
  • POST/#Action=AuthorizeDataShare
  • GET/#Action=AuthorizeEndpointAccess
  • POST/#Action=AuthorizeEndpointAccess