Economics news, commentary, research: 2025

Concatenation code:
* create dataset A;
data DataA;
Num=1;VarB=1;output;
Num=2;VarB=2;output;
Num=3;VarB=3;output;
run;
* create dataset B;
data DataB;
Num=1;VarB="1";output;
Num=2;VarB="2";output;
Num=3;VarB="3";output;
run;

* concatenate A and B;
Data DataAB;
set DataA DataB;
run;
* concatenate B and A;
Data DataBA;
set DataB DataA;
run;
Data DataAB1;
set DataA DataB;
VarB1=VarB*1;
run;

data dataA1;
set DataA;
VarB1 = VarB;
drop VarB; *fix;
run;
* two variables: Num and VarB1;

data dataB1;
set DataB;
VarB1 = VarB*1;
run;
* three variables: Num, VarB, VarB1;
Data DataA1B1;
set DataA1 DataB1;
run;

==========

For Badge, complete all quizzes at 80% or higher

Then you should see 100% completion here:

https://learn.sas.com/course/view.php?id=235

When you scroll down you should be able to claim that badge:

It will tell you that you will receive digital copy in email:

... after about 30min.

THIS IS SUFFICIENT - you can simply create PDF of your email and upload to Canvas or take screenshot.

Apparently you must create an account and share your ECU email with private company:

I did my standard password and added at the end "QQQ111!!!"

I selected Public badge view

This is what changed:

When I clicked verification I got:

So any screen with your name on it is fine.

CNBC: Private-jet demand is on the rise amid government shutdown, says Flexjet CEO

Flight disruptions from shutdown worsen; Delta, United offer extra pay to crew flights

https://www.cnbc.com/2025/11/10/government-shutdown-flight-delays-cancellations.html

AIRLINES Private-jet demand is on the rise amid government shutdown, says Flexjet CEO PUBLISHED MON, NOV 10 20259:12 AM ESTUPDATED 25 MIN AGO thumbnail Leslie Josephs @LESLIEJOSEPHS

https://www.cnbc.com/2025/11/10/private-jet-demand-government-shutdown.html

-=-=-=

Can Donald Trump do what Ronald Reagan did to solve issue with airlines during government shutdown?"

That’s a really sharp question — and it touches on a few important legal and historical differences. Let’s unpack it carefully.

1. What Reagan did

In 1981, President Ronald Reagan fired over 11,000 air traffic controllers who went on strike with the union PATCO. He did this because:

Federal law (the Taft–Hartley Act and 5 U.S.C. §7311) prohibits federal employees from striking.
Reagan gave them 48 hours to return to work; when they didn’t, he terminated their employment and banned them from federal service (a ban later lifted under Clinton).

So Reagan acted under existing law against striking federal workers — not during a government shutdown, but during an illegal strike.

2. How a government shutdown is different

A shutdown happens when Congress fails to pass funding, not when workers strike. During a shutdown:

Federal employees aren’t allowed to work (except “essential” workers) because there’s no legal authority to pay them.
They’re furloughed or required to work unpaid until funding is restored.
The Antideficiency Act bars agencies from spending money Congress hasn’t appropriated.

So, unlike Reagan’s situation, employees aren’t refusing to work — the government is legally barred from employing or paying them. That means Trump (or any president) can’t fire workers for not working during a shutdown, because they’re being told by law not to work.

3. What Trump could do

If Trump were president during a shutdown, his options would be more limited:

He could declare some additional employees “essential” to keep certain operations running (like air traffic control).
He could redirect or repurpose existing funds — but only within strict legal limits.
He could negotiate with Congress or use political pressure to end the shutdown.

But he couldn’t use Reagan’s 1981 approach, because that was a response to an illegal strike, not a lack of congressional funding.

In short:
No — Donald Trump (or any president) couldn’t “do what Reagan did” during a shutdown, because Reagan’s solution addressed an illegal strike, while a shutdown is a funding issue controlled by Congress. The law that stopped Reagan’s air traffic controllers doesn’t apply to shutdowns.

Would you like me to explain how a president might legally keep air traffic running during a shutdown (for instance, by reclassifying or reprioritizing essential workers)?

So explain how the shutdown affects airlines different than when it happened during Reagan presidency?

Excellent follow-up — and an important distinction.

