Unable to configure AWS integration with Maximizer

  • 1
  • Problem
  • Updated 2 months ago
Maximizer Live with AWS:

Unable to setup AWS integration with MaxLive

Walked through the process of setting up an AWS account.  Result is the following key ID and secrent.


Secret access key: Z5RQ9SWieOkI+EqNTWdKdV6iX4DDXMMTjEkWh71M

bucket name: wintec1

Region: us-east-1

Endpoint for US East (n. va): apigateway.us-east-1.amazonaws.com

We attempted to use both the Region value and the Endpoint value.

When using Region value we got this error.

The result of the integration installation:
Failed to process:Object reference not set to an instance of an object. at AppStore.Controllers.MidwareAMZS3Controller.Process(String maxToken, String webAPIURLRequest, String customerId, Int32 appInstanceId, Int32 enableLogRecordId, String userId) in C:\Build15\MX\AppStore - Main\Sources\AppStore\AppStore\Controllers\Midware\MidwareAMZS3Controller.cs:line 73

When using the Endpoint value we got this error.

Integration installation error:
Failed to process API credentials:The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.GetResponse() at AppStore.Core.WebApiClient.CreatePutHttpResponse(String url, String cotentType, Dictionary`2 headers, String data) in C:\Build15\MX\AppStore - Main\Sources\AppStore\AppStore\Utility\WebApiClient.cs:line 145 at AppStore.Core.CEConfigAMZS3.UpdateAppInstance(Int32 instanceId, String code, String customerId, String userId) in C:\Build15\MX\AppStore - Main\Sources\AppStore\AppStore\Core\CEConfigAMZS3.cs:line 61 at AppStore.Core.CEConfig.StartAppInstance(String shortName, String code, String customerId, String userId) in C:\Build15\MX\AppStore - Main\Sources\AppStore\AppStore\Core\CEConfig.cs:line 651 at AppStore.Controllers.MidwareCEController.ApiCredential(ApiCredentialViewModel model) in C:\Build15\MX\AppStore - Main\Sources\AppStore\AppStore\Controllers\Midware\MidwareCEController.cs:line 280

In neither instance is AWS connecting.  I think the instructions may be off or something else is wrong with how we implemented it.

Photo of Jonathan Arancio

Jonathan Arancio

  • 63 Posts
  • 0 Reply Likes

Posted 3 months ago

  • 1
Photo of Jonathan Arancio

Jonathan Arancio

  • 63 Posts
  • 0 Reply Likes
No response ?
Photo of Jonathan Arancio

Jonathan Arancio

  • 63 Posts
  • 0 Reply Likes
MSI solution:

The key/secret you provided doesn’t exist in your amazon account. That’s the reason why the authentication fails. Moreover, using the old “user” denies access to the bucket.


We created a new user “maximizerintegration1” and generated the new key/secret, which passed the test. Please use the following info to pass through the authentication:


Access key ID:  AKIA*********************

Secret access key: Ymmjye**********************************

bucket name: wintec2

Region: us-east-2

Photo of Anant Mahrok

Anant Mahrok, Product Manager - Integrations

  • 5 Posts
  • 1 Reply Like
Thanks for adding the provided solution Jon. Let us know if you experience any further issues.