Backup and Disaster Recovery

AWS Backup

Data Backup Strategies

  • AWS Backup is a fully managed central service which can be used to manage and automate backups across AWS services. There is no need to create custom scripts or manual processes.
  • Set up lifecycle policies known as Backup plan based on below aspects.
    • Backup frequency: 12 hours, daily, weekly, monthly, cron expressions.
    • Backup window
    • Transition to cold storage: Never, Days, Weeks, Months, Years
    • Retention period: Always, Days, Weeks, Months, Years
  • AWS Backup supports services including EC2/EBS, S3, RDS, DynamoDB, Aurora, DocumentDB/Neptune, EFS and Amazon Storage Gateway.

Disaster Recovery Planning

  • Set up replication and failover systems to keep your services running if something goes wrong.
  • Use AWS services to automate recovery processes, minimising downtime and keeping your data safe.
  • Disaster Recovery approaches:
    • Backup and Restore: This is like making a copy of your data and putting it somewhere safe. If something bad happens, you can bring your system back to life using that copy.Imagine it’s like taking a photo of your important documents. If the originals get lost or damaged, you still have the photo to use.
    • Pilot Light: This is a bit like having a small flame always burning. It’s not doing much, but it’s ready to quickly light up the whole system if needed. Think of it as having the essential parts of your system ready to go. When a disaster strikes, you just need to add fuel to the fire to get everything running smoothly again.
    • Warm Standby: In this setup, you have a partially active backup system ready to take over if the main system fails. It’s not as quick as Pilot Light, but it’s faster than starting from scratch. It’s like having a backup car that’s almost ready to go. You just need to warm up the engine a bit before you can drive it.
    • Multi-site active: This is like having two or more fully working systems running at the same time in different locations. If one system goes down, the other one can immediately take over without any interruption. It’s similar to having duplicate keys for your house. If you lose one set, you can still get into your house using the spare key.

AWS Security Best Practices

The AWS Simple Storage Service (S3) is a cloud service provided by Amazon Web Services (AWS) to store your data securely. You can access this service through your IAM role or root user account. In this article, we’ll see different security measures to protect your data from fraudulent access using AWS Security Best Practices. Please note that, due to the extensive nature of security practices, we’ll cover a selection of key measures in this article.

Similar Reads

Implementing Access Control

Principle of Least Privilege...

Utilizing AWS IAM for user access management

...

Multi-Factor Authentication (MFA)

AWS MFA...

Logging and Monitoring

AWS Logging and Monitoring...

Data Encryption

Encrypting Data in Transit...

Network Security

Amazon Virtual Private Cloud (VPC)...

Patch Management

Importance of Regular Patching...

Backup and Disaster Recovery

AWS Backup...

User Education and Training

Enhancing user awareness of security risks....

Conclusion

Implementing Access Control: Use IAM to manage user permissions and restrict access to resources. Logging and Monitoring: Set up logging with AWS CloudTrail for proactive threat detection. Data Encryption: Encrypt data with TLS/SSL and client side encryption methods. Regular Patching: Ensure systems are regularly updated to mitigate vulnerabilities. Network Security: Use VPCs, security groups, and ACLs to control access and protect data. Data Encryption: Encrypt data in transit and at rest using TLS/SSL and AWS KMS. Backup and Disaster Recovery: Utilise Amazon S3 for backups and establish disaster recovery mechanisms. Security Awareness: Educate users about security risks and leverage AWS training resources....

AWS Security – FAQ’s

What is biggest threat to security on cloud?...