Update buildspec.yaml

[ishu599]

Summary by CodeRabbit

Release Notes

• Chores
  • Updated build pipeline email notification configuration to ensure proper delivery of build status updates.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates the CodeBuild email notification configuration in buildspec.yaml. A commented SES send-email command and the active post_build phase both change the sender and recipient email addresses to ishuraghuvinder@gmail.com and update the AWS region to eu-north-1.

Changes

Email Notification Configuration

Layer / File(s)	Summary
SES email configuration update DevOps-Project-23/Swiggy_clone/buildspec.yaml	Commented SES command updates sender address, and active post_build phase is rewritten with both --from and --to set to ishuraghuvinder@gmail.com with AWS region changed to eu-north-1.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A buildspec update hops into place,
SES emails find their new space,
From Dublin to Nordic shores they'll race,
With addresses shiny and emails so bright,
DevOps gets configured just right! 📧✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update buildspec.yaml' is generic and vague—it describes only the file being changed without conveying the specific nature of the updates (email notification configuration changes).	Consider a more descriptive title such as 'Update SES email configuration in buildspec.yaml' to clarify the actual change being made.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@DevOps-Project-23/Swiggy_clone/buildspec.yaml`:
- Around line 58-59: Replace the hardcoded emails used in the SES command
(--from and --to) with Parameter Store references and load them via the
buildspec env.parameter-store configuration; update the buildspec.yaml to
declare parameters (e.g., /cicd/ses/from-email and /cicd/ses/to-email) and
change the SES invocation to use the parameter values instead of literal
addresses so the SES command (the lines containing "--from" and "--to") reads
values from the parameter-store variables; also ensure CI/CD secrets are created
in SSM (aws ssm put-parameter ...) with verified SES addresses before the
pipeline runs.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0a8698d3-1abd-4bb8-9b5b-1dc87ed78584

📥 Commits

Reviewing files that changed from the base of the PR and between a38cc0f and 0381f99.

📒 Files selected for processing (1)

• DevOps-Project-23/Swiggy_clone/buildspec.yaml

[coderabbitai]

⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

Hardcoded email addresses expose PII and create security/maintainability risks.

Personal email addresses are hardcoded directly in the repository, which:

• Exposes PII (Personally Identifiable Information) to anyone with repository access
• Creates a spam/phishing target
• Makes the configuration inflexible and harder to maintain
• Violates security best practices for managing sensitive data

🔒 Proposed fix: Use AWS Systems Manager Parameter Store

Store email addresses in Parameter Store and reference them in the buildspec:

Update the env.parameter-store section:

 env:
   parameter-store:
     DOCKER_REGISTRY_USERNAME: /cicd/docker-credentials/username
     DOCKER_REGISTRY_PASSWORD: /cicd/docker-credentials/password
     DOCKER_REGISTRY_URL: /cicd/docker-registry/url
     SONAR_TOKEN: /cicd/sonar/sonar-token
+    NOTIFICATION_FROM_EMAIL: /cicd/ses/from-email
+    NOTIFICATION_TO_EMAIL: /cicd/ses/to-email

Then update the SES command:

 post_build:
   commands:
     - |
       aws ses send-email \
-        --from "ishuraghuvinder@gmail.com" \
-        --to "ishuraghuvinder@gmail.com" \
+        --from "$NOTIFICATION_FROM_EMAIL" \
+        --to "$NOTIFICATION_TO_EMAIL" \
         --subject "CodeBuild Status: $CODEBUILD_BUILD_ID" \
         --text "Build status: $CODEBUILD_BUILD_STATUS" \
         --region "eu-north-1"

Create the parameters:

aws ssm put-parameter --name /cicd/ses/from-email --value "your-verified-email@example.com" --type String
aws ssm put-parameter --name /cicd/ses/to-email --value "recipient@example.com" --type String

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@DevOps-Project-23/Swiggy_clone/buildspec.yaml` around lines 58 - 59, Replace
the hardcoded emails used in the SES command (--from and --to) with Parameter
Store references and load them via the buildspec env.parameter-store
configuration; update the buildspec.yaml to declare parameters (e.g.,
/cicd/ses/from-email and /cicd/ses/to-email) and change the SES invocation to
use the parameter values instead of literal addresses so the SES command (the
lines containing "--from" and "--to") reads values from the parameter-store
variables; also ensure CI/CD secrets are created in SSM (aws ssm put-parameter
...) with verified SES addresses before the pipeline runs.