u/badoopbadoopbadoop

Yes, definitely try this. I have experienced something similar (very poor networking performance). Very inconsistent, but this fixed it.

Iowa is blacked out for 6 teams while also not having a team.

Are you sure you had an Elastic IP? Elastic IPs aren’t released by anything you described. Elastic IPs generally have to explicitly released.

Maybe you just had a regular dynamic public IP address?

Azure B2C wasn’t retired May of 2025. They just aren’t selling it to new customers. It doesn’t currently reach end of life until at least May of 2030. Unless you’re using P2, which those features end in March 2026.

Grassley is 92. And is potentially running again in 2028.

If you really don’t need general internet access, you can also set it up so that the session hosts can hit Azure service endpoints directly without a NAT gateway . This is referred to as Private Link. It will only work for AWS services and is designed to keep Azure service traffic on the Azure private network.

In addition

What region is your bucket in? Where is your upload occurring relative to that region?

Being loyal to a large service provider generally provides no benefit to the individual consumer. The service providers goal is to make money. Keeping you happy might be a desire, but they will drop that if it means they can get more money.

Generally the larger the service provider, the less they will care.

I’ve had all of the streaming services at some point. This happens to all of them. I recently left Direct TV because it was getting too expensive for my needs. I found alternatives to be acceptable and cheaper for my needs. If my needs or desires change, perhaps I’ll be back.

Being “proud” of supporting a brand as a consumer is tricky. I used to share it for certain brands. Personally I’ve found that it isn’t beneficial to me or anyone I tried to share it with.

Lots of questions on the timeline until AWS provides a full report. Just going off what I personally experienced and heard - which is that it started with a missing DNS entry for dynamodb. After that was corrected and recovery was underway the load balancer issue was reported. It’s possible that the load balancer issue was the root cause of the original dynamodb problem, but I haven’t seen anything from AWS indicating that. But it is absolutely possible.

The issue wasn’t with the availability of Route 53 as a service.

The (initial) issue is that the DNS record no longer existed - likely because it was removed - probably automatically by some sort of scaling / availability service.

A customer (AWS themselves in this case) is responsible for their own records and wouldn’t be covered by a service SLA.

https://docs.aws.amazon.com/ebs/latest/userguide/recognize-expanded-volume-linux.html

https://aws.amazon.com/end-user-messaging/pricing/

Note: When you create a short code request case, we send you information about the one-time and recurring charges for obtaining the short code in the countries or regions that you request. If you accept these charges, the fees associated with using short codes begin immediately. You're responsible for paying these charges, even if the short codes that you requested haven't been completely provisioned yet.

Not saying I agree with the practice, but it is documented.

What service + platform are you attempting to run it on?

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/capacity-blocks-pricing-billing.html

You paid for the reservation, not the use of it. This is the case for all savings types (Savings Plans, Reserved Instances, etc). The alternative is to use OnDemand and have no guarantee of capacity. AWS is giving a discount because you are committing to the spend.

With Amazon EC2 Capacity Blocks for ML, you pay only for what you reserve. The price of a Capacity Block depends on available supply and demand for Capacity Blocks at the time of purchase. You can view the price of a Capacity Block offering before you reserve it. The price of the Capacity Block is charged up front at the time the reservation is made

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-explicit.html

Usage – When you share an AMI, users can only launch instances from the AMI. They can’t delete, share, or modify it. However, after they have launched an instance using your AMI, they can then create an AMI from their instance. Copying shared AMIs – If users in another account want to copy a shared AMI, you must grant them read permissions for the storage that backs the AMI. For more information, see Cross-account copying.

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/how-ami-copy-works.html

To copy an AMI that was shared with you from another account, the owner of the source AMI must grant you read permissions for the storage that backs the AMI, not just for the AMI itself.

So you can’t prevent them from launching an instance then creating an Ami from that instance. You should be able to prevent them from directly creating a copy of the AMI by not allowing access to the underlying snapshots.

Because your EBS volume uses one KMS key and your backup vault uses a different KMS key. A snapshot can only be encrypted by one key.

Because you can’t specify a KMS key when creating a snapshot from an EBS volume. When snapshotting an EBS the snapshot will always have the same KMS key as the volume.

Only when you are copying a snapshot can you specify a KMS key for the target snapshot.

I’m 4-0 this year. One (regular season) game left against Cards.

What’s confusing about this name?

All camping on the swamps is on cots or in hammocks out in the open. We had youth and adult females in our crew. All necessary accommodations are made to ensure privacy and follow BSA rules. Changing tents are available for everyone to use.

Base camp is at a hotel and you’ll get a room to yourself if you’re the only female adult leader.

Travel: we drove as a caravan of vehicles. About 16 hours so we obviously had to split it across two days. Found a place a little past midway where we could camp.

Prep: we asked all youth participants to have canoeing or kayaking MB. We only had time to get in one pre-trek canoe trip. Would more have been beneficial? Absolutely, but it was the best we could do.

Weather: it was hot. Very hot and sunny. We took a lot of breaks and spent a lot of time jumping in the water to cool off. You will sweat and be uncomfortable, even at night. Don’t think you’ll find any way to avoid that.

Portages: the portages are short. You work as a team to drag the canoes across. The first has a large berm you’ll go over so that makes it more challenging. The swamp stomp is fun but it can be physically taxing. It isn’t very long though.

It is a high adventure. Expect it to be a mental and physical challenge for adults and youth. Some will excel and some will struggle. But you work together as a crew and rise above the challenges. It is an amazing experience and a very well run program. I recommend it to everyone that asks me about it. There is a lot of amazing beauty in the swamp that I never expected to see.

Medical: I’m not sure I can provide anything specific regarding diabetes. But medical was handled like any other event - a crew adult handled medications and ensured they were distributed as needed. Scouts with lifesaving medical devices (inhalers, Epi, etc) carried one on them and had a crew adult with backup. Guides had the ability to arrange emergency evacuation.

In many cases the access denied is because the python module install location is in Program Files and is write restricted. You can work around this using virtual environments (venv) which is built into python. You can create a venv somewhere in your home directory that you have full write access to and install modules to that venv.

If the company has other policies that are actually blocking pypi from a network perspective this wouldn’t work. But based on your error message that isn’t what is happening.

Could be your ALB healthchecks depending on how you have those configured.

You can verify by using access log or cloudtrail data events. If it shows source ip as private it’s going through the endpoint.

https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-s3.html

The source IPv4 addresses from instances in your affected subnets as received by Amazon S3 change from public IPv4 addresses to the private IPv4 addresses in your VPC

Huh? These aren’t really related. You can do SCIM regardless of whether the authentication method is SAML or OIDC.

OIDC is a newer protocol than SAML. I find that most enterprise apps that have been around for a long time still only support SAML, but OIDC is finally on the rise.