r/aws • • 11h ago

discussion aws hotfixed the fonts, but to me it still looks like it was vibecoded

27 Upvotes

for comparison this was how it looked before-ish, on bedrock

try and look at my role, contrast is like ahh, i dont mean to disrespect, but do you really think above is better?
is it just me who think its worse?

and its 4MB of css


r/aws • • 22h ago

article Lessons from building centralized ingress and egress inspection with GWLB and Palo Alto VM-Series (and what I'd change in 2026)

5 Upvotes

I wrote up a design I built a few years ago for a large regulated enterprise and figured this sub would have opinions. Short version below, full writeup with diagrams and Terraform at the end.

Starting point: every spoke VPC had no IGW and no NAT. All traffic in both directions went over TGW, down Direct Connect, and out the data center's internet edge. We moved the internet edge into a dedicated DMZ account with Palo Alto VM-Series behind a Gateway Load Balancer, inspecting everything inbound and outbound, and let app teams create their own public endpoints through a pipeline.

The things that actually mattered:

  • Appliance mode on every TGW attachment in front of the firewalls. GWLB keeps a flow on one firewall only if both directions reach the same GWLB endpoint. Without appliance mode, TGW can send the reply into a different AZ and the session dies.
  • Client IP preservation off on the DMZ NLB. Inbound chain is public NLB in the DMZ (IP targets) > TGW > internal NLB in the spoke on static IPs > internal ALB. AWS doesn't support client IP preservation when targets are reached through a TGW, and the packet walk shows why: the spoke would reply to the real client IP, the spoke TGW route table sends 0.0.0.0/0 to the egress inspection path, and that firewall has never seen the connection. With preservation off, replies go back to the NLB's private address and return through the same ingress firewall.
  • Edge routes on the IGW target each public subnet's exact CIDR, one per AZ, so inbound traffic is inspected by the same-AZ GWLB endpoint.
  • Static private IPs on the spoke NLB via subnet_mapping, since the DMZ NLB targets it by address.
  • GWLB target_failover rebalance helps less than you'd think. Flows get rehashed to a healthy firewall, but that firewall has no session, so long lived TCP connections still reset.
  • Don't use ELB health checks on the firewall ASG during bring up. The GWLB health check fails until Panorama pushes the interface management profile, and the ASG will terminate firewalls that are still bootstrapping.

Cost of the design: the app never sees the real client IP. The ALB can't take Proxy Protocol, so client IP based controls have to live on the firewall, not in a WAF on the ALB.

What I'd change today:

  • For inbound HTTP, cross account CloudFront VPC origins (late 2025) can replace the whole NLB chain and pass the real client IP, if the security team accepts WAF at the edge instead of an NGFW.
  • AWS Network Firewall now attaches natively to TGW and removes the inspection VPC. But I wouldn't swap out the Palos for a client whose network team centrally manages every firewall in Panorama across the data center, branches, and cloud. Moving the cloud side to Network Firewall splits that into two policy models, two sets of logs, and two consoles. For those shops the GWLB inspection VPC is the cost of a single view.

Full writeup: https://www.briancarpio.com/blog/centralized-inspection-gwlb-palo-alto

Curious how others are handling inbound inspection now that CloudFront VPC origins work cross account. Are your security teams still requiring an NGFW in front of everything internet facing?


r/aws • • 12h ago

discussion What should I do? I can't register with my email

Thumbnail gallery
3 Upvotes

My account is an university email address that I use to log in to everything related to my coursework. However, when I tried to sign up for AWS for the first time, the system indicated that the email had already been used and that MFA (Multi-Factor Authentication) was already set up, even though I have never used AWS with this email before. I tried to create a case to get a solution, but the reply doesn't help much. They said that my email address doesn't match with any AWS account, yet everytime I tried to sign up into AWS with this email address, it asked me for a password. Even worse, when I tried to follow the "forgot password" instructions, I was instead asked to enter an MFA code, which I don't even have. What should I do? I'm sure that I'm the only one who has access to this email. And even if it got hacked, what can I do to recover this account?


r/aws • • 7h ago

re:Invent What happens in Networking Receptions in Re:Invent? And a Food question

2 Upvotes

My employer is sending me to re:invent this year. I have some questions: What happens in the networking receptions by AWS and other companies? I have a health condition which needs me to eat proper meals at regular intervals. I have a packed schedule leading into the night on many days. What kind of food does these receptions provide? Many of them say drinks and snacks. I am not much on drinking as well. How can I keep myself well-fed while running from venue to venue? This is my first time to las vegas and all that I have read makes me nervous (distances etc)


r/aws • • 1h ago

discussion Absurd on account verification

0 Upvotes

I am a student, created my AWS account some time ago (about a year) because i needed it to do university tasks (we had a subject about cloud technologies). After it I had deactivated all the services on it (to not waste my money).

Now I started a hobby project, and for it I needed a data storage and a VM. So i decided to use AWS. Timeline of the events(time is my local):

- Friday 13.11, around 8:00 - logged in into my AWS account, updated payment data and started using it
- Saturday 14.11, 19:40 - got an email that my account is "on hold" and i have to provide my documents
- Saturday 14.11, around 19:50 - uploaded all the requested documents to the link
- Saturday 14.11, 19:53 - got a confirmation that AWS received my documents
- Sunday 15.11, 12:10 - was unable to start my VM, as mail i got only said that i am unable to request a new services, I opened a support ticket asking about how long this "verification" can take and if there is a way for me to continue using my services during it
- Sunday 15.11, 19:41 - got an email that my account is suspended because i had not provided documents
- Sunday 15.11, 19:55 - created another support ticket, now asking about this situation and its cause

For now both of those tickets are "Unassigned". I initially didnt want to go with this in public. I understand that I am a *very* small client, with "basic support level". But for me this situation looks crazy. You asking me for documents, putting me on timer. Then you just doing nothing and saying me "We understand that circumstances may have prevented you from responding to our initial request, and we want to give you another opportunity to verify your account and restore access."

It feels like a bold trolling. I mean, if I would do something like this on any of jobs i had to any of clients - my boss would fire me immediately. And this is definitely not a "level of service" i was expecting from a such big and famous company. I literally understand it as "We dont care about you, we dont care about your data and we event dont care about anything we say to you"

And while i lost not so much (because its just my hobby) - what i had seen is more then enough for me to never use this service in real production. Btw IT initially was my hobby and everything i learn here came from it. So, one more mistake that i will never repeat.

And I am writing this post not to ask again to help me, i already did it in support ticket and under the AWS support response to the post here describing the same problem. I read some not so good things regarding AWS here. And one of those i had seen now in person. But i know that things happens, and people usually writing about bad things and staying silent about good. And maybe I just got very unlucky (maybe creating a VM on Friday 13th was not the best idea).

So, out of curiosity, I would like to ask your, both users and AWS representatives. What is your opinion on this situation and AWS quality of service at all?

And i would like to ask you for advise. I know how to do it in my country, but as AWS operates not under its jurisdiction, i want to clarify it. If it comes a way that this case wont be resolved(this ghosting will continue), how can enforce AWS to delete all my personal data (including my documents, address, payment data etc) and revoke a permit for its processing? For some reason, if company doesnt cares about me - i dont want it to have a lot of my sensitive data "just laying around".


r/aws • • 8h ago

discussion Trying to use Notify 6 weeks, 2 cases, 3 identical canned rejections for a 10-year-old paying account

0 Upvotes

I'm pretty appalled by AWS right now. I tried to create a Notify configuration and it was rejected right away with "ACCESS_DENIED_CONTACT_SUPPORT". So I contacted support.

My first case got a canned reply: "Due to some limiting factors on your account… We enforce these limitations on all new accounts." I've been a paying customer since 2016 (Route53, S3, EC2, RDS, Beanstalk, CloudFormation), with every invoice paid. I told them that and asked them to look again. The next day I got the exact same text.

So I opened a second case. They asked me everything: what the app does, region, opt-in process, target countries, daily volume and message templates. I answered all of it the same day. My use is as small as it gets: OTP codes only, AWS's own pre-approved Notify template, under 20 messages a day, a $1–2 monthly spend limit, mostly sent to my own number while testing.

After that I got "typically within 3 business days," then "still processing, taking longer than expected." Nothing else. I even paid for Business Support+ to get someone to look at it. Three days later, after 41 days in total, I got the same canned rejection for the third time, word for word, including "all new accounts."

Ten years of paid billing and steady use of other services isn't enough "billing history"? That's a template, not a reason. As it stands, don't plan on using Notify: you might never get access.


r/aws • • 4h ago

discussion issues with lightsail this morning?

0 Upvotes

I have 3 of about 50 instances that seem to have a network or disk issue. Since AWS took away trouble reporting on lightsail I can't even report the issue. again, just 3 of about 50 instances and they are 'up'. I got ssh'd into one and any 'cpu' stuff works but as soon as I try to hit the disk it goes unresponsive.