And there I was, stopped in my tracks by a red error message: "Endpoint needs to be in full URL form".
How did I get here? We've got to go back. Way back... about 10 entire minutes....
"I'm totally using the new Named Credentials for my new setup of Event Relays to AWS EventBridge. It's the way of the future!" I said eagerly.
After following the docs here on External Credentials for AWS, I found nothing about the URL for AWS. Back to the Event Relays doc, I saw only Legacy Named Credentials in the documentation.
"No, it'll be fine" I say to myself, and read:
"For URL, enter a URL in the format arn:aws:aws_region:aws_account_number. Replace the aws_region placeholder with your AWS region. Replace the aws_account_number placeholder with your 12-digit AWS account ID. The URL is case-sensitive, and aws_region is in capital letters. For example, the URL for an account in the US-WEST-2 region has this format: arn:aws:US-WEST-2:XXXXXXXXXXXX. (XXXXXXXXXXXX is a placeholder for the 12-digit AWS account ID.)"
I checked the Named Credential I used for my first AWS EventBridge integration to a different AWS account, and it matched. Confidently I entered the appropriate value (Account # changed in the screenshot for this post):
I clicked Save ready to celebrate quick success. And my hopes were dashed - shattered like a piece of cheap china tossed carelessly onto a tile floor.
The heartless words stare back at me still: "Endpoint needs to be in full URL form"
I know this works with Legacy Named Creds - is the arn:aws URL format no longer supported with new Named Credentials?
Hey @Jonathan Green, Event Relay only works with Legacy Named Credentials right now, which is definitely buried in the Named Credentials UI these days. If it helps, @Ross Belmont and I are fleshing out New Named Credentials support right now and we're hoping to have a POC to show you and other interested folks in a few months. We're going into Spring '25 Planning now and can update you when we have timelines nailed down a little more.
