Akeneo Amazon S3 Integration

Once you have created an account or signed in then you have to create a ticket.

Step1: Create a Bucket

Go to Services >> All Services >> S3 to create a bucket, or enter “s3” directly into the search field.

Next, create a new bucket or select an existing one.

Once you’ve selected “Create Bucket,” you have to enter the details mentioned below.

1. Type the bucket name
2. Select your AWS Region
3. Choose the ACLs enabled from object ownership.

Rest Keep all the default configuration and click on create bucket button.

Step 2:  Create a Policy 

After creating the bucket, go to step two to create the policy for it by navigating to Services >> All Services >>IAM.

Following that, choose Policy from the left menu, and then click the “new policy” option.

After clicking the create button, a popup screen will display.

• Select the service S3
• Select the following  Actions:

1. ListBucket
2. GetBucketAcl
3. GetObject
4. GetObjectAcl
5. DeleteObject
6. PutObject
7. PutObjectAcl

• Choose Resources => Enter the name of the bucket and object.

Click the next Tags. In step 3, enter the policy name.

Once the policy has been created, update it, then copy the JSON and Policy ARN for further processing.

Step 3: Create a User

To create a new user you have to navigate to Services>> All Services >> IAM >> Users >> Add Users.

Next, enter the user name then select the next button.

Set the permissions after which you can choose “Attach policy directly” >> “Choose the created policy” and “Next.”

And then click on the create user.

Step 4: Create access key

To get access, edit the created user, and then select the security credentials tab. Then, click the Create Access Key button to get the key.

Select the other case click on the next button then click on create an access key button and then download the CSV.

Read This Blog

Before beginning the composer installation

1: Get the ACCESS KEYS [Create a support ticket]
2: In Akeneo composer.json, add our repository as well as the installation script.

Akeneo 6 and 7:

{
  "scripts": {
        "post-update-cmd": [
           "vendor/webkul/awsintegrationbundle/src/Webkul/AwsIntegrationBundle/install/config.sh COMPOSER=true NO_DOCKER=true"
        ],
        "post-install-cmd": [
           "vendor/webkul/awsintegrationbundle/src/Webkul/AwsIntegrationBundle/install/config.sh COMPOSER=true NO_DOCKER=true"
        ],
        "post-create-project-cmd": [
          "vendor/webkul/awsintegrationbundle/src/Webkul/AwsIntegrationBundle/install/config.sh COMPOSER=true NO_DOCKER=true"
       ]
   },
  "repositories": [{
    "type": "composer",
    "url": "https://akeneorepo.webkul.com/"
  }]
}

For Akeneo <=5.x 

{
  "scripts": {
        "post-update-cmd": [
           
"vendor/webkul/awsintegrationbundle/composer_install.sh"
        ],
        "post-install-cmd": [
           
"vendor/webkul/awsintegrationbundle/composer_install.sh"
        ],
        "post-create-project-cmd": [
         
"vendor/webkul/awsintegrationbundle/composer_install.sh"
       ]
   },
  "repositories": [{
    "type": "composer",
    "url": "https://akeneorepo.webkul.com/"
  }]
}

3: Use composer to install the extension.

         composer require webkul/awsintegrationbundle

4: Complete the authentication form.
5: Send a Message of Success
6: Delete your browser’s cache.

•  After unzipping the appropriate extension zip, merge the “src” folder into the akeneo project.
• From the PIM directory, run the following command over the NO-DOCKER Instance.

./src/Webkul/AwsIntegrationBundle/install/config.sh COMPOSER=false NO_DOCKER=true

•  Run the command below over the PIM directory’s DOCKER instance.

./src/Webkul/AwsIntegrationBundle/install/config.sh COMPOSER=false NO_DOCKER=false

After installing this Bundle, add settings in Aws Integration tab and product data like image and files will be saved to Aws bucket

If you have already existing product media data then run following command from terminal to move files to amazon s3

<span id="LC1" class="line" lang="plaintext">    php bin/console aws_integration:move_existing_files:s3</span>

