Hello,
I’d like to explore some of the subscription-only content on AWS Skill Builder, but it seems that the only available payment method is through an AWS account.
Are there any alternative ways to pay for the subscription?
Everyday since the end of April cost of EBS is sky-rocketing without clear reasons as to why.
Things i've check and explored. estimated end of month would be around 7-8TB-Mo
If it was a new provisioned you'll expect a large jump and stabilise like feb and march. But currently it just going up and up.
When workloads were on-prem the perimeter was clear. The data center was where security enforcement happened and the WAN was just how sites got there.
After moving to AWS, Azure, and SaaS that model inverts completely. Traffic between users and their data never touches the data center anymore, so enforcement at the perimeter covers nothing that actually matters.
What you end up with is networking managing WAN connectivity and security managing cloud posture in parallel, running different tooling with different visibility into the same environment. That gap is where incidents happen.
I've got a sudden email about two weeks ago that my AWS account is closed.
No reason was given but I suspect that it's because I haven't updated my payment method as my card expired some time ago. I haven't received any notifications that it expired though.
After receiving the email I immediately went and updated the payment method and created a support ticket for account reinstating.
But it has been two weeks now and the ticket just sits there unassigned without a response.
What do I do now?
I have important data that I haven't backed up on S3. I really can't loose it.
Can I do anything to save my account?
UPD. Here's an exact email I've got:
>Greetings from Amazon Web Services,
>This e-mail confirms that your Amazon Web Services account has been closed.
>If your AWS account was closed after the first day of any month you may still receive another bill. Please see the Billing & Cost Management Console for details about any remaining charges applicable to the services you have used. You may also download any past billing statement or tax documents in the Billing & Cost Management Console.
>If you self-closed your account, it will permanently close in 90 days. Once that period has passed, the account cannot be reopened, and AWS will delete any remaining content in the account.
>If AWS closed your account, the account will be permanently closed after 60 days. Once that period has passed, the account cannot be reopened, and AWS will delete any remaining content in the account.
>To reopen your account before it is permanently closed, (1) you must contact AWS Support as soon as possible, and (2) we must receive full payment of any outstanding balance, including providing required information as specified on the invoice, 30 days before your account will be permanently closed.
>Note that if your account was associated with GovCloud, there are different account closure processes. Refer to additional instructions at AWS GovCloud Account Closure page.
>If you wish to download any past statements or tax invoices you can do so here (select the month and expand the summary section to download the payment invoices and/or tax documents), you will not be able to do this after your account is permanently closed.
>For more details, please see the Amazon Web Services Account Closure page.
>Sincerely,
>Amazon Web Services
Tying to find a course to improve my AWS knowledge. Im considering Boot dev, KodeKloud, Pluralsight, and AWS Skill Builder. What would be enough to develop a solid foundation for someone with a devops background?
Building an MVP right now and keep seeing mixed opinions on Amazon Cognito. Some people say it’s great because you don’t have to manage auth yourself. Others say costs + complexity become painful as you scale.
For people who’ve used it: was it worth it? did you eventually migrate away? any better alternatives for startups/simple SaaS apps?
Trying to avoid rebuilding auth later 😭
Update/edit: now considering Auth0, but most folks are saying its costly, descope is also an option - has less reviews on the market but it seems more customisable, stytch / firebase are decent options too but cost/feature parity is again another ongoing discussion.
Hi folks.
Our team is building a new feature for our application and we need an Amazon Connect instance with a few associated phone numbers (just several for now). On the Amazon dashboard, the AWS default quota value is listed as 5, with a description saying: "The maximum number of phone numbers you can claim for this instance in the current Region".
So we're on a development/testing phase at the moment. I was initially able to create and claim a phone number, but after deleting it and attempting to recreate it, I'm no longer able to create even a single phone number. Interestingly, there's another column in the console called "Applied quota value" and it shows "0", which I assume overrides the default quota.
We contacted support to request an increase to the quota and this is what we received:
>Your account does not currently meet the criteria for approval for a phone numbers per instance quota increase. The "Applied quota value: 0" you are seeing is an intentional account-level restriction, not a provisioning error. As a result, your request for more phone numbers per instance cannot be approved at this time. Amazon Connect is a contact center solution intended for organizations with production business use cases.
Has anyone encountered anything similar? I've seen plenty of YouTube videos where people create phone number instances left and right for demos, tutorials and other purposes, and I've never heard that this type of instance is intended "for organizations with production business use cases" only. It's even stranger because our case is an actual production business use case, it's just in the initial phase of development right now.
We have a node project, and I just upgraded to serverless v4, and I'm having issues with the deploy, we deploy doing sls deploy with github actions, and it takes like 15 minutes to deploy all lambdas with serverless v3, we use the serverless-bundle plugin. But now, with esbuild, it kept going for 47 minutes, until github just said it failed, in the action itself it showed the loading yellow dot like it kept going.
Anyways, I'm working on fixing it, at least have a clean deploy and then optimize stuff. But I started to question if it's worth it. A lot of people don't like v4, especially becuase of the price, but I think our org is small enough for it to be free, we don't even make that many deploys daily. I'm not 100% sure we won't have to pay though.
Do you think it's better to switch to something else? I'm not sure how much it'll take me to fix the deploy and optimize it, and maybe we can just switch to something else, like https://github.com/oss-serverless/osls, or AWS SAM.
Yes, it sucks that I already worked on upgrading to v4, but that's life.
I just started learning AWS yesterday.
I learned that AWS uses a pay-as-you-go pricing model.
If I publish a website using S3 as a portfolio, do I have to keep paying to keep it online, even when no one is viewing it?
I want to know how to prove that I can use AWS.
In many videos, people say that instead of only getting certifications, it’s better to build real projects because it helps you get jobs more easily.
I know this might be a beginner question, but I couldn’t get a clear answer from ChatGPT, so I’m asking here.
Hello! Wondering what I should learn such as knowing where tokens are stored, S3, etc.
Thanks 😃
I've been using AWS for many years. When starting a new project, I create a new account for it. Recent stack plan is: Bedrock, SES, DynamoDB, Lightsail, IAM, CloudTrail, ECR, EKS, CloudWatch, Certificate Manager, etc.
It's still early in the project but I know SES requires approval so I submit my request... 2 days later, after sending them all the details requested, they deny my request. Their reason? "We cannot tell you why, for security reasons." Then they marked the issue as "resolved."
I've never misused an account nor sent marketing emails nor spam and never would. I re-opened the issue, replied, and linked my previous, years-old account. After 3 days, still no response.
I always looked at the difficulty with using AWS as job security for me, but the delay in responding and the ridiculous reason for denial make me wonder: Should I be avoiding AWS?
I was building my website for several months and was planning to use SES from Amazon because it's honestly the cheapest option, and I won't be making any money from my website since it would just be showing information to users for free, so it looked like a good choice.
I was planning to use it for registration/password reset/security emails for my users.
Well, I got rejected today, and after reading a bit about it on this subreddit, I can see that it's not uncommon.
Could someone please give me any tips on whether there is something that I can do to try again, or suggest an alternative?
Migrated our GenAI development from OpenAI to Bedrock to keep data in VPC. First month bill was 3x expected. Claude Opus tokens are expensive and we had no caching, plus cross-region inference costs we didn’t see. Also paying for provisioned throughput we barely use. For teams doing GenAI development on Bedrock, what cost controls are non-negotiable? Any AWS native tools for prompt caching, batching, or do you build your own? Need to cut this bill 60% or we roll back. CTO is angry.
Hi, I’m doing an internship where my mentor has asked me to transfer data from my laptop’s folder (local machine) to an ec2 server in THREE different methods.
I used scp but she said it’s too basic, then for my first method i used aws s3 sync, mountpoint and task scheduler.
PLEASE tell me two more methods i can use under FREE TIER.
We're two non-tech founders building an accounting product for Indian SMBs. Tiny scale, 0 to 10 customers in the first few months, maybe 100 by end of year if things work. Compliance pushes us into ap-south-1 because Indian books of accounts have to stay in India.
The reason I'm posting is we just went through two rounds of cost review and both rounds caught fairly basic stuff we'd missed. Want to see if r/aws spots more before we click anything.
Setup at launch:
RDS PostgreSQL Multi-AZ db.t4g.small for the main DB, plus a separate Single-AZ db.t4g.micro for the audit log (compliance reason, restore of main can't reach audit). RDS Proxy in front of both. Cache.t4g.micro Redis, single node. One Fargate worker running 24/7 for backups. App Runner for the main app, though we have a fallback to Fargate+ALB because there's some chatter that App Runner is closed to new accounts now. Six S3 buckets, one of them in Object Lock Compliance mode for the audit evidence. KMS keys per environment. CloudTrail and GuardDuty in both ap-south-1 and ap-south-2.
After corrections, our line items work out to roughly:
RDS main 5,200. RDS audit 1,000. Two RDS Proxies 3,700 (this is the one that stung, we had it at 500 because we thought it was a flat fee, turns out it's per vCPU per hour). Redis 1,500. Fargate worker 3,470. App Runner 2,100. S3 350. KMS 300. Secrets Manager 550. CloudWatch 400. CloudTrail 200. GuardDuty 600. CloudFront 100. NAT Gateways 5,500 (we just plain forgot this one in v1, two NATs for prod, one for staging). Public IPv4 500 (the EIPs the NATs sit on, AWS started charging $0.005/hr per IP last year). Developer Support for the launch month, 2,400. Misc data transfer 500.
Comes to 27,985 pre-GST. AISPL adds 18% GST. Lands around 33,022 a month all in.
At 100 customers we're projecting 51,053 a month. Plan is to grab Reserved Instances once we have 30 to 60 days of stable usage, that should claw back 30 to 62% on the RDS side depending on term.
What I want to know:
What are we still missing. The ones I'm nervous about are cross region S3 replication egress (we replicate to Hyderabad), RDS backup storage past the free tier (35 day retention at 50GB autoscaling to 200GB, that compounds), ECR storage as we push more images, and CloudWatch Logs Insights if we end up using it a lot.
Anyone actually running a vaguely similar shape on ap-south-1, does our launch number track with what you see on your bill.
The RDS Proxy question. Is 3,700 a month for the pair actually worth it on db.t4g.small. We use Prisma which is connection-hungry but at our launch scale it might be cheaper to tune the pool manually and add Proxy later.
Anyone provisioned App Runner in a fresh ap-south-1 account opened this month. If it's actually closed to new customers we need to know now.
Not selling anything, trying to not blow up our runway in month one.
Hey everyone. I am a pre final year student. I have built a web app comprising of 4 microservices along with Docker and all. I dont have any idea about AWS and will be guided by my Devops teacher at the University.
small rant.
Woke up this morning to our account suspended. We had a case come up about a month ago stating suspicious activity and possible compromised account. We looked all over cloud trails all the tenant items and found nothing of note. Proceeded to ask for more information for the next couple of days with no response from AWS support. I closed the ticket as I've seen them re-open if there are any issues still open. Not this time and then finally the day of reckoning came and boom account suspended.
I understand I probably should have pestered them more but I don't think its cool to not respond to a ticket and then suspend a production account. I have since opened up the old ticket and created a new one to bring the account online. I was hoping to pay for expedited services but can't while your account is in this state it seems. So I'm stuck with basic support and a director who is pacing in front of my office.
So in desperation here I am on reddit posting in hopes of an escalation.
Happy Tuesday everyone 😄
Is it risky to disable AWS WAF, when all I have is placeholder 1-page sites. It costs me 24 per month to have WAF.