Let’s break this down step-by-step:

1. Reagan’s 1981 situation (PATCO strike)

What happened:
The Professional Air Traffic Controllers Organization (PATCO) went on strike for better pay, shorter hours, and improved working conditions.
Why it happened:
Controllers voluntarily stopped working, violating federal law, because federal workers are forbidden to strike (5 U.S.C. § 7311).
Reagan’s response:
He ordered them back to work, and when they refused, he fired over 11,000 controllers and banned them from federal service.
Impact on airlines:
- About half of the nation’s air traffic control system was suddenly understaffed.
- The FAA reduced the number of flights allowed to maintain safety.
- Airlines saw fewer flights, delays, and temporary service disruptions, but operations continued using supervisors, military controllers, and replacements.
- Within months, air travel stabilized.

→ Summary: Airlines were affected by a labor shortage caused by a strike, not a lack of funding.

2. A modern government shutdown

What happens:
When Congress fails to pass a funding bill (appropriations), the Antideficiency Act requires many federal operations to stop because they can’t legally spend money.
Who’s affected:
- “Non-essential” federal workers are furloughed (temporarily laid off).
- “Essential” workers — such as air traffic controllers, TSA officers, and FAA safety inspectors — must keep working, but without pay until the shutdown ends.
Impact on airlines:
- Flights generally continue operating, since air traffic controllers and TSA keep working.
- However, unpaid workers often call in sick, creating staffing shortages and long security lines.
- Training, certification, and inspections (non-emergency FAA functions) are paused, which can delay new routes, aircraft certifications, or safety reviews.
- Extended shutdowns can cause airline scheduling chaos, delays, and economic ripple effects, even if planes keep flying.

→ Summary: Airlines are affected by disruptions due to unpaid or furloughed federal workers, not by an illegal strike or mass firing.

3. The core difference

Aspect	Reagan’s 1981 Crisis	Government Shutdown
Cause	Illegal strike by air traffic controllers	No funding from Congress
Legal Authority	Workers broke the law; Reagan fired them	Law forbids paying workers without funding
Workers’ Status	Striking voluntarily	Forced furlough or unpaid work
President’s Options	Fire, replace, or negotiate	Classify as “essential,” pressure Congress
Airline Impact	Sudden but fixable staffing shortage	Ongoing disruptions, slower operations

In short:

Under Reagan, the problem was workers refusing to work — so he used executive authority to replace them.
During a shutdown, the problem is workers can’t be paid — and only Congress can fix that by restoring funding.
Airlines keep flying during a shutdown, but face delays, morale issues, and operational bottlenecks, not the outright collapse risk seen in 1981.

Would you like me to show how a long shutdown (say, over 3 weeks) might start to impact air travel safety or scheduling based on recent examples like 2019?

Friday, October 31, 2025

CNBC: AI companies are downplaying amount of energy and capital they need, Joe Lonsdale says

AI companies are downplaying amount of energy and capital they need, Joe Lonsdale says

https://www.cnbc.com/2025/10/30/palantir-s-lonsdale-says-ai-companies-downplay-energy-capital-needs.html

Venture capitalist Joe Lonsdale, who previously co-founded Palantir, said that top artificial intelligence executives are downplaying the resources needed to meet their plans.
Tech giants have heavily ramped up spending on AI in recent months to build out infrastructure and lure top talent.
Meta, Microsoft and Alphabet on Wednesday raised their forecasts for capital expenditures.
===========

*Example from Prep Guide*;

* first observation;

data DataA1;

Num=1;

VarA="A1";

run;

* second observation;

data DataA2;

Num=2;

VarA="A2";

run;

* concatenate DataA1 and DataA2;

data DataA1A2;

set dataA1 dataA2;

run;

* third observation;

data DataA3;

Num=3;

VarA="A3";

run;

* concatenate DataA1 - DataA3;

data DataA1A2A3;

set DataA1 DataA2 dataA3;

run;

data DataA1A2A3b;

set DataA1A2 DataA3;

run;

* create dataset B;

data DataB;

Num=1;VarB="B1";output;

Num=2;VarB="B2";output;

Num=3;VarB="B3";output;

run;

* concatenate A and B;

Data DataAB;

set DataA1A2A3 DataB;

run;

* how to change the code to align Variable VarA in one column;

