AWS CloudFormations

Type: Bitnami Support Tool

Description:
Hi There,

I am using the pre-build AWS-Marketplace template for creating the wordpress - link here https://aws.amazon.com/marketplace/server/fulfillment?deliveryMethod=d836eefcc5b629e6bd3fb61ab22c8c7a&productId=fab4b73b-1de2-4c15-81e9-8882c3a02d0a&region=us-east-1&version=64bd5ace-873c-4595-9bcd-bc1269807d1d&ref_=cfg_full_continue

when i run those cloudformations stack , the stack get an error as below:

021-10-05 22:20:52 UTC+0100 WordpressEFSMountTarget2 CREATE_FAILED Resource handler returned message: “The IAM identity making this call has an IAM policy that is too large. Reduce the size of the policy and try again. (Service: Efs, Status Code: 400, Request ID: ca02e170-1553-4c49-9ed7-465983af9bbc, Extended Request ID: null)” (RequestToken: 425f7b46-e4a7-86ec-b31a-47daa890c12b, HandlerErrorCode: GeneralServiceException)
2021-10-05 22:20:51 UTC+0100 NotificationTopic CREATE_COMPLETE -
2021-10-05 22:20:51 UTC+0100 WordpressEFSMountTarget1 CREATE_FAILED Resource handler returned message: “The IAM identity making this call has an IAM policy that is too large. Reduce the size of the policy and try again. (Service: Efs, Status Code: 400, Request ID: 84b569b6-c071-499f-9b85-d99e91c717b6, Extended Request ID: null)” (RequestToken: 16e40fba-492f-5f76-97b0-015f8904831c, HandlerErrorCode: GeneralServiceException)

Can you please help ? how i can run this cloudforamtions?

Hi @kodrasteve,

Did you follow the steps in this guide?

https://docs.bitnami.com/aws-templates/apps/wordpress-production-ready/get-started/launch-production-ready-deployment/

Regards,
Michiel

@michiel Yes i did follow that, but i managed to get it working some how after running few times the deployment.

I have another issue at the moment - I am trying to create an LetsEncrypt for the ec2 severs on private subnet…
so I have Route53 --> A Record with Alias to -->ALB --> to EC2 .
sow when i run below command:

sudo /opt/bitnami/bncert-tool

I get the following:
Warning: the Doman paviitaly.mx resolves to a different IP address than the one detected for this machine, which is ‘54.158.213.99’, please fix the its DNSentries or remove it for more info see
https://docs.bitnami.com/general/faq/configuration/configure-custom-domain/

Some how the IP ‘54.158.213.99’ that LetsEncrypts detects is the NAT gateway IP…

on same ec2 when i do nslookup to the paviitaly.mx it retuns the right public IP

paviitaly.mx
Server: 10.0.0.2
Address: 10.0.0.2#53

Non-authoritative answer:
Name: paviitaly.mx
Addresses: 3.216.47.70
34.206.251.254

any ideas?

Hi @kodrasteve,

I’m afraid the bncert tool does not work in this situation. Could you try the manual approach?

https://docs.bitnami.com/aws/how-to/generate-install-lets-encrypt-ssl/#alternative-approach

Regards,
Michiel