Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Static Outbound IPs, VPCs, and Access Zones

0

I was planning on using a Lambda service to access an API that requires pre-registered IP addresses. I followed this guide to create a VPC that included a gateway, two subnets, and two elastic IP addresses:

Generate a static outbound IP address using a Lambda function, Amazon VPC, and a serverless architecture.

Everything worked correctly and I was able to verify that my Lambda function was able to use these outbound IP addresses. Since successfully setting up this VPC I have been receiving charges at $2.30 / day for "EC2 - Other", about $70 USD / month. This is more than I expected a service like this to cost.

On visiting the EC2 Global view I was surprised to see I have resources set up in 17 regions. Is this what is contributing to this cost? Should I destroy the additional services in other regions to reduce my cost?

Topics
ServerlessCloud Financial ManagementComputeNetworking & Content Delivery
Tags
Amazon VPCAWS LambdaAWS Billing
Language
English
asked 2 years ago644 views
1 Answer
1
Accepted Answer

If I create the configuration diagram as you shared in your document, the NAT Gateway fee is included in "EC2 - Other".
NAT Gateway is 0.045 USD per hour.
This costs 2.16 USD per day since there are two of these.
Also, since you are charged for the amount of data processed, I thought perhaps the "EC2 - Other" on your bill is mostly for the NAT Gateway.
https://aws.amazon.com/vpc/pricing/?nc1=h_ls

The invoice would show the region where the cost is being incurred.
If this region is not the one you are expecting, you should check your resources, etc.
Please refer to the following document on how to check for active AWS services.
https://repost.aws/knowledge-center/check-for-active-resources

EXPERT
answered 2 years ago
EXPERT
reviewed 2 years ago
  • bummmer
    2 years ago

    Thank you very much - that makes sense. After setting up a single VPC what do you think contributed to having VPCs set up in 17 regions? My account is new and the only networking changes that I made were from this tutorial.

  • Riku_Kobayashi EXPERT
    2 years ago

    I believe a default VPC was just created for each region. https://docs.aws.amazon.com/vpc/latest/userguide/default-vpc.html

    When you start using Amazon VPC, you have a default VPC in each AWS Region. A default VPC comes with a public subnet in each Availability Zone, an internet gateway, and settings to enable DNS resolution. Therefore, you can immediately start launching Amazon EC2 instances into a default VPC. You can also use services such as Elastic Load Balancing, Amazon RDS, and Amazon EMR in your default VPC.

  • bummmer
    2 years ago

    Great answers - thank you very much

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.

Relevant content