Skip to content
Database / ERP

Amazon Lightsail and NetSuite integration

Plan how Amazon Lightsail and NetSuite 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
NetSuite
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

Customer reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving the proposed customer table in Amazon Lightsail or NetSuite Customer needs a defined result in the other system.

  1. Start with the proposed customer table in Amazon Lightsail and NetSuite Customer. Use the record-matching and field-ownership rules from your mapping worksheet.

  2. Resolve person or company type, legal entity, business role, and any billing account before transactions.

  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

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

Example record relationships between Amazon Lightsail and NetSuite
Amazon Lightsail recordNetSuite recordRecord matchingField ownership
Proposed customer tableProposed table; choose its name and schema.Reporting datasetCustomerDocumented record: Read: Supported. Write: Supported.Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Proposed customer invoice tableProposed table; choose its name and schema.Reporting datasetInvoiceDocumented record: SupportedRetain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.
Proposed supplier bill tableProposed table; choose its name and schema.Reporting datasetVendor BillDocumented record: SupportedRetain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

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 typesCoverage and requirements
  • Tables
  • Managed Databases
  • Databases
  • Schemas
  • Views
  • Users and Grants
Confirm support for this record type and the direction you need.

Discuss Amazon Lightsail requirements

NetSuite

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Customer
  • Contact
  • Nexus
  • Tax Type
  • Sales Tax Item
  • Billing Schedule Customer Subsidiary Relationship
  • Vendor
  • Vendor Category
  • Employee
  • Other Name Category
  • Vendor Subsidiary Relationship
  • Project
  • Project Status
  • Project Task
  • Job Type
  • Task
  • Partner
  • Customer Status
  • Phone Call
  • Support Case
  • Calendar Event
  • Note Type
  • Message
  • Job Status
Reading: ✅ Supported. Updating this object: ✅ Supported.
  • Invoice
  • Sales Order
  • Check
  • Credit Card Charge
  • Credit Card Refund
  • Credit Memo
  • Currency Revaluation
  • Customer Deposit
  • Customer Payment
  • Customer Refund
  • Deposit
  • Deposit Application
  • Estimate
  • Expense Report
  • Intercompany Journal Entry
  • Advanced Intercompany Journal Entry
  • Item Fulfillment
  • Item Receipt
  • Journal Entry
  • Opportunity
  • Purchase Order
  • Transfer
  • Vendor Bill
  • Vendor Credit
  • Vendor Payment
✅ Supported. Confirm field permissions and sync direction.
  • All custom objects
Reading: ✅ Supported. Updating this object: 🔓 Request Access.
  • Account
  • Accounting Period
  • Bin Transfer
  • Currency Rate
  • Price Level
  • Term
  • Subsidiary
  • Contact Category
  • Contact Role
  • Customer Category
  • Customer Message
  • Department
  • Expense Category
  • Classification
  • Location
Reading: ✅ Supported. Updating this object: 🕜 Coming soon.
  • Lead
  • Case
Reading: 🔓 Request Access. Updating this object: 🔓 Request Access.
  • Saved Searches
Reading: ✅ Supported. Updating this object: Read-only object.
  • Published Reports
Reading: 🔓 Request Access. Updating this object: Read-only object.

Read the NetSuite 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 LightsailNetSuite
Integration interfaceMySQL or PostgreSQL wire protocol (SQL) to the managed database endpointSuiteTalk REST and SOAP web services, plus SuiteQL queries
AuthenticationConfirm the credentials, API plan, and permissions required for Amazon Lightsail.Token-Based Authentication
Change detectionConfirm how Stacksync detects changes for this connector and the objects you need.Read and write support is documented by object; the source guide does not establish one change-detection method or frequency for every object.
Read accessConfirm with StacksyncAvailable for supported records
Write accessConfirm with StacksyncAvailable for supported records

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

  • SOC 2 Type II
  • ISO 27001
  • HIPAA BAA
  • GDPR
  • CCPA
  • DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

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.
NetSuite
Integration interface
SuiteTalk REST and SOAP web services, plus SuiteQL queries
Authentication
Token-Based Authentication (TBA): enable REST Web Services (and SOAP Web Services) + Token-Based Authentication in NetSuite, create an integration record to get Consumer ID/Secret
Change detection
Read and write support is documented by object; the source guide does not establish one change-detection method or frequency for every object.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Have a NetSuite administrator enable web services and token-based authentication, then create an integration record and access token.
  • Provide the account ID, consumer credentials, and token credentials through the Stacksync connection form. Check object-specific read and write access.
