Amazon connection default naming convention

Integration Apps
1

Mostly looking for support or solutions to our issue. Not a huge issue as there is a tedious workaround, but it is still annoying.

When adding accounts in the Amazon - NetSuite Integrator App, the Default and un-editable name is “Amazon Connection”. This is rather annoying as we are growing to hit multiple markets for all the regions, .eu, .na, .fe.

The work around is to set up these accounts using the default names, which cannot be deleted later, then creating custom connections within the IA, example being “Amazon Connection Italy”, and then migrating all of the flows created through making the Italy account to the new custom connection.
The reason for wanting these Unique connection names is to follow a Standard for logging and auditing our account.

Curious how many others have run into this issue and if you have found a better solution, please let me know. We just don’t want 10 default connections in our list that don’t get used and can’t be deleted.

2

Hi Kenny,

Thank you for reaching out here in Celigo Connective.

I checked this internally, and it appears that the workaround used by other customers is the same approach you mentioned, creating custom connections within the Integration App so they can assign unique connection names.

To clarify why the original connection cannot be renamed:
When the Amazon–NetSuite Integration App is installed, Celigo automatically creates the connection and binds it to dozens of prebuilt flows, hooks, linked resources, and Integration App settings.

The system uses the connection name as a reference key across several internal configurations, including:

  • Default connection assignments within prebuilt flows

  • Hard-linked Integration App settings (imports, exports, lookups)

  • Integration App–managed resources that expect the original name

  • App patch/upgrade processes that rely on the default connection name

Renaming the connection manually would not update those internal references, which can lead to issues such as:

:cross_mark: Potential Side Effects

  • Flows showing “connection not found”

  • Imports/exports reverting to “No connection selected”

  • Errors during Integration App upgrades

  • Internal resources failing to locate the connection

  • Support needing to repair Integration App resources using backend tools

For these reasons, Celigo strongly discourages renaming system-generated Integration App connections.

I hope this helps clarify the behavior. Please feel free to reach out if you have any further questions or concerns.

1 Like
3

Hello Aaron,

Thanks for the response. This doesn’t really clarify things though.

I am not talking about any connections that are set up when the Integration App in installed. I am specifically talking about when you add a new account, like Japan to your IA.

You started with agreeing that the work around I mentioned is a good course of action, but then followed it up with changing the Connections cannot happen as so much is tied to them. Maybe we are using the word Connection to mean different things. I would essentially be moving all Flows created by adding that new Account to a different connection than the Default one created. So I would essentially be making that default Connection useless.

If so much is tied to this, and it is not being used, how does the work around work?

Unless you mean that the default connections are still working somehow in the background and that is why they cannot be deleted. If this is the case, then why wouldn’t it be part of the process to create Unique name connections by default to begin with? Celigo is essentially forcing bad practice with naming convention.

4

Hi Kenny,

Thank you for reaching out. At the moment, our integration app does not support changing the connection name. That said, your request is a valid use case from a user experience perspective, and we will review it further to determine whether it can be included as a future enhancement.

For now, the best approach is to replace the default connection that is created automatically when a new store is installed with a custom connection that you set up. The default connection is required to remain in the app because it is created as part of the installation process, but it will not impact your flows or the overall functionality of the integration app. Everything will continue to work as expected when you use your custom connection instead.

Please feel free to let me know if you have any other questions or if there is anything else I can help clarify. We appreciate the feedback and will continue evaluating this option as we explore additional use cases.

Thank you.

1 Like