Teri Radichel
jt7dI wish there was a CloudWatch metric for Lambda per-function network traffic. #AWSWishList
Andreas WittigMy feature wish for re:Invent 2025: a VPC endpoint that enables access to all AWS services at once.
But I suspect that profit is being optimized here rather than customer wishes being fulfilled.
The AWS Community celebrates the release of AWS Capabilities by Region, an overview of the service and feature availability by region.
But that's not what customers asked for. At least, not me.
I'm asking to close the gaps between regions instead. The current situation creates unnecessary complexity.
Focus on rolling out all services and features to all regions, please. That's the customer-centric approach here.
Something on my #AWSWishList: brownout as a service. I'd like to be able to inactivate a thing without otherwise hurting it, across many services. Then emit a Health event for "inactivated thing <service>.<instance> tried to do something". Then I could automate lengthening brownouts to verify it's unused before reporting it's OK to terminate. But it'd need tiny changes to many resource types in many services, so I suppose unlikely.
If I’m in the US and have all but two regions denied in my SCPs I don’t want the console trying to connect to Asia, Africa, Europe, Canada, and Latin America every time I open it. Also Adobe. AWS in my current region only, please. #awswishlist
AWS console needs to support longer TXT records for DKIM 2048. #awswishlist
Amazon Q in console needs a stop button. #awswishlist
Is something in a remote AWS account is trying to use my customer managed KMS key I want to see that in my logs in the account where the KMS key exists.
#awswishlist
#awswishlist
I want to use my customer-managed prefix list in IAM policy sourceIP conditions in IAM policies, trust policies, and resource policies so I can update my prefix list and then access all the things from my IP after that one change. #awswishlist
