How to integrate AWS with Bubble

You integrate AWS with Bubble by exposing an AWS service through an HTTPS API and calling it from Bubble using the API Connector. Bubble cannot install AWS SDKs, run Lambda directly, or use IAM keys inside code. Everything must be done through standard REST endpoints with authentication handled in the API Connector.

Most Common Working Setups

• API Gateway + Lambda: You create an HTTPS endpoint in API Gateway, attach a Lambda function, and Bubble calls that URL.
• S3: You normally avoid signed AWS auth in Bubble and instead use pre‑signed URLs generated by your backend (Lambda / API Gateway) so Bubble can upload/download safely.
• SES / SNS: You expose an HTTPS endpoint through API Gateway and trigger SES (email) or SNS (notifications) from Lambda.

How to set it up

The cleanest way is: API Gateway → Lambda → AWS Service → Bubble via API Connector.

• You create a Lambda function that does the AWS work (upload file, send email, run computation).
• You expose that Lambda through API Gateway as a public HTTPS endpoint.
• You configure the endpoint to require an API key or Bearer token.
• You plug that endpoint into Bubble’s API Connector.

Example: Bubble calling Lambda through API Gateway

// Lambda code example using Node.js
exports.handler = async (event) => {
  const name = event.queryStringParameters.name
  return {
    statusCode: 200,
    body: JSON.stringify({ message: "Hello " + name })
  }
}

// Example Bubble API Connector call
{
  "method": "GET",
  "url": "https://your-api.execute-api.us-east-1.amazonaws.com/prod/hello?name=test"
}

Important Bubble Concepts

• Backend workflows can also call AWS endpoints (good for server-to-server calls).
• Do not store raw AWS secret keys in Bubble pages; always keep them in API Connector private fields.
• Use pre‑signed S3 URLs if you need direct file uploads from users.