Limitations to check
  • Write coverage varies: the saved support matrix marks several accounting objects as Coming soon and custom-object writes as Request Access.
  • NetSuite Account is an accounting object; do not map it to a CRM Account merely because the names resemble each other.
Technical documentation

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

NetSuite setup guide

Prepare Amazon Lightsail and NetSuite 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.
NetSuite setup checklist
  • Have a NetSuite administrator enable web services and token-based authentication, then create an integration record and access token.
  • Provide the account ID, consumer credentials, and token credentials through the Stacksync connection form. Check object-specific read and write access.

Setup guides: Authorize NetSuite

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 NetSuite 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

Reporting dataset

Proposed customer table in Amazon Lightsail (choose its name) / Customer

Plan a customer dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Amazon Lightsail
Your database schema
NetSuite
Documented record · Read: ✅ Supported. Write: ✅ Supported.
Record identity
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership
Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

  • Source customer ID
  • Person/company classification
  • Legal entity or business unit
  • Destination identity reference
Record dependencies
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

References: NetSuite: Customer documentation

Reporting dataset

Proposed customer invoice table in Amazon Lightsail (choose its name) / Invoice

Plan a customer invoice dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Amazon Lightsail
Your database schema
NetSuite
Documented record · ✅ Supported
Record identity
Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
Field ownership
The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.

Fields to include

  • Source invoice ID
  • Customer or supplier reference
  • Line totals
  • Currency
  • Posting/payment status
Record dependencies
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Validation
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
Recovery
Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

References: NetSuite: Invoice documentation

Reporting dataset

Proposed supplier bill table in Amazon Lightsail (choose its name) / Vendor Bill

Plan a supplier bill dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Amazon Lightsail
Your database schema
NetSuite
Documented record · ✅ Supported
Record identity
Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
Field ownership
Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.

Fields to include

  • Source bill ID
  • Supplier reference
  • Entity
  • Line amounts and currency
  • Approval/posting state
Record dependencies
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Validation
Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
Recovery
Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

References: NetSuite: Vendor Bill documentation

Reporting dataset

Proposed sales order table in Amazon Lightsail (choose its name) / Sales Order

Plan a sales order dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Amazon Lightsail
Your database schema
NetSuite
Documented record · ✅ Supported
Record identity
Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
Field ownership
Decide which system approves the order and which can cancel or amend it after fulfillment begins.

Fields to include

  • Source order ID
  • Customer reference
  • Line references and quantities
  • Order status
  • Currency
Record dependencies
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Recovery
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

References: NetSuite: Sales Order documentation

Reporting dataset

Proposed payment or settlement table in Amazon Lightsail (choose its name) / Customer Payment

Plan a payment or settlement dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Amazon Lightsail
Your database schema
NetSuite
Documented record · ✅ Supported
Record identity
Preserve transaction ID, provider/source, currency, and links to invoices; one payment may settle several documents.
Field ownership
Keep payment authorization, settlement, and accounting allocation distinct.

Fields to include

  • Source transaction ID
  • Invoice references
  • Amount and currency
  • Settlement status
  • Reversal reference
Record dependencies
Resolve the affected invoices and cash/account references before allocating the payment.
Validation
Test partial payment, one-to-many allocation, refund, and repeated delivery of the same transaction.
Recovery
Look up the original transaction before retrying to prevent duplicate allocation or charging.

References: NetSuite: Customer Payment documentation

Reporting dataset

Proposed supplier or vendor table in Amazon Lightsail (choose its name) / Vendor

