-
AWS RDS Aurora being created using the mySQL database engine
-
Then the creation of AWS Elasticache Redis Cache
- The creation of a domain abdulhamid.com on amazon Route53,
-
Creation of an S3 Bucket
-
S3 bucket named myabdulbucket being created already
-
Uploading a png file on my AWS S3 bucket
Sample of an S3 Bucket policy
{
"id" : "Policy15672859245",
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Stmt12674263965",
"Action":[
"s3: BetObject"
],
"Effect":"Allow",
"Resource":"arn:aws:s3:::myabdulbucket",
"Principal":"*"
}
]
}
- Uploading a static website on AWS S3, index.html file
- S3 Bucket Replica being created, by first creating the bucket and its replica
- Creation of a destination bucket replication rule
-
Batch Object Operations asking if we want to replicate exisiting objects
-
the replication rule created finally
- Setting of storage classes for the AWS S3 Bucket object from the properties tab
- Ading a lifecycle rule for the objects in the S3 Bucket
- Getting started with the EC2 instance metadata Version 2 (V2)
launching of eC2 instance for the instance metadata
- The first token code for the imdsV2 being put in our EC2 instance connect to get our token for the metadata
- Here are the tokens to be used
TOKEN=`curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"`
curl -H "X-aws-ec2-metadata-token: $TOKEN" http://169.254.169.254/latest/meta-data/
- Our token for imdsV2 getting our EC2 instance metadata works as expected
- Creation of an S3 Event from the property section in the S3 bucket you created
-
Creation of an event notification
-
Creation of queue for the event notification destination
- Editing the SQS Queue policy to accept the event notification
- Generating the policy for the amazon SQS Queue using the aws policy generator
Here is the policy in JSON
{
"Id": "Policy1711364311955",
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Stmt1711364309953",
"Action": [
"sqs:SendMessage"
],
"Effect": "Allow",
"Resource": "arn:aws:sqs:us-east-1:058264276076:demos3notification",
"Principal": "*"
}
]
}
Now our event notification has been created finally
- Working on the server side encryption settings on the objects in the S3 bucket
- Here is the final encryption being created finally
- Setting up an statice website hosting and then planning to work on CORS(Cross Origin Resource Sharing)
- Got an error from setting the static website
- Finally working now
Due to the bucket policy I added to allow public access
Here is the bucket policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "*"
},
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::demo-encryption-mide/*"
}
]
}
- Created another bucket to allow the CORS
- Then we have the CORS policy to allow the cross origin possible
[
{
"AllowedHeaders": [
"Authorization"
],
"AllowedMethods": [
"GET"
],
"AllowedOrigins": [
"http://demo-encryption-mide.s3-website-us-east-1.amazonaws.com"
],
"ExposeHeaders": [],
"MaxAgeSeconds": 3000
}
]
- CORS origin worked finally
- Getting the server side logging for the S3 bucket done
- Making use of S3 presigned URL to share files and data for a specific period of time
- Creation of an S3 Bucket for cloudfront
-
The Cloudfront distribution has been successfully made and then the S3 policy has been updated:
-
Here is the S3 bucket policy
{
"Version": "2008-10-17",
"Id": "PolicyForCloudFrontPrivateContent",
"Statement": [
{
"Sid": "AllowCloudFrontServicePrincipal",
"Effect": "Allow",
"Principal": {
"Service": "cloudfront.amazonaws.com"
},
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::demo-cloudfront-mide/*",
"Condition": {
"StringEquals": {
"AWS:SourceArn": "arn:aws:cloudfront::058264276076:distribution/E2LL851ED9SCNW"
}
}
}
]
}