* .... so VarB needs to be as VarA in DataB;

Data DataAB;

set DataA1A2A3 DataB;

run;

CNBC: Nvidia CEO Jensen Huang says AI is in a ‘virtuous cycle.’ Here’s what he means

Nvidia CEO Jensen Huang says AI is in a ‘virtuous cycle.’ Here’s what he means

https://www.cnbc.com/2025/10/31/nvidia-ceo-jensen-huang-says-ai-has-reached-a-virtuous-cycle.html

Wednesday, October 29, 2025

CNBC: Boeing stems cash burn for first time since 2023 but takes $4.9 billion charge on 777X delays

Boeing stems cash burn for first time since 2023 but takes $4.9 billion charge on 777X delays

https://www.cnbc.com/2025/10/29/boeing-ba-3q-2025-earnings.html

Friday, October 24, 2025

10/24: Post symposium discussion

Spencer Banzhaf: https://spencerbanzhaf.wordpress.ncsu.edu/

I forgotten to mention that tomorrow Economics Department has a Symposium and I welcome you to attend and want to give you an opportunity to show you are present with the following assignment where you upload your selfie:

Symposium Attendance potential extra credit

Economics Symposium, tomorrow, Thursday, October 23 🕖 7:00 PM 📍 ECU Life Science Building and Biotechnology Building Room 1006

Economics LinkedIn page: https://www.linkedin.com/company/ecu-department-of-economics?trk=public_post_feed-actor-nameLinks to an external site.

-=-=-=

Chat GPT 2025-10-24

✅ Was It True That Economics Initially Focused Only on Market Goods?

Yes — for most of its early history, economics focused almost entirely on goods that were bought and sold in markets. Value was thought to be revealed through prices, and if something had no market price (like clean air, biodiversity, national parks, or scenic beauty), it fell outside traditional economic analysis. Economists viewed these as moral or political issues, not economic ones.

🌿 When Did This Change?

The turning point began in the early 20th century, but became mainstream only after 1950s–1970s.

🌟 Key Pioneers Who Revolutionized Non-Market Valuation

Economist / School	Revolutionary Idea	Key Contribution
Arthur Pigou (1920)	Externalities	Showed that some costs/benefits are not reflected in market prices, laying groundwork for valuing pollution, public goods
Harold Hotelling (1949)	Valuing public lands	Proposed methods for valuing national parks based on people’s travel costs (Travel Cost Method)
Ronald Coase (1960)	Property rights	Demonstrated that environmental goods could be valued through bargaining even when no market exists originally
John Krutilla (1967)	"Conservation Reconsidered"	Argued that nature has economic value even without use, introducing idea of existence value
Clive Granger and later economists (1960s–80s)	Contingent valuation	Developed survey-based methods to measure people’s willingness to pay for non-market goods
Elinor Ostrom (1990s)	Common pool resources	Showed the economic value and governance possibilities of resources without market pricing

🔥 The Most Revolutionary Idea

John Krutilla's 1967 paper "Conservation Reconsidered" is often considered the birth of modern environmental economics. His radical claim:

"A person may derive satisfaction from knowing that a natural environment exists, even if they never visit it or use it."

This was a new economic category: existence value — value without consumption.

📌 Before This Revolution:

If there was no market, economists assumed no value could be measured.
Nature was seen merely as input for production, not as a source of utility in itself.

📌 After This Revolution:

Economists began using survey methods, travel cost models, and hedonic pricing to infer value from people's behavior or preferences.
Environmental economics emerged as a formal subfield.
Today, ecosystem services (like pollination, flood protection, carbon storage) are routinely valued in billions of dollars.

🎯 Final Answer (in simple terms):

Yes, historically economics only valued goods traded in markets.
The revolution began with Arthur Pigou's concept of externalities (1920) and came to full maturity with Harold Hotelling (1949) and John Krutilla (1967), who proved that economists can measure the value of environmental goods even if no market exists. This gave birth to environmental economics and fundamentally expanded the scope of what economics can analyze.

The truly revolutionary step was Krutilla’s idea:

Nature has economic value even if no one ever uses it.

That changed the field forever.

-=-=-=

QUERY: Who was the first one to attempt to put actual value on it, not just argue that it was possible and that there was value?

Great question — you're asking specifically:

