Skip to content
Database / Data warehouse

Amazon Lightsail and Snowflake integration

Plan how Amazon Lightsail and Snowflake should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

  • Scope your workflow with an integration engineer
  • Review the systems, records, and updates you need
Integration planning
stacksync.com
Amazon Lightsail
Snowflake
Review the integration scope

Built for teams where self-serve, reliability and scale matter

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Proposed workflow

Plan table mappings between Amazon Lightsail and Snowflake

This is an evaluation scenario; connector and operation support require confirmation.

Starting eventA selected source table needs an operational replica, a reporting projection, or a migration copy.

  1. Choose actual tables in Amazon Lightsail and Snowflake and compare their schemas and record types.

  2. Specify the primary/business key, type conversions, filter boundaries, relationship dependencies, and the source of each writable field.

  3. Choose a one-way copy or two-way sync according to connector support and your update rules. Keep source views, aggregate outputs, and writable base tables distinct.

What to verifyCounts reconcile within identical filters; updates preserve keys; precision, nulls, deletes, and schema changes follow the agreed mapping rules.

Review records and field ownership

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Choose the tables you need in Amazon Lightsail and Snowflake, then map their keys, field types, and filters. Your schemas determine how records relate and which system should own each field. Use the worksheet to document those choices before testing the first load.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

Amazon Lightsail

Connection and object support require review

Record types to review with Stacksync

Record typeCoverage and requirements
TablesConfirm support for this record type and the direction you need.
Managed DatabasesConfirm support for this record type and the direction you need.
DatabasesConfirm support for this record type and the direction you need.
View 3 more Amazon Lightsail record types
Record typeCoverage and requirements
SchemasConfirm support for this record type and the direction you need.
ViewsConfirm support for this record type and the direction you need.
Users and GrantsConfirm support for this record type and the direction you need.

Discuss Amazon Lightsail requirements

Snowflake

Read and write support varies by record

Record types covered in the setup guide

Record typeCoverage and requirements
Standard tables (including Permanent, Transient and Temporary tables)✅ Supported. Confirm field permissions and sync direction.
Views (including materialized and non-materialized views)🕘 Coming soon. Confirm field permissions and sync direction.
External tables❌ Not supported. Confirm field permissions and sync direction.

Read the Snowflake connector guide

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits
Connection requirementAmazon LightsailSnowflake
Integration interfaceMySQL or PostgreSQL wire protocol (SQL) to the managed database endpointSQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API
AuthenticationConfirm the credentials, API plan, and permissions required for Amazon Lightsail.Dedicated Snowflake service user + role with RSA key-pair authentication
Change detectionConfirm how Stacksync detects changes for this connector and the objects you need.The saved Stacksync guide does not specify the change-detection mechanism.
Read accessConfirm with StacksyncAvailable for supported records
Write accessConfirm with StacksyncAvailable for supported records

Enterprise controls

Security and control for your integrations

Access and connectivity

Use SSO and SCIM to manage access and secure connection options to reach your systems.

Explore security controls →

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide →

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

Amazon Lightsail
Integration interface
MySQL or PostgreSQL wire protocol (SQL) to the managed database endpoint
Authentication
Confirm the credentials, API plan, and permissions required for Amazon Lightsail.
Change detection
Confirm how Stacksync detects changes for this connector and the objects you need.
Read access
Confirm with Stacksync
Write access
Confirm with Stacksync
Setup requirements
  • Identify the Amazon Lightsail account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for Amazon Lightsail, including read/write support, authentication, and initial-load limits.
Limitations to check
  • Confirm Stacksync support for Amazon Lightsail and the record types your workflow needs.
  • Review write-back, deletion handling, update timing, and account limits with the integration team.
Snowflake
Integration interface
SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API
Authentication
Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles
Change detection
The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Have an administrator run the documented setup script for a dedicated service user and role with RSA key-pair authentication.
  • Specify the correct warehouse, database, schema, and account identifier. Verify table grants for the service role.
  • Existing tables need a non-null primary key with a UUID_STRING() default, as specified in the connector guide.
Limitations to check
  • The saved support matrix excludes external tables and marks materialized and ordinary views as not yet supported.
  • Geography and geometry fields are excluded by the saved connector guide.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Snowflake setup guide

Prepare Amazon Lightsail and Snowflake access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

Amazon Lightsail setup checklist
  • Identify the Amazon Lightsail account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for Amazon Lightsail, including read/write support, authentication, and initial-load limits.
Snowflake setup checklist
  • Have an administrator run the documented setup script for a dedicated service user and role with RSA key-pair authentication.
  • Specify the correct warehouse, database, schema, and account identifier. Verify table grants for the service role.
  • Existing tables need a non-null primary key with a UUID_STRING() default, as specified in the connector guide.

Setup guides: Authorize Snowflake

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the Amazon Lightsail and Snowflake planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Choose the tables you need in Amazon Lightsail and Snowflake, then map their keys, field types, and filters. Your schemas determine how records relate and which system should own each field. Use the worksheet to document those choices before testing the first load.

Compare integration approaches

Choose a method around one example record and the update your business needs. Define how the Amazon Lightsail source record should appear or trigger work in Snowflake. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit
Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility
Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose
Provide your table or object schemas and one example update; confirm the supported keys, fields, and direction.

Native vendor integration

Best fit
A vendor-built integration may fit if it supports your Amazon Lightsail and Snowflake record types.
Operating responsibility
Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose
First check whether either vendor offers this integration. If available, verify your record types, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit
Consider when Amazon Lightsail and Snowflake need a transformation, approval, or action outside a direct record sync.
Operating responsibility
Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose
Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.

File or scheduled snapshot

Best fit
Consider for a one-time Amazon Lightsail / Snowflake migration or a reporting need with an explicit freshness window.
Operating responsibility
Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose
Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Plan table mappings between Amazon Lightsail and Snowflake

Starting event: A selected source table needs an operational replica, a reporting projection, or a migration copy.

  1. Choose actual tables in Amazon Lightsail and Snowflake and compare their schemas and record types.
  2. Specify the primary/business key, type conversions, filter boundaries, relationship dependencies, and the source of each writable field.
  3. Choose a one-way copy or two-way sync according to connector support and your update rules. Keep source views, aggregate outputs, and writable base tables distinct.

Expected result: Counts reconcile within identical filters; updates preserve keys; precision, nulls, deletes, and schema changes follow the agreed mapping rules.

If it fails: Compare current source state, key mapping, and destination constraints before retrying. Reconcile the backlog after any schema or permission change.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Schema, keys, and reconciliation

Test case

Use an actual Amazon Lightsail and Snowflake table. Compare key uniqueness, nulls, decimal precision, timezone conversions, and counts within identical filters.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

A record type or update is unavailable

Investigate

Check the Amazon Lightsail and Snowflake connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between Amazon Lightsail and Snowflake

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Amazon Lightsail Snowflake Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Snowflake.

Snowflake Amazon Lightsail Direction requires confirmation

Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.

Apply updatesConfirm that Stacksync can create or update the records you need in Amazon Lightsail.

Update timing and record limits
  • Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
  • Review write-back, deletion handling, update timing, and account limits with the integration team.
FAQ

Amazon Lightsail and Snowflake integration FAQ

Next step

Plan your integration with an engineer

Walk through your Amazon Lightsail and Snowflake records, field mappings, and requirements with an integration engineer.

Talk to an engineer Explore plans and pricing

Further reading

Resources for your technical review