Is Amazon Web Services down?

@AWSSupport The problem isn’t the notification, it’s the pipeline “failing” because Pipeline’s isn’t smart enough to see that an instance was already terminated by auto scaling. It “fails” because Pipelines can’t terminate an already terminated instance

@AWSSupport Thanks for getting back so fast. I believe I meet the requirements and I have the permission added but I still get the error “bucket_properties_acceleration_configuration_error” where it tells me the admin needs to add permissions... I am the admin

@AWSSupport is there an issue on AWS? Trying to add S3 Transfer Acceleration and it says I don’t have permission. I can see the permission in both my Root and IAM listings. Any workarounds? Need to upload large volumes of files and standard upload is slow

@cloudoption $PLTR doesn't control the market. The company doesn't care what it's share price is short term. They just announced a partnership with Amazon AWS today, but the market is crashing. Am in at $10, adding on the way down, and will have my day in the sun when things turn around.

Glue ETL / Glue Studio seems to not work with Glue tables that use Partition Projection; has anyone experienced similar issues? @awscloud

@saykay @Rackspace I mean, @awscloud tried to once but missed and hit "Follow" instead. They're still probably trying to work out the best way to unwind it without causing A Problem.

@zersiax @marcysutton @AWSSupport Hopefully, they fix this stuff.

@honnibal @spacy_io @awscloud Error 320 times

@honnibal @spacy_io @awscloud There are 640 cores and the model loads only 330 times. Peanuts. 100ms/doc is the problem. I see it producing records, it is just slow. I excluded all but 3 components.

@honnibal @spacy_io @awscloud No, you're mistaken. The Doc processing rate is incredibly slow. Model load times 32 times per node per job is not a large portion. I load once perpartition. Performance indicate about 100ms/Doc per core.

@markuslindqv @AWSSupport Hey Markus, did you ever figure out what the issue was with this? I'm getting the same when attempting to import a Lambda into GG?

@coudron @AWSSupport Been there. Almost shut down my entire account to start from square one. Turned out the billing dashboard was the easiest way to hunt down rogue resources. I’d then continue to delete (on repeat) until it no longer complained about dependencies.

@dblooman @awscloud Sure thing glad to help! I'm going to chat with some of the folks in the ECS devx team. We have been looking at places where we should contribute to Terraform to make it better, and this looks like a place where it needs a fix

@AWSSupport Thanks for the quick response. I was able to fill out this form. However, even this form has a11y issues. As I was typing in the comments field, the number of characters remaining kept dynamically updating, causing my screen reader to chatter incessantly.

@dblooman @awscloud Okay so that would be a Terraform specific integration issue. If you look at CloudFormation for example the `CapacityProviderStrategy` property does not require replacement, so there is no reason why Terraform should be requiring a replacement there.

@honnibal @spacy_io @awscloud The transformer model works well to detect names here, that isn’t a problem. It works even without context.

@AWSSupport A bunch of my resources are stuck in a dependency circle. Can’t delete network interfaces because they’re attached to a device. Can’t detach other devices because something is using them. Might be multi-zone issue.

@honnibal @spacy_io @awscloud According to the 684/sec word rate, it should have finished in 10 minutes. It already ran for 8 hours when I just restarted it excluding components. Any idea what a good rate is per doc created? I know from watching it the rate is slow.

When I started working with @honeycombio, @lizthegrey gave me the exploded billing page view. Me: "Yeah, I see what to fix first." Liz: "We haven't shown you our architecture yet!" Me: "Reading the @awscloud bill and drawing the arch is the world's weirdest party trick."

First let's talk about risk. And let's talk about the specific expensive problem I solve: the @awscloud bill. At the Duckbill Group what we deliver is advice, usually in the form of reports, presentations, or (whenever @mike_julian can't cut my power in time) interpretive dance.

@awscloud I don’t get why you need to recreate a ECS service if you want to change the capacity requirements for a service. If i want to use more fargate spot instances down the line, it becomes tricky when using something like terraform #ecs #fargate

@TysonTrautmann @awscloud If you see peers complaining they are having a horrible day due to harassment and say nothing, you're part of the problem. I know Ali personally and am more than happy to support her

@AWSSupport Fix your form first, it's ending with a CORS error at the moment

@LARosen @wimremes The good news is that @awscloud takes security very seriously. With everything I tried, they would not reset the account. It was a perfect storm of errors. There were lots of lessons learned, postmortem done. And it won’t happen again.

@AWSSupport This is a lie. We’ve been very clear about the issues with support and you are not looking to improve, nor are you looking to do right by small businesses when you mess up.

@peter_szilagyi @awscloud Also, I believe the team is now fixing the release. Again, I apologize. I think the intent was "Ethereum is even 'awesomer' as a managed service." But the delivery was wrong. We sometimes make mistakes, but I do know the team meant well. Thanks for calling out the error

When @awscloud Backup released Backup Metrics, I cracked that "too bad they don't ship Restore Metrics." Welp, it turns out they do! And they were FAST to request that I clarify that for customers, which I had no problem doing. I'm wrong from time to time! This stuff is hard!

@DropboxSupport It did not work for like one-two minutes. And also @Twitter appeared not to work so this is why I was considering some @awscloud outage or something.

@AWSSupport The documentation hasn't helped in clarifying my doubt. Let me raise the issue in the forums.

@AWSSupport fraudulent activity has been committed on my account. I submitted a support request via your Support page by selecting the option that I couldn't login and providing my email address, but I didn't get an email to confirm the creation of the ticket. Cause for concern?