Who was the first to actually attempt to measure or quantify the economic value of a non-market good, rather than just argue that such goods have value?*

🎯 The First Real Attempt to Quantify Value of Non-Market Environmental Goods:

Harold Hotelling (1949)

Hotelling is widely credited as the first economist to propose an actual empirical method to measure the economic value of non-market goods — specifically, U.S. national parks.

🔍 What Did He Do?

In 1947, the U.S. Department of the Interior asked economists how they might justify funding for national parks.
Hotelling responded (published in 1949) with the idea that:

The value of a national park could be estimated by observing how much people spend to travel to it (gas, lodging, time).
This became known as the Travel Cost Method, which is still one of the main tools in environmental economics today.

✅ Hotelling was the first to move from philosophy to actual economic valuation using observable behavior.

🧠 Why Hotelling is Considered the First:

Pigou (1920) talked about externalities in theory but didn't estimate actual dollar values.
Coase (1960) discussed property rights and bargaining but didn’t calculate values.
Krutilla (1967) argued for existence value but did not measure it.
Hotelling (1949) actually gave a workable method to measure a non-market good using real data.

🚩 Therefore:

The first serious attempt to put a numerical economic value on a non-market environmental asset (like a national park) was by Harold Hotelling in 1949.

He didn’t complete an empirical study himself, but his method directly led to Clawson & Knetsch (1966), who carried out the first full empirical valuation using the travel cost method based on Hotelling’s framework.

🧾 Summary Answer:

First to propose a practical valuation method: Harold Hotelling (1949)
First to actually implement it in a measured study: Marion Clawson and Jack Knetsch (1966)

Would you like a simplified timeline table showing how valuation evolved from theory → method → measurement?

Wednesday, October 22, 2025

10/22: CBS Evening News: Why is an Amazon Web Services outage able to disrupt vast parts of the internet?

Survey Link:

https://docs.google.com/forms/d/e/1FAIpQLScM6DdUkC8zGQfLI3KyGjZYE_tmXYPWJDxZn_3NfScBHiTybQ/viewform?usp=publish-editor

Why is an Amazon Web Services outage able to disrupt vast parts of the internet?

https://www.youtube.com/watch?v=vrg6mY5fYwo

https://www.youtube.com/watch?v=s567jUtkgEU

https://www.youtube.com/watch?v=KFvhpt8FN18

Monday, October 20, 2025

ECN6111 class

Sas Course: https://learn.sas.com/course/view.php?id=118

SAS Studio: https://welcome.oda.sas.com/

SAS Programming 1: Lesson 4, Part 2, Video 1: Demo: Using Expressions to Create New Columns

https://docs.google.com/forms/d/e/1FAIpQLSd1PiYDZ8ztRBt7p7tsOTP6iJN7k0vcidyvi6ZLrf_dcNPeQA/viewform?usp=header

SAS Programming 1: Lesson 4, Part 2, Video 2: Using Numeric Functions to Create Columns

https://docs.google.com/forms/d/e/1FAIpQLSdx1uPo-TKu8ZqJeToHu9z02A1HuChqDVdH-5M8EDtnoamKjA/viewform?usp=header

SAS Programming 1: Lesson 4, Part 2, Video 3: Demo: Using Character Functions

https://docs.google.com/forms/d/e/1FAIpQLSehHLNu_mlxUJI6P9q6n9R5AaInlQCaOoA6UFxFSgtWIQFOhg/viewform?usp=header

SAS Programming 1: Lesson 4, Part 2, Video 4: Demo: Using Date Functions

https://docs.google.com/forms/d/e/1FAIpQLScpzkILXaEwLvll4E1Ehhm34pAJqOcIcH80cWLBgV9BsHYxoQ/viewform?usp=header

10/20 (IN-CLASS): Level 1: Creating New Columns and Level 2: Creating New Columns with Character and Date Functions

https://docs.google.com/forms/d/e/1FAIpQLScnlMpGLTJ85PRXwaK27-YMVrDNInF-4bQIt486E2BtY-np_Q/viewform?usp=header

10/20: CNBC: Amazon Web Services outage hits major websites: What we know so far as recovery begins

Amazon Web Services outage hits major websites: What we know so far as recovery begins https://www.cnbc.com/2025/10/20/amazon-web-services-outage-takes-down-major-websites.html

