I just signed up to the forum for AWS using my console account. All good.
I go post for the first time and I get:
Your account is not ready for posting messages yet
I do not have an ad blocker so I have not found any other solutions to this. Any help is appreciated.
If this is a persistent problem, the solution is to open a ticket with support.
According to this document, this is to help reduce the amount of spam. New accounts accumulate the ability to post messages over time.
To limit spam posted to the AWS forums, the number of messages an account can post is limited. The number of messages an account can post steadily increases over time. Newly activated accounts might not be able to post any messages for a few hours.
Look here for more info.
I could posted my question in forum with in 1 hour.
Just wait for a while, approximately 30 mins. It's automatically solved.
Related
I'm working on a longitudinal research study where we need to re-survey the same set of Workers.
A complication: I'm doing this with a new MTurk Requester account, as access to the original one isn't readily available. Therefore the previous project & batch are not there. I'm making a new project.
I have the MTurk IDs for the past Workers though.
Will this be enough, or will I need to access the old MTurk Requester account? If it is enough, how can I do this?
So far, I attempted to import the Worker list, and set a qualification that only those workers could participant in this next HIT. But I'm not sure how I can notify those specific Workers that there is a follow-up intended for them.
Thanks for you help in advance.
You cannot contact workers who have not worked for you (on that requester account) previously.
What I would do if I were you would be to name the qualification something like "Follow-up HIT posted just for you please check it out http://shorturl.to/yourHIT". Turkers get an email when a qualification is granted, so this will notify them and they'll be curious enough to check it out.
If I didn't get enough Ps, I'd log into the old account and send a message to the workers through the API asking them to participate in the new HIT.
I am using Google Cloud for development and training of deep neural networks. I've reached the limits of what I can do with CPUs and now need to create and instance with one or more GPUs.
I've followed the instructions from multiple sources. As the instance was being created I received a notification that my quota for my region (us-west1) was zero and to request an increase.
I did so and received the confirmation email within minutes. However, when I then attempted to recreate the instance I was again met with the quota increase error.
I submitted another request (same region) but heard nothing.
I tried in a different region, again requesting a quota increase, but heard nothing. I did this 6 times and -- as you might have guessed -- neither received a confirmation email nor was I able to create my instance.
I tried the hack of using Chrome in Incognito mode, but no joy.
This was an issue a few months ago, at least judging from the S/O and Google forum posts. I would think that by now it would be fixed.
Any help would be much appreciated as I'm totally stuck
NB: Cross-posted to the gce-discussion forum
I think you should contact the Google Cloud Platform Support for this kind of issues.
Open a case asking why your quota increase has not been applied and I am sure they are going to solve this in some days or at least to tell you why your request was declined.
Notice that quoting from the official Documentation "Free Trial accounts do not receive GPU quota by default."
Disclaimer: I work for the Google Cloud Support.
I am receiving the following when I try to add new AWS accounts to my newly created organization. Any thoughts on how to tackle this problem?
Make sure that your account has a complete billing profile, including payment information. If that is the case, and you are still having issues, AWS support will be able to help you identify the issue.
If this error occurs, wait for few minutes and retry. If it comes again contact AWS support. They will fix the issue mostly in 24hours time.
There is a clear message on the top, that your organization is in initialization status. Because of that you should wait until it's done initializing (in some cases it could take about an hour) and try again. AWS Documentation states (see step #7. Create), that
If you get an error that indicates that you can't add an account
because your organization is still initializing, wait one hour and try
again.
Therefore there is no need to contact a support for this kind of problems.
It seems like api's are timing out when creating subscription for already existing topics. My tests which validate this was working until few minutes back but now they started failing. I am not even able to create subscription using Google's console either.
Though Google's dashboard shows service as working. Anyone else seeing this? I am not sure what else I can do to gather more info.
Yes, we had an issue with error rates higher than expected around that time. The users should have seen 504 errors during the outage. As of 1:30PM, the issue has been resolved, and everything should be back to normal. Sorry about the inconveniences.
We do have SLA. Cloud Pub/Sub SLA is described here:
https://cloud.google.com/pubsub/sla
If you think you're eligible, you can request a refund from that page.
Sorry again for the inconveniences you may have had.
Company credit card expiry passed and new expiry details needed putting onto AWS payment methods. Since then billing has failed. I am assuming its because CVS number is not taken by AWS and the bank are rejecting it. (The card has been used for many other things since to make payment so its active).
Is there another way to get around this as the bank won't allow to bypass it. I can't believe there arent any posts from others with similar issues as the payment methods for AWS are rather limiting.
Its ran seamless for a few years now until this happened and I can't get an answer out of ticket system on AWS.
Many thanks.
Its randomly started working again. Very strange.