Use On-Demand Instances for flexibility

Use Spot Instances to lower cost

Move to AWS Lambda immediately

Switch to Reserved Instances with a 1-year term

Replace the security group with a new one

Add an inbound rule for TCP port 80 to the existing security group

Configure an Internet Gateway

Reboot the EC2 instance to refresh firewall rules

Savings plans

Reserved instances

On demand

Spot instances

Amazon Redshift

Amazon RDS

Amazon DynamoDB

Amazon Aurora

Place a CloudFront distribution in front of the S3 bucket

Move the bucket to the Asia Pacific (Singapore) Region

Enable cross-region replication for the S3 bucket

Use AWS Global Accelerator to distribute traffic

Amazon CloudWatch

AWS CloudTrail

AWS Trusted Advisor

Amazon Inspector

Tightly coupled systems are more flexible in adding new components, whereas loosely coupled systems require careful configuration to add new components

Loosely coupled systems require components to share data directly with each other, whereas tightly coupled systems store data in a central repository

In a tightly coupled architecture, components are tightly connected and dependent on each other, whereas in a loosely coupled architecture, components can operate independently

Tightly coupled architectures are designed for scalability, whereas loosely coupled systems focus on maintaining high availability

The ability to create fixed resources that never change in size

The ability to grow and shrink resources dynamically based on real-time demand

The ability to permanently increase resource capacity for long-term growth

The ability to manually adjust resources based on peak usage

It stores transaction details until the fraud detection service can process them, even if the service is down

It forces the transaction service and fraud detection service to depend on each other directly

It guarantees immediate approval of transactions

It speeds up transaction processing by avoiding the use of a buffer