https://docs.google.com/forms/d/e/1FAIpQLSdJgx_bglFUDT4-vo6dLyy0BYm7xC6zHjz3GPGPX1sULMXZOA/viewform?usp=header

as of 14:05

https://health.aws.amazon.com/health/status

Operational issue - Multiple services (N. Virginia)

Service

Multiple services

Severity

Degraded

RSS

Increased Error Rates and Latencies

Oct 20 10:38 AM PDT Our mitigations to resolve launch failures for new EC2 instances are progressing and the internal subsystems of EC2 are now showing early signs of recovering in a few Availability Zones (AZs) in the US-EAST-1 Region. We are applying mitigations to the remaining AZs at which point we expect launch errors and network connectivity issues to subside. We will provide an update by 11:30 AM PDT.

Oct 20 10:03 AM PDT We continue to apply mitigation steps for network load balancer health and recovering connectivity for most AWS services. Lambda is experiencing function invocation errors because an internal subsystem was impacted by the network load balancer health checks. We are taking steps to recover this internal Lambda system. For EC2 launch instance failures, we are in the process of validating a fix and will deploy to the first AZ as soon as we have confidence we can do so safely. We will provide an update by 10:45 AM PDT.

Oct 20 9:13 AM PDT We have taken additional mitigation steps to aid the recovery of the underlying internal subsystem responsible for monitoring the health of our network load balancers and are now seeing connectivity and API recovery for AWS services. We have also identified and are applying next steps to mitigate throttling of new EC2 instance launches. We will provide an update by 10:00 AM PDT.

Oct 20 8:43 AM PDT We have narrowed down the source of the network connectivity issues that impacted AWS Services. The root cause is an underlying internal subsystem responsible for monitoring the health of our network load balancers. We are throttling requests for new EC2 instance launches to aid recovery and actively working on mitigations.

Oct 20 8:04 AM PDT We continue to investigate the root cause for the network connectivity issues that are impacting AWS services such as DynamoDB, SQS, and Amazon Connect in the US-EAST-1 Region. We have identified that the issue originated from within the EC2 internal network. We continue to investigate and identify mitigations.

Oct 20 7:29 AM PDT We have confirmed multiple AWS services experienced network connectivity issues in the US-EAST-1 Region. We are seeing early signs of recovery for the connectivity issues and are continuing to investigate the root cause.

Oct 20 7:14 AM PDT We can confirm significant API errors and connectivity issues across multiple services in the US-EAST-1 Region. We are investigating and will provide further update in 30 minutes or soon if we have additional information.

Oct 20 6:42 AM PDT We have applied multiple mitigations across multiple Availability Zones (AZs) in US-EAST-1 and are still experiencing elevated errors for new EC2 instance launches. We are rate limiting new instance launches to aid recovery. We will provide an update at 7:30 AM PDT or sooner if we have additional information.

Oct 20 5:48 AM PDT We are making progress on resolving the issue with new EC2 instance launches in the US-EAST-1 Region and are now able to successfully launch new instances in some Availability Zones. We are applying similar mitigations to the remaining impacted Availability Zones to restore new instance launches. As we continue to make progress, customers will see an increasing number of successful new EC2 launches. We continue to recommend that customers launch new EC2 Instance launches that are not targeted to a specific Availability Zone (AZ) so that EC2 has flexibility in selecting the appropriate AZ. We also wanted to share that we are continuing to successfully process the backlog of events for both EventBridge and Cloudtrail. New events published to these services are being delivered normally and are not experiencing elevated delivery latencies. We will provide an update by 6:30 AM PDT or sooner if we have additional information to share.

Oct 20 5:10 AM PDT We confirm that we have now recovered processing of SQS queues via Lambda Event Source Mappings. We are now working through processing the backlog of SQS messages in Lambda queues.

Oct 20 4:48 AM PDT We continue to work to fully restore new EC2 launches in US-EAST-1. We recommend EC2 Instance launches that are not targeted to a specific Availability Zone (AZ) so that EC2 has flexibility in selecting the appropriate AZ. The impairment in new EC2 launches also affects services such as RDS, ECS, and Glue. We also recommend that Auto Scaling Groups are configured to use multiple AZs so that Auto Scaling can manage EC2 instance launches automatically. We are pursuing further mitigation steps to recover Lambda’s polling delays for Event Source Mappings for SQS. AWS features that depend on Lambda’s SQS polling capabilities such as Organization policy updates are also experiencing elevated processing times. We will provide an update by 5:30 AM PDT.

