CloudSense Endpoint Migration from Heroku to AWS

CloudSense is migrating its services from Heroku to AWS to enhance our platform's reliability and performance. This migration requires updates to the endpoints your systems use to communicate with CloudSense services.

 

What's Changing?

• Current endpoints: 
  • https://[servicename].herokuapp.com
  • https://[servicename].cloudsense.com
• New regional endpoint: 
  • North America:
    • https://[servicename]-us-app.cloudsense.com
  • Europe:
    • https://[servicename]-eu-app.cloudsense.com
  • Australia:
    • https://[servicename]-au-app.cloudsense.com

 

What You Need to Do

1. Review Your Integration

• Search your Salesforce codebase for any references to *cs*herokuapp.com or cloudsense.com (as there might be some Heroku apps with the custom hostname)
• Identify all CloudSense endpoints currently in use

 

2. Update Your Endpoints

• Replace the identified Heroku endpoints with the new regional endpoint depending on your location: 
  • North America: https://[servicename]-us-app.cloudsense.com
  • Europe: https://[servicename]-eu-app.cloudsense.com
  • Australia: https://[servicename]-au-app.cloudsense.co

Please note that certain endpoints that already had a custom hostname (https://[servicename].cloudsense.com) are slightly different and cannot be changed this way, so please find them listed at the end of this article.

• The API request and response formats remain unchanged
• Test the new endpoints starting January 9th, 2025
• The endpoints should be changed in Remote Site Settings, Custom Settings, Custom Metadata Types, etc, basically everywhere they are configured

 

Timeline

• January 9th, 2025: New endpoints available for testing
• February 16th, 2025: Heroku endpoints begin decommissioning

 

Zero-Risk Migration Period

We have implemented a controlled migration strategy where all endpoints will remain functional until February 16th, 2025. This allows you to:

• Test the new endpoints in your environment
• Validate your integration
• Rollback if needed during the migration period

 

Support and Assistance

• Our support team is ready to assist you with any questions
• If you would like assistance with this task via our Managed Services team, please contact: CustomerSuccess@skyvera.com and we will connect you with an expert.

 

Next Steps

1. Acknowledge receipt of this communication by contacting our customer success team at CustomerSuccess@skyvera.com  (we’ll keep following up until you do!)
2. Schedule your migration work before February 16th, 2025
3. Test your integration with the new endpoints
4. Confirm successful migration by emailing our customer success team at CustomerSuccess@skyvera.com

List of endpoints with a custom hostname (old > new):

EU

eu-prod-sp19-cfg-service.cloudsense.com	cs-cfg-service-eu-app.cloudsense.com
eu-prod-sp20-cfg-service.cloudsense.com	cs-cfg-service-sp20-eu-app.cloudsense.com
cs-digital-fulfilment-sandbox.cloudsense.com	cs-digital-fulfilment-sandbox-eu-app.cloudsense.com
eu.elastic.cloudsense.com	cs-elastic-eu-app.cloudsense.com
eu-int.elastic.cloudsense.com	cs-elastic-int-eu-app.cloudsense.com
messaging-api-eu.cloudsense.com	cs-messaging-dispatcher-eu-app.cloudsense.com
cs-pre-prod-eu.cloudsense.com	cs-pre-eu-app.cloudsense.com

US

us-prod-sp20-cfg-service.cloudsense.com	cs-cfg-service-sp20-us-app.cloudsense.com
sandbox.elastic.cloudsense.com	cs-ecommerce-sandbox-us-app.cloudsense.com
messaging-api-us.cloudsense.com	cs-messaging-dispatcher-us-app.cloudsense.com

APAC

apac-prod-sp20-cfg-service.cloudsense.com	cs-cfg-service-sp20-au-app.cloudsense.com
apac1.elastic.cloudsense.com	cs-elastic-au-app.cloudsense.com
apac1-int.elastic.cloudsense.com	cs-elastic-int-au-app.cloudsense.com
messaging-api-sydney.cloudsense.com	cs-messaging-dispatcher-au-app.cloudsense.com