And If you are using Akeneo Enterprise Edition and want to export all your product assets to Amazon S3 then run this command.

<span id="LC1" class="line" lang="plaintext">    php bin/console aws_integration:move_existing_asset_files:s3</span>

php -d memory_limit=4G /usr/local/bin/composer --prefer-dist --no-scripts require aws/aws-sdk-php v3.172.0 -v;

php -d memory_limit=4G /usr/local/bin/composer --prefer-dist --no-scripts require league/flysystem-aws-s3-v3 v1.0.6 -v;

For Akeneo 4

php -d memory_limit=4G /usr/local/bin/composer --prefer-dist --no-scripts require aws/aws-sdk-php v3.5.0 -v;

php -d memory_limit=4G /usr/local/bin/composer --prefer-dist --no-scripts require league/flysystem-aws-s3-v3 v1.0.6 -v;

After that please follow these steps for installing Akeneo Amazon S3 Integration in your Akeneo PIM platform.

Webkul\AwsIntegrationBundle\AwsIntegrationBundle::class => [ 'all'=> true],

php bin/console cache:clear--env=prod;php bin/console aws:setup:install

• If you are using php-fpm. Then you need to restart the php-fpm services.

For Akeneo 5

sudo service php-fpm7.4 restart

For Akeneo 4

sudo service php-fpm7.3 restart

Docker Installation Command :

For Akeneo 5

alias docker_php='docker-compose run -u www-data --rm php php';
alias docker_yarn='docker-compose run -u node --rm node yarn';
docker_php bin/console cache:clear --env=prod;
docker_php bin/console pim:installer:assets --symlink --clean --env=prod;
docker_php bin/console d:s:u --force;
docker_yarn run webpack;
docker_yarn run update-extensions;
docker_yarn run less;

For Akeneo 4

alias docker_php='docker-compose run -u www-data --rm php php';
alias docker_yarn='docker-compose run -u node --rm node yarn';
docker_php bin/console cache:clear --env=prod;
docker_php bin/console pim:installer:assets --symlink --clean --env=prod;
docker_php bin/console d:s:u --force;
docker_yarn run webpack;
docker_yarn run less;

After installing this Bundle, add settings in Aws Integration tab and product data like image and files will be saved to Aws bucket

If you have already existing product media data then run following command from terminal to move files to amazon s3

<span id="LC1" class="line" lang="plaintext">    php bin/console aws_integration:move_existing_files:s3</span>

And If you are using Akeneo Enterprise Edition and want to export all your product assets to Amazon S3 then run this command.

<span id="LC1" class="line" lang="plaintext">    php bin/console aws_integration:move_existing_asset_files:s3</span>

Please follow these steps for installing Akeneo Amazon S3 Integration in your Akeneo PIM platform.

new Webkul\AwsIntegrationBundle\AwsIntegrationBundle(),

 - { resource: "@AwsIntegrationBundle/Resources/config/config.yml" }

aws_integration:
    resource: "@AwsIntegrationBundle/Resources/config/routing.yml"
    prefix:   /

php bin/console cache:clear--env=prod;php bin/console aws:setup:install

<span id="LC1" class="line" lang="plaintext">    php bin/console aws_integration:move_existing_files:s3</span>

<span id="LC1" class="line" lang="plaintext">    php bin/console aws_integration:move_existing_asset_files:s3</span>

php bin/console aws_integration:move_existing_files:s3

php bin/console aws_integration:move_existing_asset_files:s3

npm install --save-prod webpack
npm install

• Module routing.yml is not configured properly. Re-check the routing.yml file as mentioned in the 3rd step of Module Installation
  
• Clear your browser cache using ctrl+shift+r.

./src/Webkul/AwsIntegrationBundle/uninstall/uninstall.sh COMPOSER=false NO_DOCKER=true

./src/Webkul/AwsIntegrationBundle/uninstall/uninstall.sh COMPOSER=false NO_DOCKER=false

Adarsh Shukla 6 Badges

• 10 Jan, 2024
  Updated by - Kavita Singh
• 20 Mar, 2023
  Updated by - Kavita Singh

View More