How do I send feedback to AWS?

Can there be a feature added to Amazon SES SMTP credentials to generate credentials similar to what we get with gmail or outlook. I.e. Email + password. Gmail: Host: smtp.gmail.com Post: 587 User Name: a.b@gmail.com Password: ********* Office 365: Host: smtp.office365.com Post: 587 User Name: a.b@xyz.com Password: *********

There are some services that use the interface that mandates to enter email + password. There we would not be able to use Access Key + Secret generated as SMTP credentials.

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

Is there a way to synchronise load balancer instances for automatic updates of WordPress plugins across instances simultaneously?

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

I would like to add custom actions in the menus of EC2 Web Console: is it possible ? For example, the user could select an EC2 instance and then could trigger a custom-action (probably implemented as a Lambda function). It would be a nice feature ;-)

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

I tried to "submit feedback" in the AWS console about a CORS issue in the new API gateway UI and guess what... I can't submit the feedback because of a CORS issue 🤯😂

The form has an error with "Something went wrong. Please submit your feedback again later."

Access to XMLHttpRequest at 'https://console.aws.amazon.com/aperture/feedback/submit' from origin 'https://eu-central-1.console.aws.amazon.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

AWS you really need to fix this. Because if people cannot send feedback, how do you know if something isn't working?

Here is the original issue that led me to sending feedback...

The new API gateway UI has a bug regarding "Enable CORS".

When I add the default CORS configuration for the OPTIONS endpoint the API Gateway responds with "{"message": "Internal server error"}"

If I do the exactly the same configuration in the old UI it works.

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

Submit Feedback Error

From the AWS sign-in page, I click Enable new sign in, then click New sign in at the bottom, and click Provide feedback. I fill out the feedback form and receive an error:

Something went wrong. Please submit your feedback again later.

Addendum

For the record, my feedback was:

Hey folks, the new sign-in page forces me to re-select my account in Bitwarden when the password page loads. The old sign-in page allowed me to select my account once on the email entry page, and the password autofilled as the password page loaded nearly instantaneously. Feels like a downgrade for me. Thank you!

Also, I did follow instructions to "reach out to AWS Support" from the AWS Security Blog post "Upcoming improvements to your AWS sign-in experience". However, I see no relevant selection to choose when I browse support contact category options.

whom to write to if aws twitch videos are not playing for past episodes in many streams like security rampup and lets talk about data streams

Your new "plans" on CloudFront are sneaky. You don't realize that you're not on the pay-as-you go as CloudFront has always worked, and you can't cancel the plan you didn't want in the first place until the end of the month.

I'm stuck with a free plan for 27 more days while I'm more than willing to pay, and customer service isn't sure they'll be able to help me before the cut the service for exceeding my allowance.

It doesn't make any sense. I want to pay you for what CloudFront has always been for the past 10 years. Please, don't pull the plug on me and let me just give you my money?!