Planting AWS Serverless Seeds

How to configure an AWS Integration and plant / retire AWS Serverless Seeds

Our AWS Serverless Seeds come in a variety of flavours, but they all need an AWS integration to be created first, as we use this to plant and retire the seeds and to collect signal data from the seeds.

Step 1: Create an AWS integration

Our AWS integration is a small collection of resources specifically created within your tenant (via a cloudformation link) to provide the tools we need for planting retiring and monitoring seeds. the integration includes a role, a policy, an S3 bucket and an event bridge rule. We provide all this for you, preconfigured, one you tell us where you want to put it:

1. Sign in to App.seedata.io, and browse to /integrations/marketplace

2. Click INSTALL on the AWS tile

3. Provide a name and description, so you can identify your integrations uniquely

4. Provide the AWS Account Number that you want this integration to cover

5. Chose a region to install the integration objects into

6. Confirm your agreement to the terms and conditions, and click SUBMIT

7. We will then configure the integration without our platform, and provide a link to cloudformation for you to run within your intended AWS account. This must be the same run within the same AWS Account and Region as you previously provided, so please do double check this when youve clicked the CloudFormation link

8. Once you see the stack deployment is completed, return to app.seedata.io, and look for the green status light against your new integration (usually, this completes within 5 minutes max). Once you have this, the integration is available for use within a new deployment

9. If it fails, the best first response is to delete the integration from seedata, delete the stack (if it exists) from AWS and start again. If the issue persists, contact us on [e-mail] for help

Step 2: Create a deployment

This is our standard deployment journey, but with a few minor tweaks

1. Sign in to app.seedata.io and browse to seeds/marketplace

2. Choose the seed type you wish to deploy (use the filter or scroll down to see AWS Serverless seeds group) and click Add New

3. Complete the Add New Seeds form with appropriate values. You may be required to chose a region (you have free choice here, it doesnt need to be the same region as you installed the integration).

4. Choose your intended AWS integration as the Destination

5. Click SUBMIT

6. The new seeds will be added as new AWS resources of the selected type, without any further manual intervention

Step 3: Test the seeds

The best way to trigger an event is to run a command against the seed. This will vary depending on the seed type, but we collect a wide variety of AWS Management events

Once you've run a command which triggers an event, you should see a record of the event within app.seedata.io

Step 4: Retire the seeds

Our AWS seeds can be retired directly from the platform, clicking the action button to the right of the row. This will fully remove the seed from your tenant.

Step 5: Remove the integration

Our integration needs manual interaction if you wish to remove it in the future.

1. Go to /integration and find the integration you wish to remove

2. Note the full name of the integration you wish to remove

3. Click DELETE to remove records of the integration from the seedata platform

4. Sign in to the AWS account where the integration was installed, go toCloudFormation and find the stack that shares the name of the integration

5. Click Delete. This will remove most of the objects, but you will be required to repeat this step after seeing the stack fail to delete (this happens because there are objects in the S3 bucket). So, click Force Delete, and confirm you want all objects removing