Fwd: [Notification] New pricing for Amazon Lightsail bundles that use public IPv4 address starting May 1, 2024 [AWS Account: 941561944431] [US-WEST-2]
41 views
Skip to first unread message
Larry Masinter
Apr 4, 2024, 7:55:42 PM4/4/24
to Interlisp core
I don't think we need to worry about this, but FYI. Online.interlisp.org does use a fixed IPv4 address.
Hello,
You are receiving this message to inform you about the upcoming pricing update for your Amazon Lightsail instance bundles.
On January 25, 2024, Lightsail announced updated pricing for bundles [1] that include a public IPv4 address. Following AWS’s announcement on public IPv4 address charge [2], the prices of Lightsail bundles offered with a public IPv4 address will reflect the charge associated with the public IPv4 address. Starting May 1, 2024, revised prices will be effective for all new and existing bundles that include a public IPv4 address.
Amazon Lightsail now offers IPv6 bundles for use-cases that do not require a public IPv4 address. If a public IPv4 address is not required for your Lightsail workloads, we recommend migrating your instances to IPv6 bundles. To learn more about IPv6 bundles, see Lightsail documentation [3].
A list of your affected resource(s) can be found in the 'Affected resources' tab in the AWS Health Dashboard.
If you have questions or concerns, please contact AWS Support [4].
[1] https://aws.amazon.com/blogs/compute/announcing-ipv6-instance-bundles-and-pricing-update-on-amazon-lightsail/
[2] https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
[3] https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-ipv6-only-plans
[4] https://aws.amazon.com/support
Sincerely,
Amazon Web Services
Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210
---
Reference: https://health.aws.amazon.com/health/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-west-2::event/BILLING/AWS_BILLING_NOTIFICATION/AWS_BILLING_NOTIFICATION_77d76d03906657afc581caaeb07f88863ce57b9a45b7c9923c458460fd3f7ee1&eventTab=details
--
---------- Forwarded message ---------
From: Amazon Web Services, Inc. <no-rep...@amazon.com>
Date: Tue, Apr 2, 2024 at 1:09 PM
Subject: [Notification] New pricing for Amazon Lightsail bundles that use public IPv4 address starting May 1, 2024 [AWS Account: 941561944431] [US-WEST-2]
To: <medleyi...@gmail.com>
From: Amazon Web Services, Inc. <no-rep...@amazon.com>
Date: Tue, Apr 2, 2024 at 1:09 PM
Subject: [Notification] New pricing for Amazon Lightsail bundles that use public IPv4 address starting May 1, 2024 [AWS Account: 941561944431] [US-WEST-2]
To: <medleyi...@gmail.com>
Hello,
You are receiving this message to inform you about the upcoming pricing update for your Amazon Lightsail instance bundles.
On January 25, 2024, Lightsail announced updated pricing for bundles [1] that include a public IPv4 address. Following AWS’s announcement on public IPv4 address charge [2], the prices of Lightsail bundles offered with a public IPv4 address will reflect the charge associated with the public IPv4 address. Starting May 1, 2024, revised prices will be effective for all new and existing bundles that include a public IPv4 address.
Amazon Lightsail now offers IPv6 bundles for use-cases that do not require a public IPv4 address. If a public IPv4 address is not required for your Lightsail workloads, we recommend migrating your instances to IPv6 bundles. To learn more about IPv6 bundles, see Lightsail documentation [3].
A list of your affected resource(s) can be found in the 'Affected resources' tab in the AWS Health Dashboard.
If you have questions or concerns, please contact AWS Support [4].
[1] https://aws.amazon.com/blogs/compute/announcing-ipv6-instance-bundles-and-pricing-update-on-amazon-lightsail/
[2] https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
[3] https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-ipv6-only-plans
[4] https://aws.amazon.com/support
Sincerely,
Amazon Web Services
Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210
---
Reference: https://health.aws.amazon.com/health/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-west-2::event/BILLING/AWS_BILLING_NOTIFICATION/AWS_BILLING_NOTIFICATION_77d76d03906657afc581caaeb07f88863ce57b9a45b7c9923c458460fd3f7ee1&eventTab=details
Frank Halasz
Apr 5, 2024, 3:11:29 PM4/5/24
to Larry Masinter, Interlisp core
This only applies to wasm.interlisp.org (the emscripten site), which runs on AWS Lightsail. (And I was aware of this upcoming pricing change when I set it up).
online.interlisp.org runs on an AWS EC2 instance using an ElasticIP address. I'm pretty sure the IP4 tax has been baked into the ElasticIP pricing for a while now.
As far as I can tell, Lightsail is essentially "grab and go" EC2. A Lightsail instance is essentially an EC2 instance with a specific software stack prepackaged, preconfigured, and ready to run. wasm.interlisp.org uses the Ngnix package on Lightsail.
-- Frank
--
You received this message because you are subscribed to the Google Groups "Medley Interlisp core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lispcore+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lispcore/CAKq15veVAg8o-oZU9hR15L7sqKMEx_cEKi_LKWeN_Yi_8E6LEw%40mail.gmail.com.
Nick Briggs
Apr 5, 2024, 3:25:45 PM4/5/24
to Frank Halasz, masinter, Lisp Core
I don't think we have any particular requirement for either online or wasm to have only IPv4 addresses - most people today should be able to access a site via IPv6, right?
Visit https://test-ipv6.com and see if you've got the right things configured.
For my home connection:
How this test works: Your browser will be instructed to reach a series of URLs. The combination of successes and failures tells a story about how ready you are for when publishers start offering their web sites on IPv6.
Click to see Technical Info
| Test with IPv4 DNS record | ok (0.544s) using ipv4 | |
| Test with IPv6 DNS record | ok (0.352s) using ipv6 | |
| Test with Dual Stack DNS record | ok (0.333s) using ipv6 | |
| Test for Dual Stack DNS and large packet | ok (0.336s) using ipv6 | |
| Test IPv6 large packet | ok (0.408s) using ipv6 | |
| Test if your ISP's DNS server uses IPv6 | ok (0.287s) using ipv6 | |
| Find IPv4 Service Provider | ok (1.030s) using ipv4 ASN 46375 | |
| Find IPv6 Service Provider | ok (1.008s) using ipv6 ASN 46375 |
To view this discussion on the web visit https://groups.google.com/d/msgid/lispcore/CAD80JJg_jhpzZJy9dxi%2BhgfNTUrZa%2BnBPX3dFYGjvAbBxG%2BVSQ%40mail.gmail.com.
Paolo Amoroso
Apr 5, 2024, 3:31:31 PM4/5/24
to Nick Briggs, Frank Halasz, masinter, Lisp Core
On Fri, Apr 5, 2024 at 9:25 PM Nick Briggs <nicholas...@gmail.com> wrote:
Visit https://test-ipv6.com and see if you've got the right things configured.
No joy for my ISP, Vodafone Italy, which doesn't support IPv6:
How this test works: Your browser will be instructed to reach a series of URLs. The combination of successes and failures tells a story about how ready you are for when publishers start offering their web sites on IPv6.
Click to see Technical Info
| Test with IPv4 DNS record |
ok (0.080s) using ipv4 |
| Test with IPv6 DNS record |
bad (0.034s) |
| Test with Dual Stack DNS record |
ok (0.090s) using ipv4 |
| Test for Dual Stack DNS and large packet |
ok (0.078s) using ipv4 | ||
| Test IPv6 large packet | bad (0.047s) | |
| Test if your ISP's DNS server uses IPv6 |
timeout (15.020s) | ||
| Find IPv4 Service Provider | ok (0.114s) using ipv4 ASN 30722 | |
| Find IPv6 Service Provider | bad (0.023s) |
Herb Jellinek
Apr 5, 2024, 6:30:08 PM4/5/24
to lisp...@googlegroups.com
Not looking good with AT&T Fiber and Google DNS:
| Test with IPv4 DNS record |
|
ok
(0.017s) using ipv4
|
| Test with IPv6 DNS record |
|
bad
(0.008s)
|
| Test with Dual Stack DNS record |
|
ok
(0.017s) using ipv4
|
| Test for Dual Stack DNS and large packet |
|
ok
(0.019s) using ipv4
|
||
| Test IPv6 large packet |
bad
(0.011s)
|
|
| Test if your ISP's DNS server uses IPv6 |
|
ok
(0.018s) using ipv4
|
||
| Find IPv4 Service Provider |
ok
(0.767s) using ipv4 ASN 7018
|
|
| Find IPv6 Service Provider |
bad
(0.013s)
|
Herb
--
You received this message because you are subscribed to the Google Groups "Medley Interlisp core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lispcore+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lispcore/CAGi1hzveMmBZ2Mv1P3QqL78XOKrh5Dp%3DXFUpLGn4i7PMpF3CWQ%40mail.gmail.com.
Nick Briggs
Apr 5, 2024, 7:10:49 PM4/5/24
to Herb Jellinek, Lisp Core
Hmm... AT&T says they support IPv6 and have provided IPv6 capable CPE for some time. Perhaps it's a case of configuring it on?
To view this discussion on the web visit https://groups.google.com/d/msgid/lispcore/1b68656e-1c17-4fb0-abd3-39e9ef71412d%40newscenter.com.
Michele Denber
Apr 5, 2024, 7:50:10 PM4/5/24
to lisp...@googlegroups.com
On 4/5/2024 7:10 PM, Nick Briggs wrote:
> Hmm... AT&T says they support IPv6 and have provided IPv6 capable CPE
> for some time. Perhaps it's a case of configuring it on?
My ISP had IPv6 disabled on my account. I called them up and asked if
> Hmm... AT&T says they support IPv6 and have provided IPv6 capable CPE
> for some time. Perhaps it's a case of configuring it on?
they had IPv6. I could tell the CSR was looking at the phone like I had
two heads. He just said no. I said "How can you not have IPv6? It's
been around for 20 years now." He replied "Oh, well we wouldn't support
anything that old." I finally got through to someone else who knew what
IPv6 was.
- Michele
Runes
Apr 5, 2024, 8:15:29 PM4/5/24
to Lisp Core
My ISP (Astound) says they have ISP in “most locations”. Turned on the default config on my router, but it’s not picking up a config so I suspect I’m not in one of those locations. I’ve called them before and like Michele’s experience, it’s a crapshoot on whether you find someone who knows what they’re talking about.
> --
> You received this message because you are subscribed to the Google Groups "Medley Interlisp core" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to lispcore+u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/lispcore/953ed46c-24fb-4c99-b1b2-abd27af4526b%40gmx.com.
> You received this message because you are subscribed to the Google Groups "Medley Interlisp core" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to lispcore+u...@googlegroups.com.
Herb Jellinek
Apr 5, 2024, 8:15:35 PM4/5/24
to Nick Briggs, Lisp Core
My fiber gateway, an ARRIS BGW210-700, says this:
And its built-in diagnostics tool appears to allow pinging IPv6 addresses.
I need to look into this more deeply. A new hobby!
Herb
| Service Type | native IPv6 |
|---|
And its built-in diagnostics tool appears to allow pinging IPv6 addresses.
I need to look into this more deeply. A new hobby!
Herb
To view this discussion on the web visit https://groups.google.com/d/msgid/lispcore/F6ADADA7-F8F3-4494-9487-00FCE5B0B51F%40gmail.com.
Reply all
Reply to author
Forward
0 new messages