financial-times/upp-provisioners

Contains the various provisioning projects used by the Universal Publishing Platform

upp-provisioners's Issues

No tags for buckets created by upp-elasticsearch-provisioner

Buckets created by the upp-elasticsearch-provisioner playbook does not contain the required tags.

Resource has no tags. Required tags are: [systemCode, teamDL, environment]

Here is a direct link to the ansible task that should be changed.

upp-concept-publishing-provisioner - creation of resources out of order causes stack roll back.

On one occasion I have experienced an Error when provisionning AWS stack with Docker image in upp-concept-publishing-provisioner project.
The error is as follows:
"Unable to validate the following destination configurations" when using S3 event notifications in CloudFormation.
The issue was to do with creating the s3 bucket, SNS Topic and Subscription in the wrong order, (possibly due to time it took CF to create). This caused the stack to roll back.

It is described here in detail.
https://aws.amazon.com/premiumsupport/knowledge-center/unable-validate-destination-s3/

Jenkins provisioner to use amazon ft-base

the content jenkins provisioner uses an ami which doesn't come with FT related things. Use amazon ftbase as base for the EC2 instance.

Elasticsearch snapshot fails

upp-provisioners/upp-elasticsearch-provisioner/ansible/files/register-es-snapshot-dir.py

Line 45 in 9ebfae4

path='/_snapshot/index-backups',

This should point towards the new s3 bucket upp-concepts-k8s-prod-eu-backup.

Otherwise, we get this:

{
    "error": {
        "root_cause": [
            {
                "type": "repository_missing_exception",
                "reason": "[upp-concepts-k8s-prod-eu-backup] missing"
            }
        ],
        "type": "repository_missing_exception",
        "reason": "[upp-concepts-k8s-prod-eu-backup] missing"
    },
    "status": 404
}