Skip to main content

Allow others to upload files in your Amazon S3 bucket

 Allow others to upload files in your Amazon S3 bucket

Let us explore how can we allow others to upload files in our AWS account using AWS console

01. Create user - Login to to AWS console --> Select IAM --> Users --> Add User --> Username -->  Password
 
02. Create Amazon s3 bucket --> Select S3 --> Create Bucket --> Bucket Name --> Create Bucket

Note:  Keep Check Box Checked for Block All public Access, and other options as default.
 
03. Create Amazon s3 bucket policy --> Select Bucket --> Bucket Policy --> Edit --> Add following bucket policy as follows.

Note: Make sure to replace Bucke_Name with your actual bucket name.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowToListBucket",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::<YourAmzon 12 Digit A/c No.>:user/<Bucket_Name>"
            },
            "Action": "s3:ListBucket",
            "Resource": "arn:aws:s3:::<Bucket_Name>"
        }
    ]
}
 
04. Create user policy - Select User --> Add Inline Policy --> Json. Add following policy for User 

Note: Make sure to replace Bucket_Name, and Folder_name with your actual bucket name and folder name.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "s3:PutObject",
                "s3:GetObject"
            ],
            "Resource": "arn:aws:s3:::<Bucket_Name>/<Folder_Name>/*"
        }
    ]
}




Comments

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...

Oracle E-Business Suite Online Patch Phases executing adop

Following description about Oracle E-Business Suite is high level and from documentation https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm#5281339 for in depth and detail description refer it. The online patching cycle phases: Prepare Apply Finalize Cutover Cleanup Prepare phase: Start a new online patching cycle, Prepares the environment for patching. $ adop phase=prepare Apply phase: Applies the specified patches to the environment. Apply one or more patches to the patch edition. $ adop phase=apply patches=123456,789101 workers=8 Finalize phase: Performs any final steps required to make the system ready for cutover. Perform the final patching operations that can be executed while the application is still online. $ adop phase=finalize Cutover phase: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase that involves a brief ...