The URL is visible from the Instances page, and you can also request a password reset from that page. But the username is not shown on that page.
I never got my the "Welcome to Splunk Cloud!" email, so I registered with a different email address, and that welcome got through. That included a username that worked on both instances.
You can try the cloud default usernames, like sc_admin, with the password sent in the password reset.
I've had the same problem with the Cloud Trial along with the Enterprise Security Trial Sandbox. Didn't get any confirmation email with links to the sandbox or cloud version. I have the free core Splunk on my pc, but wanted to try out the other trials for experience.
Check your registered email. You will definitely receive an email with subject “Welcome to Splunk Cloud!”
Where you will get URL, username , temporary password.
Splunk prompts you to change temporary password at first login. May be other users who are unable to access splunk cloud might have forgotten their password.
Did you ever figure this out?
I've already wasted enough time on this crappy onboarding UX...all the docs don't help, the splunk.com website hardly has any useful info and feels like a big upsell.
I hear good things about Splunk from my team but why is Splunk Cloud so painful?
I am also experiencing this issue. I created an account 2 days ago and have not been able to access the instance.
From the Instances page I click on the green Access Instance button and a new tab opens asking for user name and password. I enter the same credentials used to log into the free trial account but I just get Login failed.
Two months ago I created an account to test the Cloud instance, but I never received the credentials or the Welcome email, so the trial expired.
Two months later, I was hoping the problem was already fixed, but .... after creating the new account, with a different email, I find myself in the very same situation.
I'm unable to test the instance, I have received no credentials, and I'm also in urgent need of selecting the log aggregator to use in a really big Company.
It's a shame that is was unable to test it, because I had great expectations, and I'll obviously be recommending to use other alternatives, such as ELK (which I was able to test) or AWS/AZURE related services.
Hope you solve this issue as soon as possible, it's not helping.
I understand the frustration, but the issue may be partially due to the email provider blocking the messages. I also hope that Splunk will help identify the root cause and help fix this issue.
Have you tried resetting the password for your instance and using the username above?