Le service Amazon Web Services est-il en panne ? Vérifiez les problèmes, le statut et les pannes actuelles

Publications Reddit - Aws

Score: 0 | Commentaires: 45

It's ok to not know what you're doing, as long as you recognize that and stay within your limitations until you gain understanding. Your best bet at this point is to delete the resources you created and find a clear tutorial and follow it exactly. Do not ask ChatGPT for help, you don't know enough to know where it's wrong.
Stop blindly using ChatGPT and read the documentation on what you are turning on/off before you actually do it. There are too many variables and not enough details in your post. - Does the docker container run locally where you can connect to it through localhost and port forwarding? - Did you launch the container in a public subnet? - Did you attach an internet gateway to your VPC? - Do you have an explicit allow for web tradfic on your security group? - What service (EC2 direct, ECS, EKS) did you use to launch your container? - Can you connect to the instance’s terminal and check instance state through AWS systems manager session manager?
Have you at least tried to read official AWS documentation? What you are saying doesnt make any sense, same for chatgpt...
I highly suggest that you stop using AWS. Your next post will be about how you accidentally spent $100,000.
Take some time to properly learn how things work. You’re gonna blow through your bills if you just turn on shit

Score: 0 | Commentaires: 18

SNS and SQS aren't really meant for end user notifications. One approach would be to store the status of the content into DynamoDB and have the client pulling the UI for a status update every second or so. A different approach that I've used is AppSync/GraphQL, as a user client can subscribe to notifications and AppSync handles keeping that connection open and sending them relevant events. Its been a while since I've done it, but now they've made an alternative path of instead of calling AppSync directly from your lambda... just push an event onto the EventBridge event bus and use their integration with AppSync. Going that approach would give you extra capabilities as you can attach multiple rules/targets to EventBridge events so if someone else needed to be notified, or a different process kicked off to do something about the content, it could all be handled there.
You can use api gateway’s websocket to notify a web app client from a lambda.
The managed solution to deliver events from Lambda without having any compute instances would be: 1. API Gateway Websockets 2. GraphQL subscriptions (AppSync) 3. AWS IoT Core 4. Polling from the client side
You could use websockets if it’s a live app or you could use a webhook

Score: 1 | Commentaires: 3

For a bunch of boring historical reasons, when you presign a S3 request, unless you're in one of a few special regions, you end up getting a URL against the us-east-1 endpoint, basically. Normally this is fine and the actual routing is hidden from you, but there is this comment on how [S3 handles routing](https://docs.aws.amazon.com/AmazonS3/latest/API/UsingRouting.html#:~:text=However%2C%20if%20the,resend%20the%20request.): > However, if the bucket is created in any other Region, any requests for the bucket go to the default endpoint while the bucket's DNS entry is propagated. The default endpoint redirects the request to the correct endpoint with an HTTP 302 response. Temporary redirects contain a URI to the correct facility, which you can use to immediately resend the request. In other words, while the bucket is still new, you'll see a redirect if you use the default endpoint, and that redirect doesn't have your CORS configuration, thus you get an error. Not that it matters a ton, since if the redirect did work, the signature check itself would fail since you're signed against the default endpoint, not the one you're being redirected to. The way to work around this is to explicitly use the target region endpoint in your presigned URL: s3 = boto3.client( 's3', region_name='eu-central-1', endpoint_url='https://s3.eu-central-1.amazonaws.com', ) # ... url = s3.generate_presigned_url( ClientMethod='put_object', Params={'Bucket': bucket_name, 'Key': key}, ExpiresIn=3600 ) This should have your bucket's configuration even on a freshly minted bucket.
Your cors policy is set correctly. I tested a few curl commands against it (I'd react that last 2 screenshots as you exposed it in the options request) It looks like the client likely isn't setting the "access-control-request-method" header to PUT value. Once I did this I got a successful 200 response.

Le statut actuel de Amazon Web Services est OPERATIONNEL

Aucun rapport indiquant que Amazon Web Services est en panne ou rencontre des problèmes de statut au cours des dernières 24 heures.

Si vous rencontrez des problèmes, veuillez les signaler !

Comment ça fonctionne ?

Statistiques de temps d'arrêt en temps réel pour Amazon Web Services au cours des dernières 24 heures

Carte des pannes en direct

Liens officiels pour Amazon Web Services

Rapports des utilisateurs

Derniers rapports

Discutez de l'état actuel de Amazon Web Services

Lisez-en plus sur Amazon Web Services

FAQ - Aws

Publications Reddit - Aws

Help. I fked up and now my ec2 instance not connecting. It shows that "unable to connect, check network config"

What's the best way to send from server to client?

CORS error on presigned URL for file upload