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.

🚨Service Impact Warning

• Systems using Heroku endpoints after the following dates will stop functioning.
  • Sandboxes: March 5th, 2025 (Wednesday)
  • NEW EMEA and Select US customers: March 22, 2025 (Saturday)
  • NEW All US & APAC: March 29, 2025 (Saturday)
• Business operations dependent on CloudSense will be disrupted if you don’t complete the migration.
  
  

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 (you can check the Cloudsense Service Connectivity User Guide for guidance, and if you do not have this user guide, you can request it from Cloudsense).

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.com
    
    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.
• Identify all CloudSense endpoints currently in use throughout your Salesforce org. This includes Remote Site Settings, Custom Settings, Custom Metadata Types, JILE Options, Integration Endpoint or any configuration where endpoints are defined.

Note: You can leverage the ChatBot to ask it to identify and validate the New Endpoints. Example:

 3. Validate and Test

1. 🏗️ Starting January 9th, 2025, test the new endpoints thoroughly in your development environment.
2. ✅ Perform testing to ensure your integrations function as expected.
   
   

⏰ Timeline

Date	Event
January 9th, 2025	New AWS endpoints become available for initial testing
February 21st, 2025	AWS Sandboxes become available (REQUIRED testing phase)
March 1st – March 29th, 2025	CloudSense team monitors performance and stability on AWS Endpoints
March 5th 2025	Heroku endpoints are permanently decommissioned for Sandbox environments; no exceptions
March 22nd, 2025	Heroku endpoints are permanently decommissioned in EU Region; no exceptions
March 29th, 2025	Heroku endpoints are permanently decommissioned in US and APAC Regions; no exceptions

🛡️ Zero-Risk Migration Period

We have implemented a controlled migration strategy where all endpoints will remain functional in Production until

March 22nd, 2025 for EU Services in Production 

March 29, 2025 for APAC and US Services in Production 

March 5th, 2025 for Sandboxed in all Regions

This allows you to:

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

❓ WHY THIS MIGRATION MATTERS

• Mandatory Update: Every CloudSense customer must transition to AWS endpoints.
• Improved Performance: AWS-based endpoints offer faster response times, better scalability, and greater reliability.
• Prevent Outages: Any calls to Heroku endpoints -
  • in Sandboxes, after March 5th, 2025 9 AM UTC will fail
  • In Production, after March 22nd, 2025 for EU Services and March 29, 2025, for APAC and US Services will fail.

🆘 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 this communication by emailing our customer success team at CustomerSuccess@skyvera.com.
2. Plan your work to replace Heroku endpoints with AWS endpoints before the migration dates
3. Test thoroughly using the new endpoints.
4. Confirm migration success by emailing CustomerSuccess@skyvera.com.

List of endpoints with a custom or slightly different 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
cs-cfg-service-sandbox-sp20.herokuapp.com	cs-cfg-service-sp20-sandbox-eu-app.cloudsense.com
cs-orders-subs-prod-eu.herokuapp.com	cs-orders-subs-eu-app.cloudsense.com
cs-sm-sp20-cfgsp19-prod-eu.herokuapp.com	cs-sm-cfgsp19-sp20-eu-app.cloudsense.com
cs-sm-su20-cfgsp20-prod-eu.herokuapp.com	cs-sm-cfgsp20-su20-eu-app.cloudsense.com
cs-sol-mgmt-sandbox-su20-eu.herokuapp.com	cs-sol-mgmt-su20-sandbox-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
cs-sm-su20-cfgsp20-prod-us.herokuapp.com	cs-sm-cfgsp20-su20-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
cs-orders-subs-prod-sydney.herokuapp.com	cs-orders-subs-au-app.cloudsense.com
cs-sm-su20-cfgsp20-prod-apac.herokuapp.com	cs-sm-cfgsp20-su20-au-app.cloudsense.com

ℹ️FREQUENTLY ASKED QUESTIONS (FAQ)

1. Q: What if I miss the NEW deadline?
   A: You risk service interruption when Heroku endpoints are decommissioned on the dates listed. Contact our team immediately if you believe you cannot meet the deadline.

2. Q: Where do I find my existing Heroku endpoints?
   A: Review your Salesforce codebase and configurations (Remote Site Settings, Custom Settings, Custom Metadata Types, etc.) for references to “csherokuapp.com” or “cloudsense.com” hostnames. Use the chatbot to identify endpoint URLs.

3. Q: Will my API integrations break if I only switch the endpoints?
   A: The API structure remains unchanged, so only the URLs should need updating. However, always test thoroughly in your environment, preferably in a lower one first.

4. Q: Who should I contact if I need hands-on assistance?
   A: Email CustomerSuccess@skyvera.com to be connected with our Managed Services team for more in-depth support.

5. Q: Is there a fallback option after March 22nd, 2025 for EU Services and March 29, 2025 for APAC and US Services?
   A: No. After Heroku endpoints are decommissioned, rollback is not possible. It is essential to complete the migration on time.

6. Q: It looks like we only need to update the endpoints, does anything need to be done with the security certificates that were previously provisioned?
   A: No, certificates are stored in your Salesforce org and we only keep public keys in our services' database. This data stays the same during migration.

7. Q: How will I know if we updated all endpoints or if we skipped some?
   A: You can test the functionality and see if everything is working as expected:

   • for Solution Management - try to save the basket in the Solution Console

   • for Elastic - try to create a new order

   • for Media - try to check login on the Ad Server record, or try to refresh FI or perform availability check