AWS Migration

| The migration guide says to “review and update IP allowlists for login, API access, email sending, web tracking, and integrations.” Which of these updates need to be made within Marketo/Adobe, and which need to be handled by our company IT/Network/Security team?

They’re all done by your IT team.

| The guide also says to “add new IP addresses and keep your current IPs as-is.” Should the three new AWS IPs for our data center be added only to our corporate/network allowlists, or are there any specific locations in Marketo Admin/Adobe Admin Console where we need to add them?

Again these are done by your IT team, not in the Marketo UI.

| Is there a pre-migration validation/checklist that Adobe recommends to confirm that our IP allowlisting and integrations are ready before October 16?

Not that I’m aware of. It wouldn’t be possible for Adobe to know every place (firewall egress filters, internal proxy servers) where remote IPs appear.

I  After the migration, are there any post-migration validation steps we should perform to verify API access, web tracking, email delivery, and integrations are working correctly

Sure, send a tracked email and ensure clicks, opens, and pageviews appear in the activity log. Run a manual sync (if such a thing exists) for API integrations.

Knowing if inbound email was allowlisted may be difficult however (which is why I personally hate allowlisting!). That is, a Marketo email might come through regardless of the allowlist. You should coordinate with IT to look at their inbound mail logs.

|  For web tracking/Munchkin, does our website/Web team need to make any changes because of the AWS migration? If yes, could you please specify exactly what needs to be updated?

No.

Adding a few things Adobe Support confirmed for us that aren't in the migration guide, in case they help your Oct 16 planning.

On IPs, Support told us there are no changes to API URLs or credentials, and any allowlists configured inside Marketo carry over. So yes, it's all on your IT side.

The stuff that surprised us:

• Batch campaigns scheduled inside the window are skipped. They won't fire when service comes back, so you'll need to re-send manually.
• Inbound API calls fail with service-unavailable errors. Nothing is queued on Adobe's side, so your integrations need to retry.
• Outbound webhooks that would have fired during the window are dropped. No retry.
• Opens and clicks during the window aren't tracked. Unsubscribes are the exception (queued and processed after).
• SFDC sync and LaunchPoint pause and resume on their own.

On forms:

• Embedded form submissions are lost by default. If you send Support your Form IDs + Munchkin ID at least 2 business days ahead, they cache and replay them after migration. I'd send them a week ahead.
• Even with caching, the visitor still gets an error on submit. Marketo has no maintenance mode for this, so we built a time-gated GTM tag that hides form[id^="mktoForm"] and shows a "We'll be right back" message during the window. Happy to share the snippet.
• Marketo landing pages show Adobe's maintenance page.

One more thing. Ours got postponed the morning of, because data replication to AWS hadn't caught up. So plan your comms so you can roll everything back with a couple of Slack messages, and keep your GTM tag easy to pause.