Oct 20 4:08 AM PDT We are continuing to work towards full recovery for EC2 launch errors, which may manifest as an Insufficient Capacity Error. Additionally, we continue to work toward mitigation for elevated polling delays for Lambda, specifically for Lambda Event Source Mappings for SQS. We will provide an update by 5:00 AM PDT.

Oct 20 3:35 AM PDT The underlying DNS issue has been fully mitigated, and most AWS Service operations are succeeding normally now. Some requests may be throttled while we work toward full resolution. Additionally, some services are continuing to work through a backlog of events such as Cloudtrail and Lambda. While most operations are recovered, requests to launch new EC2 instances (or services that launch EC2 instances such as ECS) in the US-EAST-1 Region are still experiencing increased error rates. We continue to work toward full resolution. If you are still experiencing an issue resolving the DynamoDB service endpoints in US-EAST-1, we recommend flushing your DNS caches. We will provide an update by 4:15 AM, or sooner if we have additional information to share.

Oct 20 3:03 AM PDT We continue to observe recovery across most of the affected AWS Services. We can confirm global services and features that rely on US-EAST-1 have also recovered. We continue to work towards full resolution and will provide updates as we have more information to share.

Oct 20 2:27 AM PDT We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information.

Oct 20 2:22 AM PDT We have applied initial mitigations and we are observing early signs of recovery for some impacted AWS Services. During this time, requests may continue to fail as we work toward full resolution. We recommend customers retry failed requests. While requests begin succeeding, there may be additional latency and some services will have a backlog of work to work through, which may take additional time to fully process. We will continue to provide updates as we have more information to share, or by 3:15 AM.

Oct 20 2:01 AM PDT We have identified a potential root cause for error rates for the DynamoDB APIs in the US-EAST-1 Region. Based on our investigation, the issue appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1. We are working on multiple parallel paths to accelerate recovery. This issue also affects other AWS Services in the US-EAST-1 Region. Global services or features that rely on US-EAST-1 endpoints such as IAM updates and DynamoDB Global tables may also be experiencing issues. During this time, customers may be unable to create or update Support Cases. We recommend customers continue to retry any failed requests. We will continue to provide updates as we have more information to share, or by 2:45 AM.

Oct 20 1:26 AM PDT We can confirm significant error rates for requests made to the DynamoDB endpoint in the US-EAST-1 Region. This issue also affects other AWS Services in the US-EAST-1 Region as well. During this time, customers may be unable to create or update Support Cases. Engineers were immediately engaged and are actively working on both mitigating the issue, and fully understanding the root cause. We will continue to provide updates as we have more information to share, or by 2:00 AM.

Oct 20 12:51 AM PDT We can confirm increased error rates and latencies for multiple AWS Services in the US-EAST-1 Region. This issue may also be affecting Case Creation through the AWS Support Center or the Support API. We are actively engaged and working to both mitigate the issue and understand root cause. We will provide an update in 45 minutes, or sooner if we have additional information to share.

Oct 20 12:11 AM PDT We are investigating increased error rates and latencies for multiple AWS services in the US-EAST-1 Region. We will provide another update in the next 30-45 minutes.

Affected AWS services

The following AWS services have been affected by this issue.

Impacted (104 services)

AWS AppConfig

AWS Application Migration Service

AWS B2B Data Interchange

AWS Batch

AWS Billing Console

AWS Client VPN

AWS Cloud WAN

AWS CloudHSM

AWS CodeBuild

AWS Config

AWS DataSync

AWS Database Migration Service

AWS Deadline Cloud

AWS Direct Connect

AWS Directory Service

AWS Elastic Disaster Recovery

AWS Elastic VMWare Service

AWS Elemental

AWS End User Messaging

AWS Global Accelerator

AWS Glue

AWS HealthImaging

AWS HealthLake

AWS HealthOmics

AWS IoT Core

AWS Lambda

AWS Launch Wizard

AWS Outposts

AWS Parallel Computing Service

AWS Partner Central

