EMR Serverless Outbound Internet Access without NAT Gateway

0

EMR Serverless requires the use of a NAT Gateway for outbound Internet access. The link is here.

Will AWS consider a feature request that doesn't require the use of a NAT Gateway? A NAT Gateway is expensive to operate. Moreover, why should I set up a NAT Gateway which has time usage charges when I'm only running a few batch processes per day on EMR Serverless?

1 Answer
1

In terms of requesting features, please reach out to your local AWS team to discuss.

If you only need access a few times a day is there scope to do something completely different? For example, if access does not need to be synchronous could you have the workload request the data that it requires via (say) a SQS message; have a Lambda function triggered from that which retrieves (or sends) the appropriate data; then put the result into S3 or back into another SQS message?

Yes, it's more work for you but it might be less expensive in terms of AWS services. That said, your time and effort is actually worth something so perhaps running NAT Gateway when you need it is actually cost effective.

profile pictureAWS
EXPERT
answered a month ago
profile pictureAWS
EXPERT
iBehr
reviewed a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions