Versent/golang-lambda-pipeline

Setup S3 SSE encryption for artefacts and deployments

Open

#5 opened on Mar 15, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (1 fork)auto 404
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (13 stars)
PR merge metrics
 (PR metrics pending)

Description

All buckets should use SSE.

  • Create an KMS key
  • Add encryption to build artefacts
  • Configure key policy so that cross-account roles can use it to decrypt when doing deployments

Contributor guide

Research direction
Investigate how to enable S3 server side encryption with KMS for build artifacts and deployments. Start by examining the current S3 bucket configurations and the AWS CodePipeline setup. Understand how KMS keys are created and how key policies must be configured to allow cross account access for deployment roles.
Tech stack
go
Domain
backendclouddevopssecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50