AWS Payment Cryptography

AWS Private Certificate Authority

AWS Resource Groups

AWS Secrets Manager

AWS Security Incident Response

AWS Security Token Service

AWS Site-to-Site VPN

AWS Step Functions

AWS Storage Gateway

AWS Systems Manager for SAP

AWS Transfer Family

AWS Transform

AWS Transit Gateway

AWS Verified Access

AWS WickrGov

Amazon AppStream 2.0

Amazon Athena

Amazon Aurora DSQL Service

Amazon Bedrock

Amazon Chime

Amazon CloudFront

Amazon CloudWatch

Amazon CloudWatch Application Insights

Amazon Cognito

Amazon Connect

Amazon DataZone

Amazon DocumentDB

Amazon EC2 Instance Connect

Amazon EMR Serverless

Amazon ElastiCache

Amazon Elastic Compute Cloud

Amazon Elastic Container Registry

Amazon Elastic Container Service

Amazon Elastic File System

Amazon Elastic Kubernetes Service

Amazon Elastic Load Balancing

Amazon Elastic MapReduce

Amazon EventBridge

Amazon EventBridge Scheduler

Amazon FSx

Amazon GameLift Servers

Amazon GameLift Streams

Amazon GuardDuty

Amazon Interactive Video Service

Amazon Kendra

Amazon Kinesis Data Streams

Amazon Kinesis Firehose

Amazon Kinesis Video Streams

Amazon Location Service

Amazon MQ

Amazon Managed Service for Apache Flink

Amazon Managed Service for Prometheus

Amazon Managed Streaming for Apache Kafka

Amazon Managed Workflows for Apache Airflow

Amazon Neptune

Amazon OpenSearch Service

Amazon Pinpoint

Amazon Polly

Amazon Q Business

Amazon Quick Suite

Amazon Redshift

Amazon Relational Database Service

Amazon SageMaker

Amazon Security Lake

Amazon Simple Notification Service

Amazon Simple Storage Service

Amazon Simple Workflow Service

Amazon Timestream

Amazon Transcribe

Amazon VPC IP Address Manager

Amazon WorkSpaces

Amazon WorkSpaces Thin Client

EC2 Image Builder

Traffic Mirroring

Resolved (26 services)

AWS AppSync

AWS CloudFormation

AWS CloudTrail

AWS Elastic Beanstalk

AWS Firewall Manager

AWS IAM Identity Center

AWS Identity and Access Management

AWS IoT Analytics

AWS IoT Events

AWS IoT FleetWise

AWS IoT SiteWise

AWS NAT Gateway

AWS Network Firewall

AWS Organizations

AWS Support API

AWS Support Center

AWS Systems Manager

AWS VPCE PrivateLink

Amazon API Gateway

Amazon AppFlow

Amazon Comprehend

Amazon DynamoDB

Amazon Simple Email Service

Amazon Simple Queue Service

Amazon VPC Lattice

Amazon WorkMail

As of 2025-10-20 at 18:00

Wednesday, November 26, 2025

Monday, November 10, 2025

ChatGPT said:

1. What Reagan did

2. How a government shutdown is different

3. What Trump could do

You said:

ChatGPT said:

1. Reagan’s 1981 situation (PATCO strike)

2. A modern government shutdown

3. The core difference

Friday, October 31, 2025

Wednesday, October 29, 2025

Friday, October 24, 2025

Economics Symposium, tomorrow, Thursday, October 23 🕖 7:00 PM 📍 ECU Life Science Building and Biotechnology Building Room 1006

✅ Was It True That Economics Initially Focused Only on Market Goods?

🌿 When Did This Change?

🌟 Key Pioneers Who Revolutionized Non-Market Valuation

🔥 The Most Revolutionary Idea

📌 Before This Revolution:

📌 After This Revolution:

🎯 Final Answer (in simple terms):

🎯 The First Real Attempt to Quantify Value of Non-Market Environmental Goods:

Harold Hotelling (1949)

🔍 What Did He Do?

🧠 Why Hotelling is Considered the First:

🚩 Therefore:

🧾 Summary Answer:

Wednesday, October 22, 2025

Monday, October 20, 2025

Operational issue - Multiple services (N. Virginia)

Affected AWS services

Economic news - CNNMoney.com