Plan a supplier or vendor dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Amazon Lightsail
Your database schema
NetSuite
Documented record · Read: ✅ Supported. Write: ✅ Supported.
Record identity
Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
Field ownership
Assign responsibility for approved supplier details; restrict changes to payment instructions to the business approval process.

Fields to include

  • Source supplier ID
  • Legal name
  • Entity reference
  • Payment terms
  • Active status
Record dependencies
Resolve business-unit and payment-term references before purchasing transactions.
Validation
Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
Recovery
Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.

References: NetSuite: Vendor documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Proposed customer table in Amazon Lightsail (choose its name) / Customer to review record matching and confirm Stacksync support for the required operations. 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
Check record matching: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit
A vendor-built integration may fit if it supports your Amazon Lightsail and NetSuite 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 Proposed customer table in Amazon Lightsail (choose its name) / Customer, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit
Consider when Amazon Lightsail and NetSuite 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. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit
Consider for a one-time Amazon Lightsail / NetSuite 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

Customer reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Proposed customer table in Amazon Lightsail (choose its name) or Customer record needs a defined result in the other system.

  1. Start with Amazon Lightsail Proposed customer table in Amazon Lightsail (choose its name) and NetSuite Customer. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve person or company type, legal entity, business role, and any billing account before transactions.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Customer invoice reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Proposed customer invoice table in Amazon Lightsail (choose its name) or Invoice record needs a defined result in the other system.

  1. Start with Amazon Lightsail Proposed customer invoice table in Amazon Lightsail (choose its name) and NetSuite Invoice. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

If it fails: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

Supplier bill reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Proposed supplier bill table in Amazon Lightsail (choose its name) or Vendor Bill record needs a defined result in the other system.

  1. Start with Amazon Lightsail Proposed supplier bill table in Amazon Lightsail (choose its name) and NetSuite Vendor Bill. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

If it fails: Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

Reconcile NetSuite business records with Amazon Lightsail

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

Starting event: A finance-owned record in NetSuite needs operational visibility through a selected destination dataset.

  1. Select Customer or Vendor with the correct legal entity, period, and currency.
  2. Define a reporting relationship in Amazon Lightsail; do not equate customer records, ledger accounts, and posted transactions.
  3. Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

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.

Proposed customer table in Amazon Lightsail (choose its name) / Customer

Test case

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Expected result

The expected customer relationship is preserved with no duplicate action or unintended write.

Proposed customer invoice table in Amazon Lightsail (choose its name) / Invoice

Test case

Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

Expected result

The expected customer invoice relationship is preserved with no duplicate action or unintended write.

Proposed supplier bill table in Amazon Lightsail (choose its name) / Vendor Bill

Test case

Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

Expected result

The expected supplier bill relationship is preserved with no duplicate action or unintended write.

Proposed sales order table in Amazon Lightsail (choose its name) / Sales Order

Test case

Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.

Expected result

The expected sales order relationship is preserved with no duplicate action or unintended write.

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.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

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.

Rejected or repeated customer change

Investigate

Inspect Amazon Lightsail Proposed customer table in Amazon Lightsail (choose its name) and NetSuite Customer, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated customer invoice change

Investigate

Inspect Amazon Lightsail Proposed customer invoice table in Amazon Lightsail (choose its name) and NetSuite Invoice, their IDs, and the destination error.

Next action

Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

Rejected or repeated supplier bill change

Investigate

Inspect Amazon Lightsail Proposed supplier bill table in Amazon Lightsail (choose its name) and NetSuite Vendor Bill, their IDs, and the destination error.

Next action

Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

A record type or update is unavailable

Investigate

Check the Amazon Lightsail and NetSuite 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 NetSuite

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 NetSuite 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 NetSuite.

NetSuite Amazon Lightsail Direction requires confirmation

Detect changesRead and write support is documented by object; the source guide does not establish one change-detection method or frequency for every object.

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 NetSuite integration FAQ

Further reading

Resources for your technical review

Next step

Plan your integration with an engineer

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

Talk to an engineer Explore plans and pricing